(Phoenix Project 1st way) Flow
|
|
|
|
|
|
|
(Phoenix Project 2nd way) delivery of better value & frequency of delivery / feedback from the customer
|
|
|
|
|
|
|
(Phoenix Project 3rd way) experimentation / learning organization
|
|
|
|
|
|
|
Ability to handle 1000s of people or avoiding need to
|
|
|
|
|
|
|
Ability to handle 100s of people or avoiding need to
|
|
|
|
|
|
|
Agendashift Outside In (across team boundaries)
|
|
|
|
|
|
|
Agendashift Right To Left
|
|
|
|
|
|
|
Agendashift Upside Down
|
|
|
|
|
|
|
Alignment
|
|
|
|
|
|
|
Alignment
|
|
|
|
|
|
|
Autonomy
|
|
|
|
|
|
|
Compatibility with portfolio approach or avoidance of need for it
|
|
|
|
|
|
|
Cooperation
|
|
|
|
|
|
|
Emergence
|
|
|
|
|
|
|
Flexibility for method choice of team
|
|
|
|
|
|
|
For people who need rules
|
|
|
|
|
|
|
Labour liquidity of teams / tendency towards multi-learning
|
|
|
|
|
|
|
Single Backlog or better / Systems Thinking
|
|
|
|
|
|
|
Speed of adoption
|
|
|
|
|
|
|