The Amplio Approach to Value Improvement

Amplio takes the following approach:

1. Identifying symptoms
2. Analyzing these symptoms to determine a diagnosis.
3. Identifying targeted areas for improvement.
4. and only then Create a plan of action 

Let’s go through a common problem I see in SAFe adoptions as an example.

Symptoms: The biggest problems in most Agile at scale adoptions are too much work in play due to:

1. Too many new functions started
2. Too many things in play at one time
3. Discovering new requirements for committed features late in the game
4. Ineffective planning – critical people not available when needed
5. Working on things that aren’t the most important
6. People working on several things at once

Analysis: The result of this is:

1. Multi-tasking, lowering overall efficiency
2. Too much work in process across the value stream
3. Delayed feedback which slows feedback and has people work on what we later know is not important
4. Teams getting out of synch which increases the time in testing and integration.

Targeted Improvement: To get out of this situation requires:

1. Having a focus on finishing things quickly at release level
2. Managing work in process at all levels of the value stream
3. Getting requirements in a way that has getting later detail not cause significant extra work
4. Alignment across the value stream so delays in the workflow are minimal. This allows for quicker feedback and lower-cost correction
5. Having all the necessary capabilities to complete a project and make it available for release as needed.
6. Improved planning