is safe evil
play

Is SAFe Evil? Henrik Kniberg Lars Roost Hi! Lars Roost Henrik - PowerPoint PPT Presentation

Is SAFe Evil? Henrik Kniberg Lars Roost Hi! Lars Roost Henrik Kniberg Program Manager & Agile/Lean coach Agile Change Agent Is SAFe Evil? It depends.... Is SAFe Evil? No. To Tools ls, to , tools ls, to , tools ls Henrik Kniberg


  1. Is SAFe Evil? Henrik Kniberg Lars Roost

  2. Hi! Lars Roost Henrik Kniberg Program Manager & Agile/Lean coach Agile Change Agent

  3. Is SAFe Evil? It depends....

  4. Is SAFe Evil? No.

  5. To Tools ls, to , tools ls, to , tools ls Henrik Kniberg & Lars Roost

  6. Any tool can be misus used Henrik Kniberg & Lars Roost

  7. Scaled Agile Framework™ Big Picture

  8. SAFe in a nutshell 10:25 01:32

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

  10. SAFe in a nutshell Portfolio Kanban System Portfolio Implementing Funnel Review Analysis Backlog PORTFOLIO LEVEL Epic Business case PROGRAM LEVEL Agile Release T rain Product Increment Program backlog 8-12 weeks Feature Releasable TEAM LEVEL Sprint Scrum T eam T eam backlog 2-3 weeks Story T estable Henrik Kniberg

  11. Pattern: 2-tier planning Months Weeks Weeks Weeks Weeks Henrik Kniberg

  12. Pat Pattern ern: Pl Plan an on a a caden adence, e, rel releas ease e on dem deman and Release 1.2.1 Release 1.0 Release 1.1 Release 1.2 Release 2.0 Plan & sync Plan & sync Plan & sync Release Release candidates candidates Henrik Kniberg

  13. Example: PI-planning @ Lego 10:32 01:32

  14. Agenda for PI planning 5 8 weeks 2 2 2 2 Weeks Weeks Weeks Week Henrik Kniberg & Lars Roost

  15. An And d this is what it looks like: e: BI BIG Ro Room m planning BIG ¡ ¡ 2 day ays + + 140 0 peo eople e + + experi erimen ents, , experi erimen ents, , experi erimen ents…

  16. Af After er having been een her ere: e: Bi Big-is ish R Room oom p planning ing Very noisy, many left with a headache Not enough chairs For everybody ¡ ¡ Timing overlapped But we had funny hats! with important releases in some teams

  17. Day ¡1 ¡ Feedb eedback on pas ast per erform rmance More! I want MORE!!! Data: ¡ Henrik Kniberg & Lars Roost

  18. Day ¡1 ¡

  19. Day ¡1 ¡ Lightning talks High level priorities: Architecture vision / priorities / constraints 1. ... 2. ... 3. .... Global ¡Insights ¡ Digital ¡Child ¡Safety ¡ Data ¡Privacy ¡Law ¡ Henrik Kniberg & Lars Roost

  20. Day ¡1 ¡ Instant feedback on the event Henrik Kniberg & Lars Roost

  21. Day ¡1 ¡ T eam breakouts Law of 2 feet.... Can you help? Henrik Kniberg & Lars Roost

  22. Day ¡1 ¡ T eams pull features from common backlog Henrik Kniberg & Lars Roost

  23. Day ¡1 ¡ T eams pull features from common backlog v2 Henrik Kniberg & Lars Roost

  24. T eam boards Day ¡1 ¡ Henrik Kniberg & Lars Roost

  25. The Program Board Day ¡1 ¡ Dependency mapping by teams Notice any patterns? Scrum of Scrums Henrik Kniberg & Lars Roost

  26. Day ¡1 ¡ Risk Board (per major project/program epic) Henrik Kniberg & Lars Roost

  27. Day ¡1 ¡ Draft plan ”fair” 4 presentation rounds: 10 min + 10 min + 5 min + 5 min Henrik Kniberg & Lars Roost

  28. Day ¡1 ¡ Management review Henrik Kniberg & Lars Roost

  29. Day 2 Henrik Kniberg & Lars Roost

  30. Day 2 Henrik Kniberg & Lars Roost

  31. Day 2 Henrik Kniberg & Lars Roost

  32. Should the building instructions be followed? 10:42 01:32

  33. Shu Ha Ri Shu = Follow the rules Ha = Adapt the rules Ri = Ignore the rules SAFe = Shu-level scaling Henrik Kniberg

  34. Lego’s journey 10:45 01:32

  35. Focus on the basics Simplicity Collaboration Lars Roost

  36. So what to do with lots of them? NEXUS TM ¡Framework ¡ Disciplined ¡Agile ¡Delivery ¡ And many, many more… Lars Roost

  37. Lars Roost

  38. Lars Roost

  39. So what have we gained? T ransparen ency, , T ransparen ency, , T ransparen ency, , T ransparen ency, , T ransparen ency… Lars Roost

  40. “Solid” effects so far Sel elec ected ed answer ers to T T e eams handle “Ho How has as SA SAFe affec ected ed your r daily work rk?” “resource e allocation” 7 out of 10: T eam Priorities are clearer 6 out of 10: I add more value 3 out of 10: We spend less time on meetings 2 out of 10: We have less Work In Progress Increas ased ed pred edictab ability Lars Roost

  41. And it gives us so much more… Momen entum Aw Awaren eness of f cha change Inter erfaces agile e teams with water erfall IT dep dep. Lars Roost

  42. But ¡journey ¡has ¡just ¡begun… ¡ Photo ¡by ¡Yoryo ¡García ¡ ¡ Lars Roost

  43. The Good The Bad The Ugly 10:55 01:32

  44. Planning as a social event Dependency Board (aka Program Board) Risk Board Henrik Kniberg & Lars Roost

  45. Big Bang is risky Don’t get stuck in Shu Don’t swallow the whole elephant Don’t believe in Hype Watch out for Queues and Batches or Anti-Hype Henrik Kniberg & Lars Roost

  46. Source: http://www.smbc-comics.com/?id=2475

  47. Wrapup 11:05 01:32

  48. Take-away points • SAFe is a toolkit. Neither Good nor Evil. • SAFe is built on Lean & Agile principles. Thanks for listening! • SAFe = Shu-level scaling. • It’s big and detailed. Take the stuff you need only. • SAFe can be useful when you have: • A bunch of teams working on the same product • A bunch of teams working on different products, but have many dependencies. • Don’t get stuck in Shu. Experiment a lot! Henrik Kniberg & Lars Roost

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend