Flowtopia 2024 Mapping Team To Value Streams

This talk explores the 3 key cornerstones for achieving fast flow of value in engineering organizations - Decoupled Architecture, SDLC processes and team-of-teams organizational design to match the two others. We will look at a set of challenges and their solutions based on 10 years of experience in building high-performing engineering organizations, scalable platforms and complex technology products - from ML-enabled high-frequency trading in FSI through highly secure government digital services to complex automotive embedded systems. The talk demonstrates how a combination of a mix of concepts like Team Topologies, Metric-Based Process Mapping, Value Stream Mapping, Wardley Mapping, Domain-Driven Design, DevOps, create a framework for decision-making covering both the organizational design and technology design.

- High-performing organizations require a balanced approach combining a number of methods and practices which address the 3 cornerstones of fast flow of value - architecture, SDLC processes and team-of-teams design.
- Aligning an existing enterprise to value streams requires an iterative approach based on finding local optimums and further enhancements through sensing and responding, similar to the Simplex Algorithm in mathematics optimization.
- Value streams are a multi-dimensional system and require more than one method for its complete understanding and optimization.

Transcript

1. Mapping Teams To Value Streams Val Yonchev
2. Value Stream Team Mapping Teams to Value Streams
3. Done! Done? Are we there yet?!
4. IDK What is really a value stream? Does it matter what teams look like? We spent X months making product teams now this?! How many should we have?
5. Yeah, how is that different? Component teams Feature teams Delivery teams
6. Value Stream Team Mapping Teams to Value Streams
7. Team assigned to value stream? Business Domain Expertise End-to-End Capability End-to-End Responsibility Dunbar’s numbers Autonomy Product teams Funded for outcomes
8. Complexity is too big for the team!
9. Complexity is too big for the team!
10. Complexity is too big for the team!
11. Complexity is too big for the team!
12. Done! Done? Are we there yet?!
13. Show me the Value Steam .. I’ll map the team
14. Value Stream Team Mapping Teams to Value Streams
15. What is really a value stream?
16. Think Mars
17. Think Mars
18. What is really a value stream? Does LoB/BU = Value Stream? We spent X months making product teams now this?! How many should we have?
19. Composable Applications
20. Think Automotive
21. Value Streams Multidimensional & Networked!!!
22. Consider the system (Fast Flow Of Value) People (Teams) Tech (Architecture) Process (SDLC)
23. Always start & end with the Customer
24. Value Streams & Value Chains Wardley Mapping starts with the Customer, her needs. Then helps define boundaries as well as what to build, what to buy
25. Value Streams & Customer Journeys Event Storming (light DDD) helps understand the Customer journey and how systems are designed to support it
26. Value Streams & Processes MBPM = Metric-Based Process Mapping
27. Fracture planes help divide complexity Business domain Regulatory Compliance Change Cadence Technology Risk Performance Isolation User Personas/Journeys Team Location
28. It is a journey. Iterate!
29. Thank you for listening! val@teamtopologies.com linkedin.com/in/valyonchev book time with Val