Team Design:
How effectively does the design of our teams enable FLOW?
Pre-Crawl (1-2): We have not intentionally designed our teams to enable flow of business outcomes. We have high dependencies, long wait queues, limited experts, misaligned priorities and not all the right roles within the teams. It's painful to coordinate delivery of business outcomes.
Crawl (3-4): We have invested in designing cross-functional teams with the core mix of roles, however, they still struggle to deliver a complete User Story within an iteration.
Walk (5-6): Our teams are cross-functional and able to deliver stories (end-to-end) each iteration. However, we still have high cross-team dependencies and coordination to get features completed.
Run (7-8): We've organized our team of teams layer (train) so that teams can plan together and deliver a quarterly outcome and related features. Teams are engaged directly with product leaders who own the outcomes.
Fly (9-10): We've included business operations teams at the team of team or portfolio levels that are needed for full outcome delivery. This optimized team design has increased flow of value / outcomes and reduced lead time.
Pre-Crawl: 1-2 | Crawl: 3-4 | Walk: 5-6 | Run: 7-8 | Fly: 9-10