Agile Scaling without Blueprints Track: On the Boundaries of Agile - PowerPoint PPT Presentation

Agile Scaling without Blueprints Track: On the Boundaries of Agile Goto, Berlin, 04-dec-2015 Stefan Roock stefan.roock@it-agile.de @StefanRoock

Scaling in the „good old days“™ ( ∼ 2005) 4 teams, 20-25 developers 13 teams, 65 developers from 3 companies from 3 companies

Just Scrum? Daily Scrum Scrum Master Sprint Review Product Owner Development Sprint Team Backlog Product Increment Sprint Vision Sprint Sprint Planning Retro- spective Product Backlog

Just Scrum+XP Pair Programming Continuous Daily Scrum Scrum Integration Master Sprint Test Driven Review Development Product Owner Development Sprint Collective Team Backlog Ownership Product Increment On-site Customer Sprint On-site Team Vision Sprint Sprint Planning Retro- spective Product Backlog

Scaling today

Agile in the Agile old days nowadays 2000-2005 At least we suck less. I have the greatest job 2 0 1 5 ever. t SAFe Deliver useful software LeSS every few weeks with DAD Scrum & XP. …

Agile in the Agile old days nowadays 2000-2005 W T At least we F ? suck less. I have the greatest job 2 0 1 5 ever. t Deliver useful SAFe software every LeSS DAD few weeks. …

Insanity?

Cargo Cult

Agile in the Agile old days nowadays C 2000-2005 a r g At least we o suck less. C u l I have the t greatest job 2 0 1 5 ever. t Deliver useful SAFe software every LeSS DAD few weeks. …

Culture and principles are more important than practices.

After years of research we discovered the secret ingredient for successfully scaling agile!

Secret ingredient for successful scaling Blueprint

Emergent structures with 
 the Agile Scaling Cycle Reduce dependencies Values and Coordinate principles Develop the teams organization

Agile Agile: Autonomous business focused Scaling Reduce teams that own their process. dependencies Cycle Values and Coordinate principles teams Develop the organization

X - Teams

Some practices for dependency reduction Beta Codex Market Product Product Owner Definition Extend team Sandboxing responsibility up-/ downstram Definition of Company Release Cadence Done Definition of Ready Open Allocation Team Missions Cross functional Teams Release Train Teams synchronized Sprints Continuous Delivery Technology Verticals Modularization low high Autonomy

Agile Scaling Reduce dependencies Cycle Values and Coordinate principles teams Develop the organization

Coordination practices Goal#1 Continuous Team Verløtung Integration shared Sprint Review Number of teams Visit Daily Scrums Portfolio/Program Kanban Task-Forces consultative individual decision Launch Pate Open Prio Meeting shared Release Scrum of Planning shared Sprint Scrums Planning Communities of Practice Hours Days Weeks Months Time horizon

Stefans Agile Scaling Maturity Model Number of coordination practices that aren’t needed (any longer)

Agile Scaling Reduce dependencies Cycle Values and Coordinate principles teams Develop the organization

Practices for organizational development organizational impediments Successful teams in Transition Transition team / agile organization Backlog Agile Center

Practices for organizational development Gemba shared Walks Retrospectives North Operations Review Star organizational impediments Successful teams in Transition Transition team / agile organization Backlog Agile Center PDCA Lean … Thinking Theory of Systems Constraints Open Spaces Thinking

Find structures matching your business …

Summary see also: scaledprinciples.org

Summary •Cultural change •Emergent structures •Inspect & adapt •Self organization •Team autonomy •Process ownership see also: scaledprinciples.org

More information Free ebook: http://bit.ly/JimdoStory Booklet about agile scaling (german) http://www.itagileshop.de/lesen/weitere-broschüren/luna/

Thank you for your attention! Feel free to contact me: Stefan Roock stefan.roock@it-agile.de Twitter: @StefanRoock