Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

RIPPLE 2014: "Be Agile in a CMMI level 5 World"

•
•
Délio Almeida
Délio Almeida

CRITICAL Software presentation on RIPPLE conference, hosted and sponsored by BLIP in Oporto back in March 2014. The topic is focused on the alignment of Agile/Scrum within a CMMI Maturity Level 5 organization in Portugal.

1 of 11
Download to read offline
© COPYRIGHT 2014 CRITICAL SOFTWARE 2014-03-15 Be Agile in a CMMI5 context World Délio Almeida, CMMI and Agile Adopter
© COPYRIGHT 2014 CRITICAL SOFTWARE • How’s a CMMI5 company and its SW projects!? • What about Agile SW projects? • How do you glue the 2 !? • How’s a CMMI5 & Agile SW project? Agenda
3© COPYRIGHT 2014 CRITICAL SOFTWARE How’s a CMMI5 Project? Very Well structured Strongly documented process-wise Heavy Planning upfront Strong Risk and Project Mng. practises Makes use of many Engineering and Support Processes Data driven Quantitative and Statistical Analysis Predictable! Repeteable! How’s a CMMI5 company and its SW projects!? CMMI5World
4© COPYRIGHT 2014 CRITICAL SOFTWARE How’s a CMMI5 company and its SW projects!? CMMI5World
5© COPYRIGHT 2014 CRITICAL SOFTWARE What about Agile/Scrum SW development projects? AgileWorld Simpler Processes Less formalism Less outputs Less Documentation + Continuous Delivery + Working software Favours people & informal interactions Respond to CHANGE fast! Ready for Adaptation, Flexible, Moving Environments, Inspect & Adapt Empowers Teams Self-organize, No formal task assignment Transparency
6© COPYRIGHT 2014 CRITICAL SOFTWARE Use CMMI5 as a TOOL to make your Agile process, STRONG, coherent, integrated, WHILST taking advantage of the FLEXIBILITY and ADAPTABILITY TO CHANGE that it naturally provides CMMI5 is a Reference Model, a Collection of Best Practises Agile is GREAT for Products & Fast Changing Environments & Unclear Project Scopes CMMI5 is not a SW development methodology! Agile/Scrum is a process framework for complex product development You wrap Agile/Scrum SW Development framework and processes under CMMI5 umbrella How do you glue the 2 !? CMMI5+Agile!?
7© COPYRIGHT 2014 CRITICAL SOFTWARE • Uses Scrum as the basic process framework! • Has project/product plans, oh , Yes! • Quality Assurance Plan, Configuration Management Plan, etc... • Has metrics, and quantitative data for Sprint Retrospectives... • Uses statistical techniques for code review efficiency and effectiveness • Uses structured, proven and well tested Engineering and Support Processes attached to the Scrum framework: • SW Design, SW Construction, SW testing, ... • Configuration Management, Verification, Documentation, Quality Assurance, etc... • Makes heavy usage of SW tools for automation and continuous software delivery; • Uses Agile Estimation techniques (Planning Poker) + Single and 3-point estimates How’s a CMMI5 Agile SW Development project in Critical Software? CMMI5AgileSWDev
8© COPYRIGHT 2014 CRITICAL SOFTWARE How’s a CMMI5 Agile SW Development project in Critical Software? CMMI5+Agile!?
9© COPYRIGHT 2014 CRITICAL SOFTWARE How’s a CMMI5 Agile SW Development project in Critical Software? Metric / Indicator Name Unit Notes Sprint Goal Achievement % Measures the on-time delivery of scope committed with the PO Effort Estimation Accuracy % Measure accuracy of effort estimates of the team. Defect Fix Cost (ST) minutes Measures the average effort to fix a ST defect. Defect Fix Cost (post) minutes Measures the average effort to fix a post-delivery defect. Code Review Speed LOC/H Measures code review speed Code Review Defect Detection Rate defects/KLOC Measures defect rates for code reviews. Defect Density defects/KLOC Measures defect density per phase (CR, IT, ST, AT, Post-delivery), real-time Defect Detection Rate defects/KLOC Measures defect rate per phase (IT, ST, AT, Post-delivery), organizational wide Effort Breakdown / Effort per Task Type hours Effort breakdown in hours per task nature Sprint Velocity SP, Hours Measures work throughput in a given Sprint. Not comparable between Teams since baseline US are different , as well as the SP assigned to those. Project Size LOC Task Completion % Measure total effort planned + discovered in a Sprint, VS the effort completed / resolved.
10© COPYRIGHT 2014 CRITICAL SOFTWARE • Peoples Mindset! • Highly specialized resources and roles ... • A prestigious and widely recognized Agile Champion would have helped ! • Too many markets (>8), too many different project types, and too many different technologies! • Projects lasting from 2 months to 3,5 years.. • Teams are geographically distributed, normal to have members in 3 locations! How’s a CMMI5 Agile SW Development project in Critical Software? -> Problems Faced! CMMI5AgileSWDev
© COPYRIGHT 2014 CRITICAL SOFTWARE Délio Almeida, Quality Manager, CMMI and Agile Adopter

