Mixed methods in a Large Scale Agile Environment AgileCamp 2014
In Large Scale Agile, for example SAFe, the idea is that all teams use the same methods in order to be able to work aligned with a single program or even an entire portfolio. However, in practice it’s a bit harder due to the fact that different types of development would be better served by different ways of working. For example, many products are a combination of hardware and software, which require hardware and software developers to work in tight collaboration using different methods. Another example would be game features and art assets, which also require different methods. This presentation will be based on examples from the real world where companies have utilized mixed methodologies in a large-scale agile development environment to succeed with developing better products in a more collaborative way and hence stay ahead of competition. Topics covered will be: 1. How to work with mixed methods and combining Scrum, Kanban and Gantt in a single program. 2. Program level collaboration. Multiple teams working in a single program backlog allowing a single product release train, thus avoiding siloed teams. 3. Finally, what do we measure and how do we track progress?
Recommended
Recommended
More Related Content
Similar to Mixed methods in a Large Scale Agile Environment AgileCamp 2014
Similar to Mixed methods in a Large Scale Agile Environment AgileCamp 2014 (20)
Recently uploaded
Recently uploaded (20)
Mixed methods in a Large Scale Agile Environment AgileCamp 2014
- 1. Mixed Methods in a Large Scale Agile Environment Jon Leslie Senior Production Expert Hansoft
- 7. In This Session, You’ll Learn… • Scrum, Kanban and Gantt in a single Plan / Program • Program level collaboration • Agile Metrics –What do we measure?
- 8. “Implicit (to Agile) is a personal way of orienting oneself towards a development process that accepts, even welcomes, change.” Andrew Binstock Editor in Chief Dr. Dobbs Values not Practices
- 9. AAA Video Game Development • Large ScaleAgile in 2004 • Embrace Change • Innovation & Iteration • EmpowerTeams (Crunch Free) • DifferentWays ofWorking
- 10. 3 Large Scale Agile Game Examples • Amped 3 • The Sims 3 • Rock Band 3
- 11. Amped 3
- 12. Scrum for Everything Amped 3 Developed 2004 - 2005
- 13. The Sims 3: Showtime
- 14. Scrum for Features Kanban for Assets The Sims 3: Showtime, Supernatural & University
- 15. Rock Band 3
- 16. Scrum for Features Kanban for Assets Gantt for Hardware Rock Band 3
- 17. Different Industries – Similar Challenges • Telecom • Electronics • Aerospace & Space
- 18. Many Specialties
- 19. One FUN Product
- 20. AAA Game Development Challenge Certainty Assets / Hardware Features Definition
- 21. Multiple Techniques – Single Mindset • Scrum for Game Features • Kanban for Game Art Assets • Gantt for Game Hardware • Task Breakdown • Self Empowered, Self Managed Teams • Only Features & Assets • Single Backlog • Backlogs within a Backlog • Single Release Train • Shared High Level Vision Project Plan Program Backlog
- 22. Single Program Backlog - Keyboard - Guitar - Drums - Bass
- 23. Scrum - Kanban - Gantt in Same Plan • 3 Teams • 3 Techniques • 1 Program • 1 Backlog • 1 Release Train • 1 Mindset
- 24. Agile Metrics – What to Measure • Only Present & Future Looking • Only Actionable • 3 Different Levels Team Program Portfolio
- 25. Agile Metrics – Team Level
- 26. Agile Metrics – Program Level
- 27. Agile Metrics – Portfolio Level
- 28. Summary • DifferentTeams May Require Different Methods – In a Single Program – Sharing a Single Agile Mindset • Collaborate at theTeam Level and the Program Level • Measure on Forward Looking Actionable Metrics