Throwing Out the Agile Rulebook
2 likes1,195 views
The document discusses agile project management practices, focusing on portfolio management, release planning, and team synchronization within the Scaled Agile Framework. Key topics include the creation and management of epics and user stories, ensuring predictability and visibility in large projects, and the use of tools like Jira for efficient collaboration among teams. Overall, it emphasizes the need for coordinated efforts and strategic planning to enhance project outcomes.
Throwing Out the Agile Rulebook
- 1. Throwing out the Agile Rulebook LUISA RANDON • SR AGILE PROJECT MANAGER• AMGEN
- 2. Agenda SAFe or not SAFe Portfolio Management Release Planning Tools
- 4. SAFe or not SAFe
- 6. Scaled Agile Framework™ Big Picture!
- 7. Speaking the same LanguageadKeep or discard? Strategic Themes Themes Business and Architecture Epics Epics, Initiatives Business and Architecture Features Epics Stories Stories Agile Teams Product Owners Chief Scrum Master (Release Train Engineer) Scrum Masters DevOpsArchitects Product Managers (Group Product Owners)
- 8. SAFe but Simple Portfolio Management Product Roadmap Release Planning Scrum work
- 10. Product Council Review Product Managers Create Epics PMs Cross- prioritize Epics Product Owners break down Epics into User Stories User Stories groomed planned into Sprints Everybody can create a Portfolio Request Epics will be visible by Stakeholders and every body else in the Portfolio Kanban board
- 11. Watchers To Do In Progress Closed Portfolio Program Board
- 12. When stakeholders have smaller requests!
- 13. Requestors (Watchers) get notified at every change Reviewed Reviewed by PM/PO daily Story in JIRA and in Requests Board Open Groomed by the Team Ready In Progress In Sprint Delivered Closed JIRA customized for stakeholders to enter small requirements
- 14. Release Planning and Scrum Work
- 15. Becoming predictable while “Develop on Cadence and Deliver on Demand” Release PlanningSynchronized Sprints Normalized Story Points 1 3 8 2 5 13
- 16. 3 Good Reasons to synchronized sprints across teams Sprints Calendar should be available to everybody Planning Dependencies Transparencies Release Planning
- 17. Useful for Large Estimation Might Help to convert Story Points into Cost Same value shared across the different teams (1 point = 1 ideal day)Story Points Normalization Many Epics across several teams Story points
- 18. Align Business and Development More than one Sprint at the same time Release Planning or how to forecast your Product Increment All teams planning together
- 19. TEAM 1 TEAM 2 TEAM 3 TEAM 4 TEAMS User stories extracted automatically
- 20. Tools, next step
- 21. Tools, next steps…Portfolio for JIRA Operations Better view of higher level business Requirements (Initiatives and big Epics)
- 22. Think of Agile as a Tool Box Give visibility into your entire process Choose the right tools Lessons Learned
- 23. Luisa Randon• Sr Agile Project Manager• Amgen – lrandon@amgen.com Thank you!