Choose Lean when
The main challenge is process efficiency, handoffs, waste or slow flow.
Methodology
Use the method that fits the programme.
We apply Lean, Agile and Waterfall techniques pragmatically. The right approach depends on uncertainty, governance, dependencies, users and the release environment.
Lean
Remove waste. Improve flow. Focus on value.
Lean thinking helps teams simplify processes, shorten feedback loops and focus resources on activities that contribute to outcomes.
01Identify value
02Map value stream
03Create flow
04Establish pull
05Improve continuously
Agile
Deliver incrementally and learn quickly.
Agile delivery is useful where requirements evolve, user feedback matters and teams can create value in working increments.
- Individuals and interactions over rigid process
- Working software over excessive documentation
- Customer collaboration over contract interpretation
- Responding to change over following a static plan
Waterfall
Control defined scope through clear stages.
Waterfall remains appropriate where requirements and approvals are stable, dependencies are sequential, and formal stage gates are important.
Requirements
Define scope, outcomes, stakeholders and acceptance expectations.
Design
Translate requirements into technical and operational designs.
Build & test
Implement, verify and prepare for deployment through controlled stages.
Deploy & support
Release, transition, operate and manage change with traceability.
Method selection
Methodology should reduce delivery risk—not create ceremony.
Many programmes benefit from a hybrid approach: formal governance and milestones around iterative design, engineering and user validation.
Choose Agile when
Requirements evolve and working increments can be validated frequently.
Choose Waterfall when
Scope, approvals and dependencies require strong sequential control.