What's In Amplio You're Not Likely to Find Elsewhere

It’s not how to be complete or purposefully incomplete. It’s how to disseminate useful information at the right time without overloading people

Almost all the challenges I see people discussing on LinkedIn are due to concepts/practices missing in Scrum & SAFe

Many of these concepts are discussed in our Amplio Development: The Path to Effective Lean-Agile Teams or Being an Effective Value Creation Coach: How to Help Create Success for All Stakeholders. Links in paragraphs following a topic indicates it is in the book referenced. (AD) and (BEVCC) referring to the appropriate book respectively. Others are in various workshops by Success Engineering.

Missing concepts

1. Minimum business increments (MBIs) provide a focus on delivering value soonest. (AD)
2. The idealized value stream is a Pareto approach to value stream mapping
3. The Analysis matrix can quickly analyze domains with many options. This assists order of implementation while avoiding duplicate
4. Focused solution teams enable efficient teams of 8-40 people working on one product. (AD)
5. How to increase innovation by attending to the unstated objectives of your clients
6. How people create their reality in their languaging & how to take advantage of this
7. Amplio Team Estimation is 4x faster than Planning Poker, gives better results, & works well in situations PP doesn’t. (AD)
8. Systems thinking provides a holistic view necessary to solve complex problems. (AD)
9. How to deal with the effects of complexity by attending to quick feedback. (AD)
10. Accumulated risk provides insights into how to manage work in process across all levels of work being done. (AD)

Flexibility

10. Have a simple start based on the needs of the client that can be further tuned to them as needed. (AD)
11. When & how to use timeboxing or flow. What to do when cross-functional teams are not appropriate. (AD)
12. Use kaizen or kaikaku as a change method
13. Create flexible improvement backlogs Vs roadmaps both to start & continue to improve. In the same way we don’t want big designs & plans for our products, we don’t want them for our improvement activities
14. Uses single, double, & triple-loop learning. Immutability is neither required nor desired. (AD)

Organization

15. Based on Flow, Lean, & the Theory of Constraints. Amplio is not a hybrid approach but is designed directly from reality. (AD)
16. Organized around the value stream to improve alignment while helping avoid local optimizations. (AD)
17. Uses Eli Goldratt’s (The Choice) Inherent simplicity – “If we dive deep enough, we’ll find that there are very few elements at the base – the root causes – which, through cause-&-effect connections, are governing the whole system.” (AD)
18. Structured as a pattern language enabling a flexible framework. Core options for implementation are provided with access to others as needed. (AD)
19. Scale-free methods enable you to start small & grow without abandoning what you’ve done

Amplio@MidScale

20. Focuses on Agile at scale. Not scaling Agile
21. Integrates a focus on stakeholder values a la Tom Gilb
22. Can wrap SAFe, make it simpler, & avoid its common stagnation