Captain Agile Eik Thyrsted Brandsgård. Dr Agile Henrik Kniberg. Passion for Projects Uppsala, 14 March 2016

Transcription

1 Passion for Projects Uppsala, 14 March 2016 Captain Agile Eik Thyrsted Brandsgård Dr Agile Henrik Kniberg

2 Context & Problem 16:45 01:32

3 You are here

4 Consumer Marketing Agency

5 Digital Solutions

6 Family owned

7 Growth

8 Going Digital

9 Portfolio level stable yearly process, budget frames, long term planning Program level lots of meetings, spreadsheets, stress, and confusion Product Owner Project manager Product director Tea m level Scrum teams doing sprints

10 Example: PI-planning 16:50 01:32

11 Planning as a social event Product Increment planning Happens every 2 nd month

12 2 days, 20 teams, 150 people Purpose: Alignment!

13 Agile umbrella a family of iterative, incremental methods SAFe (Scaled Agile Framework) DSDM FDD Scrum XP Crystal Kanban Henrik Kniberg

14 Scaled Agile Framework (simplified...) PORTFOLIO LEVEL Funnel Review Analysis Portfolio Kanban System Portfolio Backlog Implementing Epic Business case PROGRAM LEVEL Program backlog Agile Release Train Product Increment 8-12 weeks Feature Releasable TEAM LEVEL Scrum Team Tea m ba cklog Story Testable Sprint 2-3 weeks Henrik Kniberg

15 Pattern: 2-tier planning Months Weeks Weeks Weeks Weeks

16 Pattern: Plan on a cadence, release on demand Planning event Release Release 1.0 Release 1.1 Release 1.2 Planning event Release 2.0 Planning event Release candidates Release candidates

17 PI4 demo video what did we accomplish?

18 Lightning talks Feedback & Data High level priorities: Architecture vision / priorities / constraints Digital Child Safety Global Insights Data Privacy Law

19 Fast feedback

20 Team breakouts Law of 2 feet...

21 Team breakout: Pulling from the program backlog

22 Team breakout: Pulling from the program backlog Tea m 1 Program backlog PULL PULL Tea m 2 Tea m backlog Tea m backlog Tea m 3 Tea m backlog

23 Team breakout: Pulling from the program backlog (digital version)

24 Team board

25 Team board

26 Team board Load < 100% Tea m ca pa city (story points & yesterday s weather ) Impact-based PI objectives Stretch objectives Risks

27 Draft plan fair 4 presentation rounds: 10 min + 10 min + 5 min + 5 min

28 The old way: Presented ALL plans Stopped doing this. And our plan is bla bla bla bla

29 Program Board (a.k.a Dependency Board)

30 Early detection of dependency problems A centralized tool to enable decentralized behaviour

31 Scrum of Scrums

32 Risk board (per project/epic)

33 Management review / problem solving

34 Risk board (per project/epic) Risk backlog Resolved has been addressed, no longer a problem Owned Someone has taken responsibility for this (who?) Accepted We ll take our chances Mitigated We have a plan for how to deal with this (reduce likelihoodor damage)

35 Management review / problem solving

36

37 Next morning... Management feedback & commitment to help

38 Day 2 = more of the same (break-out planning & review & discussions)

39 Mini-retro: Improving the PI planning

40

41 Impact & results 17:10 01:32

42 Key Performance Indicators Happy Executives: Singing & Dancing Happy children: Net Promoter Score Happy customers: Survey / Hourly Rate Happy employees: Survey

43 Benefits reported Improved Transparency Agile Finance Employee satisfaction Awareness of change Better interface with other departments Teams handle their own resource allocation Priorities more clear! I add more value Momentum

44

45 Spreading seeds

46 How we got started 17:15 01:32

47 Exploring

48 Training

49 Leap of faith

50 Future 17:25 01:32

51 Portfolio Do the right thing Program Create Flow Tea m Do the thing right (and fast)

52 Demand - Capacity Demand Capacity Throughput

53 Help the teams improve

54 Roadmaps

55 Portfolio What to measure Effort Output Outcome

56 Cost of Delay

57 Sequence

58 Keep experimenting

59 Photo by Yoryo García The journey has just begun