Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

10 Essential SAFe(tm) patterns you should focus on when scaling Agile

384 views

Published on

Scaling agile can be overwhelming. In this tutorial, Yuval will provide an overview of the ten essential SAFe patterns, and highlight the diagnostic symptoms that appear when the patterns aren’t in place. Attendees will develop a personal “flash assessment” of their current work context and will be able to identify to “inspect and adapt” areas for improvement. They will also learn how to use this sort of assessment/patterns during their scaled agile journey.

(This includes the Essential SAFe assessment toolkit provided by ScaledAgile)

Published in: Business
  • Hello! Get Your Professional Job-Winning Resume Here - Check our website! https://vk.cc/818RFv
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

10 Essential SAFe(tm) patterns you should focus on when scaling Agile

  1. 1. © Scaled Agile, Inc. @yuvalyeret #leanagileus© Scaled Agile, Inc. 10 Essential SAFe(TM) patterns you should focus on when scaling agile – Yuval Yeret @yuvalyeret #leanagileus
  2. 2. © Scaled Agile, Inc. @yuvalyeret #leanagileus #BuildBridges
  3. 3. The Agile Theater Starring Scrum, The Scrum Master, Product Owner, Agile Team, The Sprint. Guest Appearance – The Waterfall 3
  4. 4. The SAFe Theater Starring the Managers-Only PI Planning, The Command & Control RTE, w/ special guest - The Waterfall Thinking 4 @yuvalyeret #leanagileus
  5. 5. Why? See Kent Beck’s idea as described by Markus Gartner at http://www.shino.de/2010/11/04/software-g-forces-the-effects-of-acceleration/ @yuvalyeret #leanagileus
  6. 6. 6 The Law of Raspberry Jam: the wider any culture is spread, the thinner it gets. Alvin Toffler @yuvalyeret #leanagileus
  7. 7. © Scaled Agile, Inc. @yuvalyeret #leanagileus Introducing the Essential SAFe configuration...
  8. 8. © Scaled Agile, Inc. @yuvalyeret #leanagileus Start with the basics of Essential SAFe ...
  9. 9. © Scaled Agile, Inc. @yuvalyeret #leanagileus Apply the ten Essential SAFe elements SAFe Lean-Agile Principles Real Agile Teams and Trains Cadence and Synchronization PI Planning DevOps and Releasability System Demo Inspect & Adapt IP Iteration Architectural Runway Lean-Agile Leadership 1 2 3 4 5 6 7 8 9 10
  10. 10. © Scaled Agile, Inc. @yuvalyeret #leanagileus Ways to use Essential SAFe 4Diagnose/Repair artificial/theater SAFe Implementation 4Boost Agility at Scale using some core ideas from SAFe 4Interesting way to introduce SAFe to people already practicing agile at some level https://www.scaledagileframework.com/essential-safe/ 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1
  11. 11. © Scaled Agile, Inc. @yuvalyeret #leanagileus © 2016 Scaled Agile, Inc. All Rights Reserved. 5.12© Scaled Agile, Inc. Exercise: Essential SAFe Self-Assessment 4Fill out the Essential SAFe Self-Assessment on the next page 4Use the previous slides to identify the symptoms that exist in your enterprise 4For each Essential SAFe element, shade one box for every symptom identified 10 min Example
  12. 12. © Scaled Agile, Inc. @yuvalyeret #leanagileus Anchor the transformation with Lean-Agile Principles #1-Take an economic view #2-Apply systems thinking #3-Assume variability; preserve options #4-Build incrementally with fast, integrated learning cycles #5-Base milestones on objective evaluation of working systems #6-Visualize and limit WIP, reduce batch sizes, and manage queue lengths #7-Apply cadence, synchronize with cross-domain planning #8-Unlock the intrinsic motivation of knowledge workers #9-Decentralize decision-making 1
  13. 13. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without a shared understanding of principles ... There is no systematic way to adapt practices to local context Business outcomes do not significantly improve Practices and measures that were once beneficial become problematic Lean-Agile Mindset is unachievable Conflict and disagreement on processes and practices are difficult to resolve
  14. 14. © Scaled Agile, Inc. @yuvalyeret #leanagileus Implement Real Agile Teams and Trains Agile Teams power the train: Cross-functional teams apply Scrum, XP and Kanban and Built-in Quality practices to produce working system increments every iteration. 2 Cross-functional Agile Teams and trains work towards a common mission and operate with architectural and Lean UX guidance. Agile Release Trains (ARTs) apply systems thinking and build a cross-functional organization optimized to facilitate the flow of value from idea to release.
  15. 15. © Scaled Agile, Inc. @yuvalyeret #leanagileus Critical Agile Team roles Well defined roles empower teams and trains. Scrum Master facilitates team events, drives Agile behavior, and coaches the team Product Owner acts as the customer for the team and prioritizes their work. Defines and accepts stories. Development Team is everyone needed to define, build, and test an increment of value
  16. 16. © Scaled Agile, Inc. @yuvalyeret #leanagileus Release Train Engineer acts as the chief Scrum Master for the train Business Owners are a small group of stakeholders who have financial, governance, fitness for purpose and ROI responsibility Product Management is responsible for customer needs. Owns the vision and product backlog, prioritizes features for the best economic outcome System Architect/Engineering align ARTs to a common technological and architectural vision Customer consumes the work of an ART. They are the ultimate deciders of value Critical ART roles
  17. 17. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without Real Agile Teams and Trains ... Vision and requirements are not clear and prioritization is extremely difficult No architectural and user experience integrity; solution features and components evolve incompatibly Teams locally optimize and can’t deliver end-to-end value Responsibilities are unclear; delayed decision-making The skills needed to define, build, test and deliver value are not fully present and accountable. Over-specialization and bottlenecks inhibit flow.
  18. 18. © Scaled Agile, Inc. @yuvalyeret #leanagileus
  19. 19. © Scaled Agile, Inc. @yuvalyeret #leanagileus Apply Cadence and Synchronization 4 Transforms unpredictable events into predictable events 4 Makes wait times predictable 4 Facilitates planning; provides more efficient use of resources 4 Synchronization causes multiple events to happen at the same time 4 Sync events facilitate cross-functional tradeoffs of people and scope 3
  20. 20. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without Cadence and Synchronization ... No development rhythm Gradual decline into disorder and lack of predictability It’s hard to schedule planning, retrospectives, demos and other key events Teams are constantly overloaded Difficult to adjusting to changing priorities
  21. 21. © Scaled Agile, Inc. @yuvalyeret #leanagileus Create alignment with PI Planning No event is more powerful than PI planning. It’s the magic in SAFe—the alignment and energy created in just two days saves months of delays. 4 All stakeholders face-to-face, whenever possible 4 Management sets the mission with minimum possible constraints 4 Important stakeholder decisions are made immediately 4 Requirements and design emerge 4 Teams create and take responsibility for plans 4
  22. 22. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without PI Planning ... Stakeholders, teams, and management are not aligned Demand doesn't match capacity; no predictability; excess WIP Lack of trust between stakeholders and teams Late discovery of dependencies cause delays Low commitment, ownership, and employee engagement
  23. 23. © Scaled Agile, Inc. @yuvalyeret #leanagileus 5 Improve DevOps and Releasability DevOps improves collaboration and flow between Development and IT Operations with a continuous delivery pipeline.
  24. 24. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without DevOps and Releasability... Value delivery is seriously delayed Reduced quality of deployments and high production defects More frequent releases are not possible, increasing time to market Large batches of code are pushed to production, resulting in production errors, and emergencies Friction between development and operations limits collaboration, learning, and cultural change
  25. 25. © Scaled Agile, Inc. @yuvalyeret #leanagileus Get fast feedback with the System Demo Demonstrate the full system increment to stakeholders every iteration 4Features are either functionally complete or ‘toggled off' 4New features work together, and with existing functionality 4Demo from a production-like staging environment Full system increment System Team 6
  26. 26. © Scaled Agile, Inc. @yuvalyeret #leanagileus Producing a System Demo requires Built-in Quality “You can’t scale crappy code” (or hardware, or anything else) Built-in Quality: 4Ensures that every increment of the solution reflects quality standards 4Enables high velocity and a sustainable development pace 4Software practices include continuous integration, test-first, refactoring, pair-work, collective ownership, and more 4Hardware practices include exploratory iterations, frequent system integration, design verification, model-based systems engineering, and set-based design Built-in Quality
  27. 27. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without the System Demo ... Teams are ‘sprinting’, but the system is not Chronic lack of trust between stakeholders and teams Lack of feedback to iterate to the right solution False progress and poor quality ‘Waterfalled PIs’—problems and risks are discovered too late
  28. 28. © Scaled Agile, Inc. @yuvalyeret #leanagileus Relentlessly improve with Inspect & Adapt Inspect & Adapt (I&A) supports systematic review of PI outcomes and continuous improvement. 7 PI System Demo Quantitative measurement Problem-Solving Workshop
  29. 29. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without Inspect & Adapt ... No systemic improvement; problems persist No means to measure or establish delivery predictability Improvement efforts address symptoms, not root causes Leaders who could change the system are not engaged Low morale
  30. 30. © Scaled Agile, Inc. @yuvalyeret #leanagileus Dedicate time for Innovation and Planning The IP Iteration provides an estimating buffer for meeting PI objectives, and dedicated time for innovation, education, PI planning and I&A events. 8
  31. 31. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without the IP Iteration ... Lack of estimating buffer and poor predictability ‘Tyranny of the urgent’ iteration inhibits innovation Technical debt grows uncontrollably Lots of overtime and people burn out No time for teams to plan together, demo together, and improve together
  32. 32. © Scaled Agile, Inc. @yuvalyeret #leanagileus Enable fast feature delivery with Architectural Runway Architectural runway provide ‘just enough’ technical enablement to keep velocity high and avoid excessive redesign and delays. … to support future features Implemented now … Feature Feature Feature Enabler 9
  33. 33. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without Architectural Runway ... Architecture progressively decays under the ‘urgency of now’ Velocity peaks for a while, then falls off Infrequent and irregular releases Solution robustness, maintainability, and quality decay Unsustainable development pace
  34. 34. © Scaled Agile, Inc. @yuvalyeret #leanagileus Lead with Lean-Agile Leadership Successful transformations are based on educating leadership first. ‘Lean-thinking manager-teachers’ lead, rather than follow the transformation. “It is not enough that management commit themselves to quality and productivity … They must know what it is they must do. Such a responsibility cannot be delegated.” —W. Edwards Deming 10
  35. 35. © Scaled Agile, Inc. @yuvalyeret #leanagileus Without Lean-Agile Leadership ... Teams cannot learn from their leaders The transformation is fatally impaired Agile development with traditional governance results in ‘Agile in name only’ Constantly escalating decisions increases lead time People not allowed to experiment, fail, innovate, and learn
  36. 36. © Scaled Agile, Inc. @yuvalyeret #leanagileus One more thing, without Lean-Agile Leadership ... SAFe will not work!
  37. 37. © Scaled Agile, Inc. @yuvalyeret #leanagileus © 2016 Scaled Agile, Inc. All Rights Reserved. 5.38© Scaled Agile, Inc. Exercise: Essential SAFe Self-Assessment 4Fill out the Essential SAFe Self-Assessment on the next page 4Use the previous slides to identify the symptoms that exist in your enterprise 4For each Essential SAFe element, shade one box for every symptom identified 10 min Example
  38. 38. © Scaled Agile, Inc. @yuvalyeret #leanagileus Essential SAFe Self-Assessment 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 5 4 3 2 1 Lean-Agile Principles Real Agile Teams and Trains Cadence & Synchronization PI Planning DevOps and Releasability System Demo IP Iteration Architectural Runway Lean-Agile Leadership Inspect & Adapt No.ofSymptoms Essential SAFe Elements
  39. 39. © Scaled Agile, Inc. @yuvalyeret #leanagileus Ways to use Essential SAFe 4Diagnose/Repair artificial/theater SAFe Implementation 4Boost Agility at Scale using some core ideas from SAFe 4Interesting way to introduce SAFe to people already practicing agile at some level https://www.scaledagileframework.com/essential-safe/ https://www.agilesparks.com/services/agile-boosts/
  40. 40. © Scaled Agile, Inc. @yuvalyeret #leanagileus© Scaled Agile, Inc. 41 Questions? Yuval@AgileSparks.com

×