Slide 1

Slide 1 text

Mapping Teams To Value Streams Val Yonchev

Slide 2

Slide 2 text

Value Stream Team Mapping Teams to Value Streams

Slide 3

Slide 3 text

Done! Done? Are we there yet?!

Slide 4

Slide 4 text

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?

Slide 5

Slide 5 text

Yeah, how is that different? Component teams Feature teams Delivery teams

Slide 6

Slide 6 text

Value Stream Team Mapping Teams to Value Streams

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

Complexity is too big for the team!

Slide 9

Slide 9 text

Complexity is too big for the team!

Slide 10

Slide 10 text

Complexity is too big for the team!

Slide 11

Slide 11 text

Complexity is too big for the team!

Slide 12

Slide 12 text

Done! Done? Are we there yet?!

Slide 13

Slide 13 text

Show me the Value Steam .. I’ll map the team

Slide 14

Slide 14 text

Value Stream Team Mapping Teams to Value Streams

Slide 15

Slide 15 text

What is really a value stream?

Slide 16

Slide 16 text

Think Mars

Slide 17

Slide 17 text

Think Mars

Slide 18

Slide 18 text

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?

Slide 19

Slide 19 text

Composable Applications

Slide 20

Slide 20 text

Think Automotive

Slide 21

Slide 21 text

Value Streams Multidimensional & Networked!!!

Slide 22

Slide 22 text

Consider the system (Fast Flow Of Value) People (Teams) Tech (Architecture) Process (SDLC)

Slide 23

Slide 23 text

Always start & end with the Customer

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

Value Streams & Customer Journeys Event Storming (light DDD) helps understand the Customer journey and how systems are designed to support it

Slide 26

Slide 26 text

Value Streams & Processes MBPM = Metric-Based Process Mapping

Slide 27

Slide 27 text

Fracture planes help divide complexity Business domain Regulatory Compliance Change Cadence Technology Risk Performance Isolation User Personas/Journeys Team Location

Slide 28

Slide 28 text

It is a journey. Iterate!

Slide 29

Slide 29 text

Thank you for listening! [email protected] linkedin.com/in/valyonchev book time with Val