Adopting Leffingwell's Scaled Agile Framework: the theory and the practice - Agile Australia - June 2013

3,175 views

Published on

Presentation with Mark Richards at Agile Australia 2013 in Sydney.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,175
On SlideShare
0
From Embeds
0
Number of Embeds
2,477
Actions
Shares
0
Downloads
29
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Adopting Leffingwell's Scaled Agile Framework: the theory and the practice - Agile Australia - June 2013

  1. 1. TELSTRATEMPLATE4X3BLUEBETA|TELPPTV4 ADOPTING LEFFINGWELL'S SCALED AGILE FRAMEWORK: THE THEORY AND PRACTICE EM CAMPBELL-PRETTY, GM STRATEGIC DELIVERY @PrettyAgile www.prettyagile.com MARK RICHARDS, PRINCIPLE CONSULTANT, RICHDATA @MarkAtScale www.agilenotanchy.com
  2. 2. 5 Wagile Teams 4 Projects
  3. 3. 3PRESENTATION TITLE | PRESENTER NAME | DATE |
  4. 4. THE EDW AGILE RELEASE TRAIN Average delivery cycle time down from 12 month to 3 months Frequency of delivery increased from quarterly to fortnightly Cost to deliver down 50% 95% decrease in product defects 100% projects delivered on time and on budget Happy project sponsors (NPS 29) Happy teams (Team NPS 43 )
  5. 5. THE AGILE RELEASE TRAIN • A virtual organization of 5 – 12 teams (50-100 individuals) that plans, commits, and executes together • Common cadence and normalized story point estimating • Aligned to a common mission via a single program backlog • Operates under architectural and UX guidance • Produces valuable and evaluate-able system-level Potentially Shippable Increments (PSI) every 8-12 weeks The ART is a long-lived, self-organizing team of agile teams that delivers solutions Define new functionality Implement Acceptance Test Deploy Repeat until further notice. Project chartering not required.
  6. 6. EPICS FEATURES STORIES
  7. 7. THE BEST WAY TO START  Train everyone at the same time  Same instructor, same method  Cost effective  Align all teams to common objectives  Commitment  Continue training during planning  Orientation for specialty roles  Open spaces  Tool training for teams Training: SAFe ScrumXP Release Planning Enterprise Scrum Master Quickstart Enterprise Product Owner Quickstart Mon Tue Wed Thu Fri Tooltraining You Are Agile, Now When you find the first train, go “All In” and “All at Once”
  8. 8. HOW WE STARTED
  9. 9. STRUCTURING THE AGILE RELEASE TRAIN Deployment Services Pipeline Services (connecting, feeding, and shielding the delivery teams. Identification of strategic opportunities) Development Service (engaged and delivering directly to Epic/Feature Owners) Leadership Team ‘Loco’ + Specialist Chapters (virtual teams made from the workers themselves) SD System Team (identifies, manages, and eliminates bottlenecks) Team Collaboration
  10. 10. VISUALISE THE PROGRAM PORTFOLIO
  11. 11. SCALING THE SPRINT
  12. 12. RELEASE PLANNING • Two days every 8-12 weeks • Everyone attends in person if at all possible • Product Management owns feature priorities • Development team owns story planning and high-level estimates • Architects, UX folks work as intermediaries for governance, interfaces and dependencies • Result: A committed set of program objectives for the next PSI Cadence-based PSI/Release Planning meetings are the “pacemaker” of the agile enterprise
  13. 13. ‘PSI-LITE’ BECOMES UNITY DAY 1515
  14. 14. THE FOUNDATION IS LEAN LEADERSHIP 16PRESENTATION TITLE | PRESENTER NAME | DATE | 16PRESENTATION TITLE | PRESENTER NAME | DATE |
  15. 15. SCALING THE PRODUCT OWNER Source: Agile Portfolio and Program Management in the Scaled Agile Framework, Dean Leffingwell, Agile Melbourne Meetup, 15/02/12
  16. 16. SCALING THE PRODUCT OWNER EPIC OWNER FEATURE OWNER PRODUCT OWNER
  17. 17. THE RELEASE BOARD FEATURE LEVEL
  18. 18. CONTINUOUS INTER-TEAM COORDINATION • Agile team members may visit other team’s… • Backlog grooming: to see what’s coming next sprint, request adjustments • Sprint planning: request adjustments • Daily standups: follow up on execution • Team Demo: summarize current stage Agile teams self-manage dependencies and resolve risks Agile Team 1 Agile Team 2 Dependent story Join other team scrum ceremony
  19. 19. SCALING COMMUNICATION: THE DAILY COCKTAIL PARTY 22PRESENTATION TITLE | PRESENTER NAME | DATE | 9:00am 9:15am 930am 9:45am
  20. 20. SAFE SCRUM / XP
  21. 21. A LITTLE TASTE OF OUR CULTURE http://www.prettyagile.com/2013/05/the-power-of-haka.html
  22. 22. QUESTIONS?

×