Slide 1

Slide 1 text

Dr. Klaus Leopold web: www.LEANability.com blog: www.klausleopold.com mail: [email protected]
 twitter: @klausleopold Skalieren mit Kanban Lean DUS, 19. Oktober 2015, Düsseldorf, DE

Slide 2

Slide 2 text

www.LEANability.com @klausleopold SW Development Project • SW development project, ~200 people - project management - 1 PRM, 5 PMs - 1 product team - 8 business and marketing representatives - 5 business analysts, 3 architects - 10 dev teams, ~120 people - 4 web teams, 2 iPhone teams, 1 Android team, 
 1 shop team, 2 backend teams - 3 QA teams, ~35 people - 2 OPS teams, ~25 people • Main dissatisfactions: - Bad coordination of the whole project WHAT WOULD YOU DO?

Slide 3

Slide 3 text

www.LEANability.com @klausleopold In an agile organization all teams use agile methods.

Slide 4

Slide 4 text

www.LEANability.com @klausleopold Team Dynamic Systems Development Method Scrum Kanban Extreme Programming Adaptive Software Development Agile Unified Process Crystal Feature Driven Development Lean Software Development Scrum-ban

Slide 5

Slide 5 text

www.LEANability.com @klausleopold Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team am Team Team Team Team

Slide 6

Slide 6 text

www.LEANability.com @klausleopold Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team Team An organization is not a container of independent teams!! Team am Team Team Team Team

Slide 7

Slide 7 text

www.LEANability.com @klausleopold team 1 team 2 team 3 team 4 customer wish: write a love letter

Slide 8

Slide 8 text

www.LEANability.com @klausleopold customer wish: write a love letter

Slide 9

Slide 9 text

www.LEANability.com @klausleopold The performance of a system is not the sum of its parts. It’S the product of its interactions. — Russell Ackoff

Slide 10

Slide 10 text

www.LEANability.com @klausleopold Agility of an organization is not having a lot of agile teams. It’s having agile interactions between teams.

Slide 11

Slide 11 text

www.LEANability.com @klausleopold Team 1 Team 2 Team 3 Team 4 CUSTOMER

Slide 12

Slide 12 text

www.LEANability.com @klausleopold Team 1 Team 2 Team 3 Team 4 active time wait time CUSTOMER time

Slide 13

Slide 13 text

www.LEANability.com @klausleopold Team 1 Team 2 Team 3 Team 4 active time wait time CUSTOMER time

Slide 14

Slide 14 text

www.LEANability.com @klausleopold photo by www.autobild.de Do not optimize single parts of a system!

Slide 15

Slide 15 text

www.LEANability.com @klausleopold SW Development Project • SW development project, ~200 people - project management - 1 PRM, 5 PMs - 1 product team - 8 business and marketing representatives - 5 business analysts, 3 architects - 10 dev teams, ~120 people - 4 web teams, 2 iPhone teams, 1 Android team, 
 1 shop team, 2 backend teams - 3 QA teams, ~35 people - 2 OPS teams, ~25 people • Main dissatisfactions: - Bad coordination of the whole project Focus on optimizing how to create value and do not optimize organizational structures!

Slide 16

Slide 16 text

www.LEANability.com @klausleopold AND HOW?? KANBAN!!

Slide 17

Slide 17 text

@klausleopold www.LEANability.com Practices of Kanban Principles of Kanban 1. Start with what you do now 2. Agree to pursue improvement through evolutionary change 3. Encourage acts of leadership at every level in your organization 1. Visualize 6. You’re allowed to think! 2. Limit Work In Progress 3. Manage Flow 4. Make Policies Explicit 5. Implement Feedback Loops

Slide 18

Slide 18 text

www.LEANability.com @klausleopold 1. FOCUS ON VALUE CREATION —-> What are your services? —> How are you creating value? 2. FIGURE OUT WHOM YOU NEED —> teams, departments, etc.—- > it’s not about local optima START AS BROAD AS YOU CAN —> Use the leverage if you can! —-> whole PROJECT in this example

Slide 19

Slide 19 text

www.LEANability.com @klausleopold Build a hierarchy-bridging and cross-functional change team. program manager, project manager(s), team delegates build a Kanban system together

Slide 20

Slide 20 text

www.LEANability.com @klausleopold define B-epics develop & test integrate & test run user acc. tests roll-out prog. version concretize idea rough idea split epics

Slide 21

Slide 21 text

www.LEANability.com @klausleopold define B-epics develop & test integrate & test business & marketing 2 ops teams 10 dev teams run user acc. tests roll-out 5 BAs & 3 Arch prog. version concretize idea rough idea 3 QA teams split epics

Slide 22

Slide 22 text

www.LEANability.com @klausleopold idea doing approved int. (24) concretize idea (12) define B-epics (20) in development (8) review B-epics (10) ready for dev rejected (∞) ready for int (1) test (1) ready to roll (1) roll out DONE (4) NEXT epic program version integration every Monday release every Wednesday Kanban on project level doing done doing done UAT

Slide 23

Slide 23 text

www.LEANability.com @klausleopold It’s not “mandatory” that (all) teams do KANBAN!! LET TEAMS PULL CHANGE! We only started KANBAN on project level That’s also a perfect way to organize work for multiple SCRUM teams

Slide 24

Slide 24 text

www.LEANability.com @klausleopold task story (5) develop (∞) int. test (∞) UAT (2) waiting 4 EPIC epic define Task Stories (4) NEXT (1) review epic READY 2 ROLL Kanban on team level This part of the board is POTENTIAL DEMAND for the team! Epic 1 + Task Stories Epic 2 + Task Stories (5) test doing done

Slide 25

Slide 25 text

www.LEANability.com @klausleopold Coordination • Project stand-up, twice per week - 2 program management delegates - 3 delegates from the solution team - 5 delegates from the dev teams - 3 delegates from the QA teams - 1 delegate from the OPS teams • Team stand-ups - Dev teams, daily - QA teams, twice per week - OPS teams, twice per week • Improvement meetings - each Dev, QA, and OPS team, 2-weekly to 4-weekly cadence - Program retro, monthly cadence

Slide 26

Slide 26 text

www.LEANability.com @klausleopold Flight Level 1: Isolated team/service, uncoordinated input Do Something Smart DONE Flight Level 4: Portfolio Product A Product B Project X Project Y Biz-Analyze Org-Architect Realization Integration Roll-Out Flight Level 3: Value stream, multiple connected teams/services DONE Flight Level 2: Single team/service, coordinated input Split Develop Review DONE The Kanban Flight Levels

Slide 27

Slide 27 text

www.LEANability.com @klausleopold Scalability in Kanban simply means doing real Kanban at any scale in your organization! I don’t know how each and every company on this planet works most effectively! But we can figure it out for yours!

Slide 28

Slide 28 text

LEANability GmbH | Grundlgasse 5/11 | A-1090 Wien o f f i c e @ L E A N a b i l i t y. c o m | + 4 3 6 7 6 3 3 0 4 8 0 3 www.LEANability.com | facebook.LEANability.com www.bit.ly/kcl-wiley 25% off promo code VBJ24 EXTRA: E-Book inside klaus LEOPOLD KANBAN VOM TEAMFOKUS ZUR WERTSCHÖPFUNG in der Praxis www.bit.ly/kanbaninit-v2 to appear in May 2016