More Related Content

RIPPLE 2014: "Be Agile in a CMMI level 5 World"

  • 1. © COPYRIGHT 2014 CRITICAL SOFTWARE 2014-03-15 Be Agile in a CMMI5 context World Délio Almeida, CMMI and Agile Adopter
  • 2. © COPYRIGHT 2014 CRITICAL SOFTWARE • How’s a CMMI5 company and its SW projects!? • What about Agile SW projects? • How do you glue the 2 !? • How’s a CMMI5 & Agile SW project? Agenda
  • 3. 3© COPYRIGHT 2014 CRITICAL SOFTWARE How’s a CMMI5 Project? Very Well structured Strongly documented process-wise Heavy Planning upfront Strong Risk and Project Mng. practises Makes use of many Engineering and Support Processes Data driven Quantitative and Statistical Analysis Predictable! Repeteable! How’s a CMMI5 company and its SW projects!? CMMI5World
  • 4. 4© COPYRIGHT 2014 CRITICAL SOFTWARE How’s a CMMI5 company and its SW projects!? CMMI5World
  • 5. 5© COPYRIGHT 2014 CRITICAL SOFTWARE What about Agile/Scrum SW development projects? AgileWorld Simpler Processes Less formalism Less outputs Less Documentation + Continuous Delivery + Working software Favours people & informal interactions Respond to CHANGE fast! Ready for Adaptation, Flexible, Moving Environments, Inspect & Adapt Empowers Teams Self-organize, No formal task assignment Transparency
  • 6. 6© COPYRIGHT 2014 CRITICAL SOFTWARE Use CMMI5 as a TOOL to make your Agile process, STRONG, coherent, integrated, WHILST taking advantage of the FLEXIBILITY and ADAPTABILITY TO CHANGE that it naturally provides CMMI5 is a Reference Model, a Collection of Best Practises Agile is GREAT for Products & Fast Changing Environments & Unclear Project Scopes CMMI5 is not a SW development methodology! Agile/Scrum is a process framework for complex product development You wrap Agile/Scrum SW Development framework and processes under CMMI5 umbrella How do you glue the 2 !? CMMI5+Agile!?
  • 7. 7© COPYRIGHT 2014 CRITICAL SOFTWARE • Uses Scrum as the basic process framework! • Has project/product plans, oh , Yes! • Quality Assurance Plan, Configuration Management Plan, etc... • Has metrics, and quantitative data for Sprint Retrospectives... • Uses statistical techniques for code review efficiency and effectiveness • Uses structured, proven and well tested Engineering and Support Processes attached to the Scrum framework: • SW Design, SW Construction, SW testing, ... • Configuration Management, Verification, Documentation, Quality Assurance, etc... • Makes heavy usage of SW tools for automation and continuous software delivery; • Uses Agile Estimation techniques (Planning Poker) + Single and 3-point estimates How’s a CMMI5 Agile SW Development project in Critical Software? CMMI5AgileSWDev
  • 8. 8© COPYRIGHT 2014 CRITICAL SOFTWARE How’s a CMMI5 Agile SW Development project in Critical Software? CMMI5+Agile!?
  • 9. 9© COPYRIGHT 2014 CRITICAL SOFTWARE How’s a CMMI5 Agile SW Development project in Critical Software? Metric / Indicator Name Unit Notes Sprint Goal Achievement % Measures the on-time delivery of scope committed with the PO Effort Estimation Accuracy % Measure accuracy of effort estimates of the team. Defect Fix Cost (ST) minutes Measures the average effort to fix a ST defect. Defect Fix Cost (post) minutes Measures the average effort to fix a post-delivery defect. Code Review Speed LOC/H Measures code review speed Code Review Defect Detection Rate defects/KLOC Measures defect rates for code reviews. Defect Density defects/KLOC Measures defect density per phase (CR, IT, ST, AT, Post-delivery), real-time Defect Detection Rate defects/KLOC Measures defect rate per phase (IT, ST, AT, Post-delivery), organizational wide Effort Breakdown / Effort per Task Type hours Effort breakdown in hours per task nature Sprint Velocity SP, Hours Measures work throughput in a given Sprint. Not comparable between Teams since baseline US are different , as well as the SP assigned to those. Project Size LOC Task Completion % Measure total effort planned + discovered in a Sprint, VS the effort completed / resolved.
  • 10. 10© COPYRIGHT 2014 CRITICAL SOFTWARE • Peoples Mindset! • Highly specialized resources and roles ... • A prestigious and widely recognized Agile Champion would have helped ! • Too many markets (>8), too many different project types, and too many different technologies! • Projects lasting from 2 months to 3,5 years.. • Teams are geographically distributed, normal to have members in 3 locations! How’s a CMMI5 Agile SW Development project in Critical Software? -> Problems Faced! CMMI5AgileSWDev
  • 11. © COPYRIGHT 2014 CRITICAL SOFTWARE Délio Almeida, Quality Manager, CMMI and Agile Adopter