ELEC5618 · Software Quality Engineering
Designing an Agile Cycle & Process Improvement
Week 11 of University of Sydney ELEC5618 Software Quality Engineering designs a weekly agile cycle and reconciles agility with process maturity: hybrid models, the key considerations for adopting Agile alongside CMM/CMMI, and continuous process improvement using SPICE/CMMI. It connects the agile and standards threads before the case studies, and is a Week-11 milestone-check week.
What this chapter covers
- 01Designing a short (one-week) agile increment: users and developers together, minimal documentation, TDD, end-of-week demo and pair programming
- 02CMM/CMMI maturity levels: 1 Initial → 2 Repeatable → 3 Defined → 4 Managed → 5 Optimizing
- 03CMM idea: improve quality by gaining statistical control of processes; SCAMPI appraisal as a certification/marketing signal
- 04CMM criticisms: can reward paperwork over management, focuses on management processes not product quality, heavy documentation
- 05Agile vs CMM comparison: adaptability, documentation weight, small releases, pair programming, continuous integration
- 06Hybrid models: can Agile and CMM co-exist for safety-critical software (e.g. flight control)?
- 07Continuous process improvement with SPICE (ISO/IEC 15504) and CMMI
- 08CMMI in practice (e.g. NASA class-based maturity requirements): Process + People + Technology → reduced risk, higher quality
Identifying an organisation's CMM maturity level and its next step
- +1Match the description to a level: standardised, documented, communicated and consistently followed processes across the organisation is the hallmark of Level 3 Defined.
- +1Rule out neighbours: it is beyond Level 2 Repeatable (which has basic, repeatable project management but not org-wide standardisation), and it is not yet Level 4 Managed, because Level 4 requires statistical/quantitative control of process and product quality — which the organisation explicitly lacks.
- +1State the next step: to reach Level 4 Managed it must introduce quantitative, statistical control — collect process and product-quality metrics and set measurable customer-satisfaction and defect targets, then manage against them.
- +1Note the trajectory: Level 5 Optimizing would then add continuous process improvement driven by that quantitative data. Beware the CMM criticism that certification can reward documentation over genuine management improvement.
Key terms
- CMM/CMMI maturity levels
- Five levels of process maturity: 1 Initial (ad-hoc), 2 Repeatable (basic, repeatable project management), 3 Defined (standardised, documented, communicated processes), 4 Managed (statistical process/product-quality control with quantitative targets) and 5 Optimizing (continuous process improvement).
- SCAMPI appraisal
- The appraisal method used to certify an organisation's CMMI maturity level. Certification acts as a management and marketing signal, though critics warn it can reward paperwork over genuine improvement.
- Hybrid model
- A lifecycle that blends agile adaptability with the control and documentation of a maturity model such as CMM, used to ask whether agile and heavy process can co-exist for safety-critical software (e.g. a flight-control system).
- Agile vs CMM
- A contrast across dimensions: agile gives more control to adapt to changing requirements, documents only as required, favours small releases and pair programming and continuous integration; CMM offers less adaptability, rigorous documentation, defined up-front structure and no reliance on small releases or pairing.
- Continuous process improvement
- Ongoing refinement of the development process, associated with CMM/CMMI Level 5 (Optimizing) and supported by SPICE (ISO/IEC 15504) and CMMI, using data to drive incremental gains rather than one-off fixes.
- One-week agile cycle
- A short increment completable in a week: users and developers work together, documentation is minimal (source docs plus an end-of-week user doc), TDD keeps code working, and the week ends with a customer demo against acceptance criteria.
Designing an Agile Cycle & Process Improvement FAQ
What are the five CMM/CMMI maturity levels?
Level 1 Initial (ad-hoc, unpredictable), Level 2 Repeatable (basic project management, repeatable on similar projects), Level 3 Defined (standardised, documented, communicated processes across the organisation), Level 4 Managed (statistical control of process and product quality with quantitative targets) and Level 5 Optimizing (continuous, data-driven process improvement). The key jump to remember is 3 → 4: from standardised processes to quantitatively controlled ones.
Can Agile and CMM co-exist?
That is exactly the hybrid-model question the unit poses. They pull in different directions — agile favours adaptability, small releases, pair programming and light documentation, while CMM favours defined up-front structure, statistical control and heavy documentation — but for safety-critical software (like a flight-control system) you may want both the adaptability of agile and the control and traceability of a maturity model, so you design a hybrid lifecycle that balances the two.
What are the criticisms of CMM?
That certification can reward producing paperwork over genuinely improving management, that it focuses on management processes rather than the quality of the product itself, and that it imposes heavy documentation. This is part of why agile arose as a counterweight — and why hybrid models try to keep the control benefits without the bureaucracy.
Can AI help me with process maturity and improvement?
Yes. Sia can quiz you on the five CMM/CMMI levels, help you place an organisation at the right level with justification, and talk through the agile-versus-CMM trade-offs and hybrid models. Use it to rehearse the frameworks; it does not do graded assessment, and the University of Sydney academic-integrity policy applies.
Exam move
Commit the five CMM/CMMI levels to memory with a one-line marker for each, and drill the 3 → 4 boundary (standardised processes become statistically controlled ones with quantitative targets), because placing an organisation at the right level is a classic scenario task. Build an Agile-vs-CMM comparison table across the examined dimensions (adaptability, documentation, small releases, pair programming, continuous integration) and be ready to argue a hybrid model for safety-critical software. Be able to sketch a one-week agile cycle (planning Monday, TDD through the week, Friday demo). Because this is a milestone-check week that ties the agile and standards threads together, use it to consolidate both before the case studies. Confirm the exam format on Canvas.
Working through Designing an Agile Cycle & Process Improvement in ELEC5618? Sia is AskSia’s AI Software Engineering tutor — ask any ELEC5618 Designing an Agile Cycle & Process Improvement question and get a clear, step-by-step explanation grounded in how ELEC5618 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
