Scaling agile with sa fe v1.0
- 3. About you • Name • Organization • Role • Years of Agile Experience • Awareness of SAFe / other Scaling models
- 4. Agenda • What is Scaling Agile? • Challenges in Scaling Agile • Overview of SAFe
- 5. Characteristics of Agile Teams • Teams of sizes 5 – 9 members • Co-located • Self Organized • Collaborative • Cross Functional • Will this work for large organizations moving towards Agile methods ?
- 7. What is Scaling agile? Product Team Team Team Product Team Team Team Product Team Team Team Portfolio Product Team Team Team
- 9. Why Scale Agile? • Optimize delivery of business value • Drive consistency and predictability on project execution • Understand true Enterprise capacity
- 13. Common scaling frameworks • Scrum of Scrums (SoS) • Large Scale Scrum (LeSS) • Disciplined Agile Delivery (DAD) • Nexus • Scaled Agile Framework (SAFe) • Scaling Agile at Spotify (SaaS)
- 15. Scrum of Scrums • Allow teams to discuss their work, focusing especially on areas of overlap and integration • Each team designates one member as a representative to participate in the Scrum of Scrums. • Scrum of Scrums meetings occur 2/3 times a week • 4 questions – What has your team done since we last met? – What will your team do before we meet again? – Is anything slowing your team down or getting in their way? – Are you about to put something in another team’s way? https://www.scrumalliance.org/community/articles/2007/may/advice-on-conducting-the-scrum-of-scrums-meeting
- 16. Agile Software Development Series Alistair Cockburn and Jim Highsmith, Series Editors Agile Software Requirements Lean Requirements Practices for Teams, Programs, and the Enterprise Dean Leffingwell Foreword by Don Reinertsen 4 Creator: Scaled Agile Framework 4 Agile Enterprise Coach To some of the world’s largest enterprises 4 Agile Executive Mentor BMC, John Deere 4 Chief Methodologist Rally Software 4 Cofounder/Advisor Ping Identity, Roving Planet, Silver Creek Systems, Rally Software 4 Founder and CEO ProQuo, Inc., Internet identity 4 Senior VP Rational Software Responsible for Rational Unified Process (RUP) & Promulgation of UML 4 Founder/CEO Requisite, Inc. Makers of RequisitePro 4 Founder/CEO RELA, Inc. Colorado MEDtech Scaled Agile Framework SAFe® is a freely revealed knowledge base of integrated, proven patterns for enterprise Lean-Agile development
- 18. SAFe Principles 1. Take an economic view 2. Apply Systems Thinking 3. Assume variability; preserve options 4. Build incrementally with fast, integrated learning cycles 5. Base milestones on objective evaluation of working systems 6. Visualize and limit WIP, reduce batch sizes, and manage queue lengths 7. Apply cadence, synchronize with cross-domain planning 8. Unlock the intrinsic motivation of knowledge workers 9. Decentralize decision-making
- 22. SAFe at the Team Level • Empowered, self-organizing, self-managing, cross-functional team • Delivers valuable, tested, working system every two weeks • Uses a team framework which combines the best of Scrum project management, XP-inspired technical practices and Kanban for flow • Value delivery via User Stories
- 23. SAFe at the Program Level • Self-organizing, self-managing team-of-agile-teams • Delivers working, tested full system increments every two weeks • Operates with Vision, architecture and UX guidance • Common iteration lengths and estimating • Face-to-face planning for collaboration, alignment, and adaptation • Value delivery via Features and benefits
- 24. SAFe at the Value Stream level • Coordinates development of large Solutions • Synchronizes multiple ART Value Streams • Manages Solution Intent • Integrates suppliers as partners • Value delivery via Capabilities
- 25. SAFe at the Portfolio level • Organized around the flow of value • Lean-Agile budgeting empowers decision makers • Kanban system provides portfolio visibility and WIP limits • Enterprise architecture guides larger technology decisions • Objective metrics support governance and improvement • Value delivery via Epics
- 26. The Agile Release Train • A virtual organization of 5 – 12 teams (50 – 125+ individuals) that plans, commits, and executes together • Program Increment (PI) is a fixed timebox; default is 10 weeks • Synchronized Iterations and PIs • Aligned to a common mission via a single Program Backlog • Operates under architectural and UX guidance • Frequently produces valuable and evaluable system-level Solutions Define new functionality Implement Acceptance test Deploy AGILE RELEASE TRAIN DELIVERS SOLUTIONS Repeat until further notice. Project chartering not required.
- 27. Release Planning • 2 days every 8-12 weeks • Every one attends in person, if at all possible • Each team comes out with PI objectives which are brief summaries in business terms what each team intends to deliver at the end of the PI • There is a Program Board which lists out all the features, the milestones, the dependencies, and anticipated delivery dates of all the teams in a PI
- 28. New Roles • Program level • Release Train Engineer – Chief Scrum master for the train • Product Management – owns, defines and prioritizes the program backlog • System Architect – provides architectural guidance and technical enablement to the team • System team – provides process and tools to integrate and evaluate assets early and often • Business Owners – Key stakeholders of the Agile Release Train • Value Stream level – Value Stream Engineer – Facilitate Value Stream process and execution – Solution Architect – Responsible for Tech and Architecture vision at Solution level – Solution Management – Responsible for the Value Stream backlog • Portfolio level – Program Portfolio Management – responsible for Strategy and Investment funding, Program Management and Governance – Enterprise Architect – drive holistic technology implementation across the enterprise – Epic Owners – responsible for driving individual epics from identification through to implementation
- 29. SAFe Delivers Business Results Increase in employee engagement 20-50% increase in productivity 30-75% faster time to market 50%+ defect reduction
- 31. SAFe Role-Based Learning Paths Core AdvancedRoles Executives Managers Stakeholders Leading SAFe 4.0 2 days SAFe Agilist Agile Change Agents Consultants Implementing SAFe 4.0 4 days SAFe Program Consultant Product Owners Product Managers Relevant experience of agile and scaling agile Lean-Agile Leaders SAFe 4.0 PM/PO 2 days SAFe Product Manager/ Product Owner Teams SAFe 4.0 for Teams 2 days SAFe Practitioner Agile Teams Scrum Masters SAFe 4.0 Scrum Master 2 days SAFe 4.0 Advanced Scrum Master 2 days SAFe Advanced Scrum MasterSAFe Scrum Master OR CSM, PSM, other More info: ScaledAgile.com/which-course *available Nov. 2016
- 32. Questions?
- 33. Thank you