Downloaded 28 times
Uploaded byAtlassian
Scaling Agile in an Un-SAFe World
The document discusses the challenges and strategies of scaling Agile practices at DocuSign, emphasizing the need for alignment across geo-dispersed teams and effective release management. It outlines a structured quarterly planning process that incorporates both top-down and bottom-up planning to prioritize features and manage dependencies. Key elements include cross-organizational collaboration, capacity planning, and metrics to track progress in an evolving Agile environment.
More Related Content
Similar to Scaling Agile in an Un-SAFe World
Scaling Agile in an Un-SAFe World
- 1. KUNAL ARORA SENIOR PROGRAMMANAGER • DOCUSIGN Scaling Agile in an Un-SAFe World STEVE GRAYKOWSKI DIRECTOR, PROGRAM MANAGEMENT • DOCUSIGN
- 4.
- 5. Our Challenges • 30+Geo-Dispersed Teams • Multiple Release Trains • Responding to Changing Priorities • Dependencies • Common Nomenclature and Cadence
- 6. A Bit Un-SAFeToday • Normalized Story Points • Visualize WIP • Architecture Runway • Design Framework Locally Optimized • Business Value Based Priorities
- 7. Scaling to ServeGlobal Growth • Agile Principles, Teams & Roles • Synchronized Organizational Cadence • Release Trains • Top-Down Planning • Bottom-Up Planning & Execution
- 8. Capacity PlanningSales &Marketing Interlock Mission Based Roadmap Product Priorities Top-Down Planning – Quarterly Cadence Vision and Strategy Transparency and Alignment Most Valuable Features First Team Alignment
- 9. T-40 Days • Featureroast • High level priorities matrix T-30 Days • High level scope • Capacity planning • Release items for consideration T-7 Days • Bottom up planning • Final priorities • Target scope Quarterly Planning Timeline
- 10.
- 11.
- 12.
- 14. Bottom-Up Planning Quarterly PlanningIT,Legal, and Security Readiness UX Roast Feedback on Scope, Requirements and Designs Business Requirements! Scrum teams commit to sprint-by-sprint plan
- 15.
- 16. Bottom-Up Planning inthe Beginning…
- 17. Then it Evolved… Sprint12 Sprint 13 Sprint 14 Sprint 15 Sprint 16 Sprint 17 Team2Team3Team1
- 18.
- 19. Execution (Delivering theplan) Program ReviewsProduct CouncilScrum of Scrums Weekly status reporting with Leadership Open items from Scrum of Scrums! Program updates and dependency reviews
- 20.
- 21. Release Trains –Mission Control…
- 23. T-60 Days • Productmarketing alignment • Identify marketing opportunities T-15 Days • Deploy to demo • Customer testing T-10 Days • Product update & release notes • Demo Day (Internal) T-0 Days • Deploy to prod • Final release notes • Marketing launch Quarterly Release Process
- 24. What’s working well? • Cross-Org Planning • Better understanding of current processes and priorities • Metrics to track our progress
- 26. Evolution of ScaledAgile and SAFe • Portfolio for JIRA • Metrics – Information Radiators • Mission Centric Scrum of Scrums • Architecture Runway • Agile Coaching
- 27.
- 28. Thank you! KUNAL ARORA SENIORPROGRAM MANAGER • DOCUSIGN STEVE GRAYKOWSKI DIRECTOR, PROGRAM MANAGEMENT • DOCUSIGN