Uploaded byHolly Green
Case Study: How to scale agile
The document summarizes how REI scaled agile practices across multiple teams and divisions. It describes adopting techniques from the Scaled Agile Framework (SAFe) including establishing portfolio vision, architectural runway, and agile release trains. This helped improve coordination, reduce waste, and better support business strategy. Key changes included aligning product owners to prioritize backlogs and conduct quarterly release planning. While improvements were made, opportunities remain to enhance reporting on progress and facilitating work across teams.
More Related Content
Similar to Case Study: How to scale agile
Case Study: How to scale agile
- 1. How to Scale Agile HollyGreen Principal Business Analyst, REI November 2013
- 2. “If you wanta kitten, start out by asking for a horse.” - Naomi, age 15
- 3. Holly Green • PrincipalBusiness Analyst, Recreational Equipment Inc. (REI) • 13+ yrs. Software Industry experience • Advisory Board Member, University of Washington Certificate in Business Analysis Program • Focus on Portfolio Management
- 4. Objectives • Identify andbridge gaps in planning • Scale agile using techniques from SAFe1 • Build partnerships for success 1Scaled Agile Framework (SAFe) is an approach to software development developed by Dean Leffingwell for leveraging agile at scale. Visit www.scaledagileframework.com.
- 5. The situation • 3years iterating on Agile Portfolio Management • Expanded Portfolio Management from one person to 5 teams • 6 Ecommerce Agile Teams • 100+ people involved
- 6. We were herdingcats!
- 7. Situation Statement immature communication channelsbetween numerous large divisions and competing views on how to best address We are impeded by our size with business strategy. Technical resources are constrained. As a result, our efforts are uncoordinated, inefficient, and lack the full power of our combined talents. Our opportunity is to establish a process that can support agile at scale, reduce waste, and enable us to better execute against business strategy.
- 8. The Inspection • ‘Connectthe dots’ team initiated • After 3 years we were: Successfully using kanban to visualize Business demand Able to quickly turn away low value propositions Able to recognize and delay requests that would be blocked by dependencies • But… We weren’t meeting our commitments We weren’t always doing the right work to support Business strategy POs didn’t have enough visibility into the portfolio to make accurate planning decisions Portfolio Planning teams weren’t communicating well SME resource constraints inhibited knowledge transfer
- 9. The adjustment • DiscoveredScaled Agile Framework (SAFe) – Helps us meet our goals to: • Establish scaled agile release planning process • Execute to support Business Strategy • Reduce waste Scaled Agile Framework
- 10. What we did •Leveraged techniques from SAFe1 – Portfolio Vision – Architectural Runway – Agile Release Train – Release Planning • Focused on roles and process 1www.scaledagileframework.com
- 11. Started at theProgram Level Portfolio Program www.scaledagileframework.com Team
- 12. Agile Release Train •Quarterly release planning off sites • To prepare: – Aligned Product Owners with the Business – POs work with the Business to prioritize Team Backlogs • Use Weighted Shortest Job First (WSJF)1 – Identify Minimal Marketable Features to release value • Produce a list of top opportunities and redline at estimated capacity 1www.scaledagileframework.com/wsjf/
- 13. Release Planning inAction GOAL: Examine opportunities across teams to detect conflicts, dependencies, and risks. Make necessary adjustments to address discoveries. Create a plan.
- 14. Planning Together Doesn’t leave communication tochance Produces plans we believe in! Empowers everyone with more knowledge Ensures Business voice is heard Makes dependencies & risks visible
- 15. Adding on thePortfolio Level Portfolio Program www.scaledagileframework.com Team
- 16. Our Portfolio wasOverwhelming
- 17. Portfolio: More thana list of requests • Key Initiatives map to investment themes and strategies • To support the vision, we: – Synchronize Portfolio Management to Enterprise Planning – Leadership communicates the plan • Progress is tracked quarterly – Architectural Runway supports the Portfolio – Incidentals go directly to teams • If it doesn’t support enterprise strategy… – It can’t be in the Portfolio Backlog
- 18. Keep on Track •Intake Process: – Raise the price of admission • Single entrance point • Stricter requirements
- 19. The Price ofAdmission
- 20. Manage Change • ‘Spike’for more information – Plan time to learn • • • • • Understand scope Reduce risk Uncover impediments Reduce waste Make commitments with confidence
- 21. Now that scaleis accounted for… Our cats are more aligned
- 22. Areas of Opportunity •Improve report-out on progress and changes to plan • Better plan how to facilitate work that crosses multiple teams
- 23. Could you dothis? • Consider: – How you could partner across the enterprise – How you could leverage the right mix of skillsets to make quick decisions and address impediments to success • Keys to success: – – – – Leadership support Accept change and its discomforts Expect an iterative process This is about a framework • We adapted SAFe to work for us • You will adapt techniques to work for you
- 24. Recap • What aresome of the ways we can identify gaps in our planning processes? • What are some techniques for Portfolio planning improvement in a constrained environment? • What are some ways to Boost portfolio planning transparency and communication between Technology and the Business?
- 26.
Editor's Notes
- #3 Have you ever seen your stakeholders use tactics like this?!
- #4 Holly Green has more than 13 years’ experience in the software industry and is a Principal Business Analyst with Recreational Equipment Inc. (REI). Her BA career has focused on work for leading ecommerce retailers with heavy involvement in Portfolio Management for the past 6 years. She currently serves on the Advisory Board for the University of Washington Certificate in Business Analysis Program. Holly is passionate about using her BA skills to help the enterprise successfully manage its portfolio by assessing business strategy, value, risk, and dependencies.
- #5 Today we will focus on ways in which we can accomplish the above 3 objectives.
- #6 Expanded from one person managing the Ecommerce Portfolio to 5 teams that moved requests from intake through to execution5 Teams for Portfolio Management:Portfolio Steering Committee (Focused on ‘What’)Provide leadership priorities and direction for portfolio mix and resourcesPortfolio Planning (Focused on ‘What’)Vet requestsApprove or deny based on ratification criteriaInitial architecture assessmentPrioritize requestsDevelop quarterly portfolio proposalPortfolio Execution (Focused on ‘What’)Breakdown epics and featuresMake program backlog commitmentsDevelop release plansDeliver valueEIE Planning (Focused on ‘How’)Lead and influence continuous improvement of people practices and technology to drive value:Engineering practicesContinuous deliveryIncrease productivityEnvironment NeedsEmployee EngagementAlign on goalsFeature Delivery Increase release frequencyImprove qualityReduce defectsDevelop metricsEIE Execution (Focused on ‘How’)Process improvementRelease and build; release calendar go/no-go evaluationEnvironment supportTest process improvementTeam staffingImpediment resolution
- #9 ‘Connect the dots’ team initiated to:Examine agile and portfolio planning needs4 P’s exercise: Prerequisites, Preparation, Participation, PayoffIdentify gaps in the agile processIdentify topics for leadership supportMake a recommendation on how to establish alignment across the leadership, business, and technology teamsAfter 3 years we were:Successfully using kanban to visualize Business demandAble to quickly turn away low value propositionsAble to recognize and delay requests that would be blocked by dependencies – setting expectations early onBut…We weren’t meeting our commitments (not enough slack to absorb variation and enable fast flow = traffic jam)We weren’t always doing the right work to support Business strategyPOs didn’t have enough visibility into each other’s release plans (the portfolio) to make accurate planning decisions (especially when cross-team dependencies came into play)The 5 teams weren’t communicating well with each other or with the Agile teamsSME resource constraints – weren’t leveraging SME skillsets appropriately so that knowledge transfer could occur
- #10 Discovered SAFeHelps us meet our goals to: Establish scaled agile release planning processExecute to support Business StrategyReduce waste:Reduced number of teams involved in managing intake and prioritization
- #11 These techniques sound fairly standard until you start to consider how they get executed at scale.
- #12 Typically, a bottoms-up approach is recommended for SAFe implementation. We had our teams in place and they were working well. We had a Kanban Portfolio backlog (not mapped to Investment Themes and far from perfect, but something to start with). So, we started at the Program Level.
- #13 WSJF = Cost of Delay / DurationCost of Delay = Business Value + Time Criticality + Value of Risk Reduction or Opportunity EnablementLeverage Minimal Marketable Features to release value quickly while maintaining a cadence for longer-term business investment themes.Opportunity list is the foundation for a team’s quarterly plan.
- #14 Attendees: Business RepresentativesAgile teamsDevelopersArchitectsProduct OwnersBusiness AnalystsScrum MastersQAResource ManagersTechnical and Business Leadership
- #16 Adding the Portfolio level is the greatest challenge: Direction and governance should come from leadership driving the enterprise business strategy and technology investment strategy. Financial constraints need to be accounted for.The stakes are high and the variables are numerous.
- #17 Requests were big and smallRequests ranged from maintenance and compliance to edgy ideasRequests were not clearly mapped to Business strategyBusiness priority for requests was not clear
- #18 Key Initiatives outlined by leadership map to enterprise investment themes and strategiesTo do this, we:Synchronize Portfolio Management to Enterprise PlanningLeadership responsible for communicating the plan and keeping the teams tracking to the planQuarterly planning marches to the mapArchitectural Runway supports the mapIncidentals go directly to the teams – they don’t muddle the big pictureFeatures, Quick Fixes, Campaigns, Tech Debt, Maintenance, and Compliance flow directly to POs
- #21 When direction changes…Share Spike example
- #23 Our cats are more aligned, but we still have room for improvement:Improve report-out on progress and changes to planPlan how to facilitate work that crosses multiple teams – especially when there is no clear owner
- #25 Ask the audience and write down:What are some of the ways we can identify gaps in our planning processes?What are some techniques for Portfolio planning improvement in a constrained environment?What are some ways to Boost portfolio planning transparency and communication between Technology and the Business?