Transcription
Scaling Agile @ LegoOur journey so farkeynote, Lean Tribe GatheringConsultantwww.crisp.seStockholm, Oct 13Henrik Agile & Lean coachAuthor
Scaled Agile Framework Big PictureHenrik Kniberg
Source: http://www.smbc-comics.com/?id 2475
Agile ”umbrella” –a family of iterative, incremental methodsSAFe(Scaled Agile Framework)ScrumXPKanbanHenrik KnibergDSDMFDDCrystal
This doesn’t scaleWTF!Huh?!?!Hey!!Henrik Kniberg#@%&?!
Scaled Agile FrameworkPortfolio Kanban SystemFunnelPORTFOLIO cBusiness casePROGRAM LEVELProgram backlogAgile Release TrainProduct Increment8-12 weeksFeatureReleasableTEAM LEVELScrum TeamTeam backlogStoryTestableHenrik KnibergSprint2-3 weeksIP sprintInnovation & planning
Pattern: 2-tier planningMonthsWeeksHenrik KnibergWeeksWeeksWeeks
Pattern: Plan on a cadence, release on demandRelease 1.0PlanningeventRelease 1.2.1Release 2.0Release 1.2Release 1.1PlanningeventReleasecandidatesHenrik KnibergReleasecandidatesPlanningevent
Example:PI-planning @ LegoHenrik Kniberg01:32
2 days, 19 teams, 150 peoplePurpose: Alignment!Side effect: Lots of collaboration in generalHenrik Kniberg
PI4 demo video – what did we accomplish?Henrik Kniberg
Lightning talksFeedback & DataHigh level priorities:1. .2. .3. .Architecture vision / priorities / constraintsDigital Child SafetyHenrik KnibergGlobal InsightsData Privacy Law
Fast feedbackHenrik Kniberg
Team breakoutsfeels like an open spaceHenrik KnibergLaw of 2 feet.
Team breakout: Pulling from the program backlogHenrik Kniberg
Team breakout: Pulling from the program backlog(digital version)HenrikKnibergHenrikKniberg
Team boardHenrik Kniberg
Team boardan alignment ”poster” that is iteratively created during the 2 daysHenrik Kniberg
A commitment is only valid if made voluntarily!(pull, not push!) “Based on what we know right now, we honestly believe that wecan fulfill this.”. “We have spare capacity to deal with uncertainties” How much spare capacity is needed? Depends on: How uncertain are we about the amount of work involved? How uncertain are we about our environment (changing prios, etc) How important is this commitment? “We will do our best to achieve the commitment, but we can’t be100% sure.” “If we at any time stop believing that we can fulfill this,we will let stakeholders know ASAP”.Henrik Kniberg
Draft plan ”fair”4 presentation rounds: 10 min 10 min 5 min 5 minVisit the teams that interest you.Nobody wants to know all team’s plans.But most people want to know a few team’s plans.Henrik Kniberg
Program Board(a.k.a Dependency Board)Who needs what from whom, and when?Henrik Kniberg
Early detection of dependency problemsA centralized view to enable decentralized behaviourHenrik Kniberg
Scrum of ScrumsHenrik Kniberg
Risk board(per project/epic)Henrik Kniberg
Management review / problem solvingManagers sync up and take ownership of escalated risksHenrik Kniberg
Day 2Management feedback & commitment to helpHenrik Kniberg
Day 2Presenting the “final” planBooooring!TODO: Change to the “fair” modelHenrik Kniberg
Day 2Henrik KnibergConfidence votingMeh.TODO: Skip or change
Mini-retro: Improving the PI planningHenrik Kniberg
Most peoplelike the eventSome don’t . But theyhave concreteproposals for how toimprove it.HenrikKnibergHenrikKniberg
Benefits observed so farAwareness ofchangeMore flexiblebudget processImproved TransparencyBetter interface with otherdepartmentsTeams handle their own“resource allocation”Henrik Kniberg & Lars RoostPrioritiesmore clear!I add morevalueMomentum
Main challenge: Release train getting too bigAnd many more challenges of course.but all in all the approach seems to be working.Henrik Kniberg
The journey has just begun Early wins are causing Agile to spread to other parts of LegoPhotobyYoryoGarcíaHenrik Kniberg & Lars Roost
LEGO astronaut flying in space. Photo taken inside the ISS.Thanks for listening!Credits: ESA/NASA
SAFe (Scaled Agile Framework) Agile ”umbrella” – a family of iterative, incremental methods Scrum XP DSDM FDD Crystal Kanban Henrik Kniberg . Henrik Kniberg WTF!?!?! #@%&?! Hey!!? This doesn’t scale. Scaled Agile Framework Henrik Kniberg Scrum Team Tea m backlog Story Testable Sprint 2-3 weeks Program backlog PROGRAM LEVEL TEAM LEVEL PORTFOLIO LEVEL Product Increment 8-12 weeks Agile .
