When I started writing up Net Objectives’ 14 years of experience in Agile at scale that has now become FLEX I came from a foundation of the following:
- FLEX itself is an hypothesis of the best way for an organization to have a customer realize value. As an hypothesis, it should be continuously tested, validated and improved.
- How people react to FLEX must be considered to be part of FLEX (this is a basic tenet of systems thinking, albeit often ignored by most frameworks)
- FLEX must both attend to how to provide a well-defined start and how to extend the start
- It must be based on the value stream so that it doesn’t inadvertently do sub-optimization
- Technical skills must be included in the system and should be considered when deciding on a starting point
- Although users will extend FLEX you never transcend it in the sense that what it’s based on is always valid. People will just come up with more innovative methods to use known principles
FLEX has been designed to grow and evolve. It attempts to be as explicit about its methods as possible so that we can examine the tenets on which it is founded. Its foundations enable adding more information and insights without adding complexity
FLEX also incorporates four shifts in thinking:
- shifting from frameworks to the work itself
- focusing on flow
- attend ro organizational development with Lean.