Adopting SAFe with JIRA
8 likes•7,117 views
This webinar discussed how a company called AcademicText.com transitioned from early Scrum adoption at the team level to implementing the Scaled Agile Framework (SAFe) across multiple teams. It began with Scrum training and using Jira for individual teams. Issues with coordination and dependencies between teams led to adopting SAFe. Key aspects discussed included: - Aligning teams into Agile Release Trains (ARTs) organized by value streams - Planning at the program level using a portfolio backlog, epics, and features - Conducting SAFe release planning meetings over two days to develop the program increment plan - Tracking progress through metrics like feature completeness and release burndowns - Managing the
Adopting SAFe with JIRA
- 2. 2! SCALED AGILE FRAMEWORK (SAFe®) USING JIRA
- 3. 3! AFTER THE WEBINAR… We will send directions to collect the PDU you will earn from attending this webinar! ! We will also send a links to the recorded webinar and presentation slides once they are posted online! ! Submit your questions in the chat box at any time and! We will address them after the presentation! ! For more information, visit www.cprime.com! !
- 4. 4! Today’s Presenter Sue Shreve – cPrime Agile Coach! • Experienced enterprise Agile Coach and trainer focusing on large scale transformations using the Scaled Agile Framework (SAFe)! • Over 25 years in software development in a range of industries and companies, from startups to large applications vendors. Extensive background in Product Management! • Assisted in enterprise Agile transitions at Greendot, LG Electronics, Philips Medical, Greenplum! • Certified Scaled Agile Framework (SAFe) Program Consultant (SPC) Certified Scrum Professional (CSP), Certified Product Owner (CSPO), Certified Scrum Master (CSM) ! • Strong expertise in coaching. Completed courses through the Agile Coaching Institute! • M.S. Mechanical Engineering, Stanford University! !
- 5. 5! Migrations, Add-Ons, Licensing, Training, Optimization and more Atlassian, VersionOne, AgileCraft, Innotas and more Contract to Hire, Consulting, Full- time, Executive Search and more ScrumMasters, Product Owners, Scrum Coaches and more Transformations, Scaling, Assessments, Planning, Coaching, Training, Advisory Services, Change Management and more Who is cPrime?
- 6. 6!
- 7. 7! Webinar Objectives At the Webinar completion you will ! ! Understand a typical path to adoption of the Scaled Agile Framework, through an example! ! See how Jira supports the Scaled Agile Framework process! !
- 8. 8! Agenda • AcademicText.com – Early Agile Adoption with JiraAgile! • Moving to the Scaled Agile Framework! • Launching an Agile Release Train – JiraAgile with SAFe Add-ons!
- 10. 10! Scrum Adoption – Team Focus Scrum Adoption – Team Level! ! Trained:! Development, ! Product Management and ! Executive Management on Scrum! Jira Agile – Out of the Box! ! Teams formed,! !Jira Agile deployed,! ! !Sprints began…! ! Team transformation in progress….! ! !
- 11. 11! Jira Team Backlog Show a backlog!
- 12. 12! Uncoordinated Teams…Program Level Issues… Dependencies between teams! Lack of coordination of release features! Unpredictably long integration and test cycles, late delivery ! Release quality issues! Visibility of feature progress! Unrealistic plans, plans that change mid-stream ! Don’t know how to set up JiraAgile for multiple teams! !
- 13. 13! Part 2: Scaled Agile Framework
- 14. 14! POLL QUESTION Where would you classify the status of your SAFe Adoption?
- 15. 15! A Way Forward Alignment, Dependencies,! Transparency, Quality!
- 16. 16! Aligning Team Structure Around Value Component Teams… ! !are organized around the architecture of the system focusing !on reliable, scalable reusable components! ! Feature Teams…! !are cross functional teams that complete customer features !end-to-end with the advantage of simplified planning, i.e. no !complicated tracking across multiple teams, reduced waste, !increased throughput)!
- 17. 17! The Agile Release Trains Text Book eCommerce (5 teams) Learning Management System (4 teams) Pla<orm/ Common Components (1 team) Program Increment Next Program Increment LMS ART eCommerce ART
- 18. 18! Pick a date to start, do some training Pick a date for the! ART Launch! ! SAFe Training:! Leading SAFe! SAFe ScrumXP! Scrum Master! Product Owner! ! SAFe ART Launch Kit! !
- 19. 19! POLL QUESTION Are you interested in SAFe Training?
- 20. 20! New Roles ! ! ! Sell Books – 5 teams Pla7orm – 1 teams
- 21. 21! Addressing Integration ! Continuous Integration and system test.! Integration is shared between the System Team and the Agile Teams.! ! System team:! Execute end to end performance testing! System Integration! Development infrastructure! System Demo!
- 22. 22! Planning the PI Customer/Value Stream Feedback Program Backlog NFRs Program Epics Vision Roadmap Product Management Team Inputs Arch. Strategic Themes PortfolioBacklog NFRs
- 23. 23! Planning - Portfolio to Program Portfolio Backlog! Create a Presence with Open Education Resources LMS ART Create Course from Open Textbook Open College Textbooks in Catalog Professor Reviews eCommerce ART
- 24. 24! Planning - Portfolio to Program The AcademicText Portfolio Backlog:! ! ! ! ! ! The eCommerce Program Backlog! ! ! ! ! ! ! !
- 25. 25! Ranking Features Rank Features by “Weighted Shortest Job First”! WSJF = User Value + Risk Reduction/Oppty Enablement + Time Criticality! Job Size! !
- 27. 27! Grooming Release Features and Stories with the Team
- 28. 28! Part 3: The Release Planning Meeting Day 1! Day 2! Communicate Business Context, ! Product and Architecture Vision! Finalize the Plan! ! Draft Plan and Adjustments! Addressing Risks, ! Commitment ! Morning!Afternoon!
- 29. 29! Sample Day 1 Agenda 8:00–! 9:00 9:00–! 10:30 1:00–! 4:00 5:00–! 6:00 10:30– 11:30 4:00–! 5:00 11:30–! 1:00 ! State of the business and upcoming objectives ! Vision and prioritized features ! Architecture, common frameworks, etc. ! Agile tooling, engineering practices, etc. ! Facilitator explains planning process ! Teams present draft plans, risks, and impediments ! Teams develop draft plans and identify risks and impediments ! Architects and Product Managers circulate ! Adjustments made based on challenges, risks, and impediments 1! 2! 3! 4!
- 30. 30! Sample Day 2 Agenda 8:00–! 9:00 9:00–! 11:00 11:00–! 1:00 ! Planning adjustments made based on previous day’s management meeting ! Teams present final plans, risks, and impediments ! Teams develop final plans and refine risks and impediments ! Business Owners circulate and assign business value to team objectives 2–2:15 1:00–! 2:00 ! Remaining program-level risks are discussed and ROAMed ! Team and program confidence vote After Commitment 2:15–! ??? ! If necessary, planning continues until commitment is achieved ! Retrospective ! Moving Forward ! Final Instructions ! 1! 2! 3! 4! 1! 2! 3! 4!
- 31. 31! Sprint 1.1 Sprint 1.2 Sprint 1.3 Sprint 1.4 Sprint 1.5 PI OBJECTIVES RISKS Velocity: 34 Load: 30 Velocity: 34 Load: 30 Velocity: 34 Load: 30 Velocity: 34 Load: 30 Velocity: 34 Load: 0 ObjecLves / Business Value 1. …. 2. …. 3. …. Stretch ObjecLves 1. …. IP Sprint X For velocity, use historic informaNon or 8 x (number of developers + testers) Be sure to adjust for holidays and vacaLon. Velocity (Capacity): ____ Load: ____ Team Deliverables
- 33. 33! Managing the Release ! Executing the Program Increment:! Teams Execute on the Stories! Frequent integration! Conduct Scrum of Scrums, Manage dependencies! Conduct Release ! Mgmt meeting! Conduct System Demo! Report metrics! Release on Demand! Build Architectural Runway!
- 34. 34! Metrics – Feature Complete and Release Burn Down Percent Feature Complete: !
- 37. 37! THANKS FOR JOINING!! ! ! Be on the look out for our follow up email!! ! ! ! Want more? Contact [email protected]!