3. MICRO IO’s CMMI Development 2 implementation - Rui Rebelo
•
0 gostou•280 visualizações
3. MICRO IO’s CMMI Development 2 implementation - Rui Rebelo
Recomendados
Mais conteúdo relacionado
Semelhante a 3. MICRO IO’s CMMI Development 2 implementation - Rui Rebelo
Semelhante a 3. MICRO IO’s CMMI Development 2 implementation - Rui Rebelo (20)
Mais de Strongstep - Innovation in software quality
Mais de Strongstep - Innovation in software quality (20)
Último
Último (20)
3. MICRO IO’s CMMI Development 2 implementation - Rui Rebelo
- 1. Micro IO’s CMMI-dev2 implementation Rui Rebelo Micro IO | Diretor Hardware
- 2. Agenda • Who’s Micro IO? • Problems and issues • Challenges • Goals • Lesson Learned • Results • Next Steps
- 3. 1- Who’s Micro IO? Founded in 1998 at the Enterprise Incubator of Universidade of Aveiro. We promote above all innovation, creativity and knowledge. We create integrated software and hardware solutions for our own products and for client specific custom applications.
- 4. 1- Who’s Micro IO?
- 5. + 500 institutions + 1.500.000 daily users Portugal Brazil Angola Cape Verde Mexico 1- Who’s Micro IO?
- 6. 2 – Problems and issues • No connection between business goals and development processes. • Software development management ad-hoc. • Hardware development managed by waterfall. • Business process centralized but not standardized.
- 7. 3 – Challenges • SME usual lack of time. • Hardware development own scope. (not a standard IT/software company) • Production and prototyping environment.
- 8. 4 - Goals • Drive by wire • Predictability and security • Communication • Increase business involvement • Improve administration involvement (on both ways) • Automatize some boring tasks…
- 9. 5 – Lessons Learned • Standardizing processes and procedures. • Increase of internal resilience. • Time spent will be recovered soon - and even more saved. • Metrics implemented helped us to know better the development team, pace and characteristics. • Approach and involvement of teams. • Organization and optimization of business processes.
- 10. • Increase internal confidence • Time savings • Better and systematic communication • Predictability • Involvement 6 - Results!
- 11. 7 – Next Steps… • Tackle CMMI dev 3 ? • Embed some of the CMMI Services and CMMI Acquisitions best practices... • Go for ISO 20001 if the market keeps pushing it.
Notas do Editor
- (10 minutes) – 6 slides maximum
- Nome – origem. História da empresa. 40 pax. Certificações
- Produtos + Projetos à medida Escolas, universidades, colégios; Empresas; Autarquias Spin-off/consórcio – para manter o focus. IDI Novas áreas na mobilidade. Grande foco com produtos para cidades inteligentes
- França, Canadá, Espanha e USA (brevemente)
- Not that bad… Lots of goodwill… …but with a lot of improving space. Tínhamos algumas lacunas… Pontos de melhoria. Normal nas SME. Estou a ser um pouco crítico de nós próprios.
- Best thing. Main key asset. People. Motivated, some times self motivated. CMMI is not that heavy to implement - that’s the best feature of it. SME doesn’t have time to do it. We were able to, in paralell being able to print a contínuos improvement pace on the team, wich still works with major improvements for the company.
- * Drive by wire or even – autonomous driving (remote team, colaboration team, flexible working hours, etc) * Predicatability on the development processes. See issues and address them at a safe distance. * Communication (in bettween the same team, diferente team, and with costumers). Increase business involvement on the development – multi stage Administration involvement on a very small basis
- ISO27001
- Bottlenecks become clearly visible in real-time – which can enable proactive actions Much better communication between development and maintenance teams
- Let’s see.
- Inovaria StrongStep Mecanismos de financiamento