Not afraid of the SAFe big bad wolf - Yuval Yeret
•Download as PPTX, PDF•
4 likes•261 views
Not afraid of the SAFe big bad wolf - Yuval Yeret
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Not afraid of the SAFe big bad wolf - Yuval Yeret
Similar to Not afraid of the SAFe big bad wolf - Yuval Yeret (20)
More from agilemaine
More from agilemaine (20)
Recently uploaded
Recently uploaded (20)
Not afraid of the SAFe big bad wolf - Yuval Yeret
- 1. Agile Maine Day 2017 – Yuval Yeret
- 2. About Me
- 3. Is SAFe really safe?
- 4. http://www.scaledagileframework.com/ What are your biggest fears about SAFe?
- 5. “A Hard-coded Agile Framework isn’t Agile and hardly a Framework”
- 6. SAFe is Linear and is not fit for dealing with the Complex Domain Dave Snowden
- 7. “SAFe is like putting Lipstick on a Pig”
- 8. SAFe is “RUP reborn in Agile clothes”
- 9. “not only a betrayal of the promise offered by AGILE but is a massive retrograde step giving the managerial class an excuse to avoid any significant change” Dave Snowden
- 10. You get the picture… Let’s move to my perspective…
- 14. My take on a SAFe value statement… For Early/late majority software/IT/technology-heavy enterprises who Develop and maintain LARGE COMPLEX products or services the Scaled Agile Framework is a Collection of lean/agile process and implementation best practices that Helps these enterprises improve their business agility despite huge change management and technology/process obstacles in their context Unlike Other scaling frameworks that assume the ability and willingness to drive revolutionary dramatic change in the organization and mostly ignore current culture and roles in the organization our solution Is able to provide a reasonable evolutionary starting point to the business agility journey flexible enough to allow organizations to evolve towards a truly lean/agile enterprise. It provides people currently holding roles in the organization a clear mapping to their new role in the agile enterprise and a path to making this change.
- 15. Start with what you have Respect People & Process Evolutionary Change Challenge the comfort zone in a pragmatic small-batch way. Crazy talk???
- 18. The SAFe Theater Starring the Managers-Only PI Planning, The Command & Control RTE, w/ special guest - Waterfall Thinking 18
- 19. 19 The Law of Raspberry Jam: the wider any culture is spread, the thinner it gets. Alvin Toffler
- 20. With great power comes great responsibility
- 21. Scaling Agile Practices is hard and dangerous without changing leadership mindset
- 22. SAFe is getting us face time to discuss Lean/Agile principles and practices with Leaders LEADERSHIP Respectfor peopleandculture Flow Innovation Relentless improvement VALUE
- 23. Worried about the RUP/Prince awakening? Make sure your SAFe consultants hail from the Lean/Agile/Flow community…
- 24. Worried about force-feeding a hard-coded methodology?
- 25. SAFe Invitations Implementation Approach Roadmap Consider SAFe Train Lean/Agile Change Agents • Implementing SAFe w/ SPC (Internal/External) Train Executives, Managers, Leaders • Leading SAFe for enterprise leaders Figure out how to implement SAFe across the enterprise • SAFe Implementation workshop Create overall implementation elevator pitch and blueprint Invite Leaders to go SAFe • Optional - Additional Leading SAFe + Implementation workshops Figure out how to Go SAFe in an ART/VS – • Leading SAFe • SAFe implementation workshop Prepare for ART Launch • SAFe PM/PO – Train + Make key decisions • SAFe Scrum Masters – Train + Make key decisions Train Teams and Launch ART • SAFe for Teams – Train + Make key decisions at team level + ROAM implementation risks • PI Planning Coach ART Execution Launch more ARTs/VSs • as more leaders accept the invitation Sustain and Improve
- 26. Use a “SAFe Implementation Strategy Workshop” http://bit.ly/ImplSAFe 8:00- 9:00 9:00- 10:30 1:00- 4:00 10:30- 11:30 4:00- 5:00 11:30- 1:00 R O A M
- 27. • Some of the fears are grounded and some are a result of misperceptions or agile community clashes • If you NEED to Scale agile in a mainstream follower organization - Use Real/Genuine Agile DNA + Lean/Agile Principles + Leadership to SAFely scale agile • Best way to dispel the fear? See healthy SAFe in action. • Next best thing? Take a good Implementing SAFe 4.0 class from a Lean/Agile/Flow- oriented SPCT… Yuval@AgileSparks.com @YuvalYeret
Editor's Notes
- Let’s demystify the Scaled Agile Framework and a lot of the FUD (Fear, Uncertainty and Doubt) going around about it. Let’s explore when and why SAFe can be useful, What’s unique about it compared to other approaches to scaling, what is causing all the bad publicity and how can we make sure we implement it effectively if we decide it’s right for us.
- OVERVIEW: In this slide, you can explain that, at first glance, the Framework may appear complicated. However, you can provide assurance that you will take them through it in a logical manner. SAMPLE SPEAKER NOTES: This is what is referred to as the “SAFe Big Picture”. At first, it may look complicated, but as we will see, it is actually a very straight-forward and logical representation. We will see that roles, artifacts, and activities are clearly defined based on proven principles and practices. Decomposing the SAFe Big Picture into it’s constituent parts, we’ll discover that it’s a simple, powerful and easily understood framework for managing complex software and systems development.
- We don’t want to commit to completing these, because we don’t know how large they may be. Epics are large, typically cross-cutting customer-facing initiatives that encapsulate the new development necessary to realize certain business benefits. Thus, we don’t have a definition of done. Instead, we are interested in getting them to the point of “done enough”, then we move on to the next thing. We want to get the most value out of them with the least amount of effort. Epics have “success criteria”.
- OVERVIEW: In this slide, you can explain that, at first glance, the Framework may appear complicated. However, you can provide assurance that you will take them through it in a logical manner. SAMPLE SPEAKER NOTES: This is what is referred to as the “SAFe Big Picture”. At first, it may look complicated, but as we will see, it is actually a very straight-forward and logical representation. We will see that roles, artifacts, and activities are clearly defined based on proven principles and practices. Decomposing the SAFe Big Picture into it’s constituent parts, we’ll discover that it’s a simple, powerful and easily understood framework for managing complex software and systems development.
- Finally, let's discuss implementation. We'll describe that using our Implementing SAFe 1-2-3 model. Number 1 is to train the Lean-Agile change agents. We call those SAFe Program Consultants. With a sufficient staff of Lean-Agile change agents onsite, and working with your partners, you'll have the ability to train the executives and leaders and managers—the people responsible for managing the people who deliver value. They'll then be in a position to support the launch of the Agile Release Trains. And one train at a time, you'll build that Agile portfolio.
- Start with Why Lean/Agile/SAFe here Something between Foundations/Leading SAFe and the AgileSparks Management Focusing Workshop* Lots of context-specific discussion mapping SAFe to the VS/ART They PULL the kind of SAFe they can commit to as a VS/ART leadership team Key Objectives/Deliverables Establish Need/Goals for Enterprise Agility through exploration of pains/opportunities in current way of doing things Establish what SAFe means applied to the organization - What will be our Portfolios? Value Streams? Trains? Who will fill which roles? Do we need 3-level or 4-level SAFe? What will be our Epics? Capabilities? Features? Stories? What should be our Release Cadence? How do we fit SAFe into our current governance context? The bigger organization? Partners? Customers? (Dealing with waterfall/phase gate/CMMI/etc.) Review and learn from applicable case studies for SAFe / Scaled Agile. Explore complementary practices required to successfully implement SAFe in the specific organizational context, e.g.: Technical Safety Sustainable Pace Lean/Agile Requirements in a world of uncertainty - Minimum Viable Products (MVPs), Minimum Marketable Features (MMFs), Requirement slicing techniques, Lean Startup thinking. Combining Scrum and Kanban into ScrumBan AgileSparks Way Approach to Change ManagementAgile Testing Approaches Is SAFe SAFE here? Create and review a draft blueprint, explore and deal with risks until a high-confidence plan surfaces.