Mixed methods in a Large Scale Agile Environment AgileCamp 2014
29
Mixed Methods in a Large Scale Agile Environment Jon Leslie Senior Production Expert Hansoft
-
date post
16-Sep-2014 -
Category
Technology
-
view
216 -
download
1
description
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?
Transcript of Mixed methods in a Large Scale Agile Environment AgileCamp 2014
PowerPoint Presentation
Mixed Methods in a Large Scale Agile Environment
Jon LeslieSenior Production ExpertHansoft
Scrum, Kanban and Gantt in a single Plan / ProgramProgram level collaborationAgile Metrics What do we measure?
In This Session, Youll LearnImplicit (to Agile) is a personal way of orienting oneself towards a development process that accepts, even welcomes, change. Andrew BinstockEditor in ChiefDr. DobbsValues not PracticesAgile is a set of values. It is not a set of practices. We need to keep this in mind if were to hold true to the intent of the Agile Manifesto.
Scrum is a process and a set of practices derived from Agile. Agile is about culture. A culture that embraces change. If a Scrum development site does not embrace change, they are not Agile.
Its a very important distinction and one we need to keep in mind anytime we bandy about terms like Large Scale Agile.
Along the lines of Team Empowerment, we should allow teams to work they way that best suits them. Even if those teams are working in a multi-team environment and not all teams are using the same methodology.
8AAA Video Game DevelopmentLarge Scale Agile in 2004Embrace ChangeInnovation & IterationEmpower Teams (Crunch Free)Different Ways of Working
3 Large Scale Agile Game ExamplesAmped 3The Sims 3Rock Band 3
Amped 3
Scrum for EverythingAmped 3Developed 2004 - 2005Large Scale Agile in 2004100+ person teamWe wanted to embrace change with ScrumDidnt realize we were different teams / disciplines with different ways of workingCrunch hell
12The Sims 3: Showtime
Also produced Supernatural & University Life.
Celebrity external dependencies. Katy Perry had to approve her Sim and all clothes / accessories and hairstyles.
13Scrum for FeaturesKanban for AssetsThe Sims 3: Showtime, Supernatural & University
Large Scale Agile in 2004100+ person teamWe wanted to embrace change with ScrumDidnt realize we were different teams / disciplines with different ways of workingCrunch hell
14Rock Band 3
102 button controller!Plus, we added a keyboard.
Had to have prototype hardware in order to test new gameplay.
15Scrum for FeaturesKanban for AssetsGantt for HardwareRock Band 3
Gantt is a technique Waterfall is a mindset
Use Gantt in an Agile context.
16Different Industries Similar ChallengesTelecomElectronicsAerospace & Space
Many Specialties
One FUN Product
AAA Game Development ChallengeCertaintyAssets / HardwareFeaturesDefinitionMultiple Techniques Single MindsetScrum for Game FeaturesKanban for Game Art AssetsGantt for Game HardwareTask BreakdownSelf Empowered, Self Managed Teams
Only Features & AssetsSingle BacklogBacklogs within a BacklogSingle Release TrainShared High Level VisionProject PlanProgram BacklogSingle Program Backlog
- Keyboard- Guitar- Drums- Bass
Scrum - Kanban - Gantt in Same Plan
3 Teams3 Techniques1 Program1 Backlog1 Release Train1 MindsetAgile Metrics What to MeasureOnly Present & Future LookingOnly Actionable3 Different LevelsTeamProgramPortfolioAgile Metrics Team Level
Agile Metrics Program Level
Agile Metrics Portfolio Level
Different Teams May Require Different MethodsIn a Single ProgramSharing a Single Agile MindsetCollaborate at the Team Level and the Program LevelMeasure on Forward Looking Actionable Metrics
Any questions?
