The document discusses different stages and states of adopting agile practices within an enterprise from a traditional waterfall model to a fully agile model. It shows how agile teams and programs can be integrated into traditional gates and phases over time through allowing internal releases, reducing dependencies between teams, and reducing formal gates and increasing governance. The final state discussed is a lean program with reduced gates and increased governance allowing for continuous agile releases.

1. Agile Enterprise Adoption and
Enterprise Stage Gates

2. Agile Continuum

3. Agile Enterprise Adoption

4. Waterfall Software Gates &
Phases
Charter Define Design Code Accept Integrate Release

5. Current State – Waterfall
1 2 3 4 5 6
Charter Design Spec Code Accept-Test System-Test GA
1 6
5
2
Traditional
Waterfall
3 4
Development
Phases and
Gates

6. State 1 – Agile Teams in "Flow"
1 2 3 4 5 6
Charter Design Spec Code Accept-Test System-Test GA
1 6
5
2
Agile Iterations 3 4
inside of
Traditional Gates

7. State 1/2 – Agile Teams in
Iteration "Pull"
1 2 3 4 5 6
Charter Design Spec Internal Release Accept-Test System-Test GA
1 6
5
2
Agile Internal
releases inside of
traditional gates 3 4

8. State 2 – Agile Team in release
"Pull"
1 2 5 6 7
1 6
5
2 3. 3.
Agile Team with 1 2
“n” Releases /4 /4
based on .1 .2
dependancy
needs

9. State 3 – Agile Program in release
"Pull"
1 2 5 6 7
1 6
5
2 3. 3.
Agile Program 1 2
with “n” Releases /4 /4
based on .1 .2
governance
needs

10. State 5 – Lean Program in
"Innovate"
1/ 5 6
2
Charter Agile Releases System-Test GA
1/ 5
Lean 2
Program with
reduced
gates and 3.
3. 3. 3. n/
increased
1 2 3 4.
governance
/4 /4 /4 n
/1 .2 .3