slide1 l.
Skip this Video
Loading SlideShow in 5 Seconds..
Agile Methodology in Game Development: Year 3 PowerPoint Presentation
Download Presentation
Agile Methodology in Game Development: Year 3

Loading in 2 Seconds...

  share
play fullscreen
1 / 27
Download Presentation

Agile Methodology in Game Development: Year 3 - PowerPoint PPT Presentation

PamelaLan
213 Views
Download Presentation

Agile Methodology in Game Development: Year 3

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Agile Methodology in Game Development: Year 3 Clinton Keith CTO, High Moon Studios

  2. What We’ll Talk About: • History of Agile at High Moon • What is Agile? Why use it? • Overview of Scrum, one Agile Methodology • Agile Planning • We’ll touch on eXtreme Programming (XP) • The results of using Agile at High Moon • Q&A This is about what we experienced, not the “Right Way” to make games

  3. History of Agile at High Moon • Used Scrum in last year of Darkwatch • Helped keep the project on track • Adopted XP and Agile planning practices on new projects over the last year

  4. Why Adopt Agile? The Reasons/Goals: • Reduce wasted effort/crunch • To find the fun first Other industries have used Agile to develop better products faster. Can we?

  5. What is Agile Development? The roots of Agile go back 60 years for product dev (in Japan) and 30+ years for software dev. The Agile Manifesto (modified for game dev): We value… • People and communication over processes and project management tools; • Working game over comprehensive design documents; • Publisher collaboration over milestone definitions; • Responding to change over following a plan;

  6. Far from Agreement Anarchy Complex Requirements Complicated Simple Close to Agreement Technology Far from Certainty Close to Certainty Wasted Effort Can Come From “Noise”…and it influences what methodology we use Preproduction Production Source: Strategic Management and Organizational Dynamics by Ralph Staceyin Agile Software Development with Scrum by Ken Schwaber and Mike Beedle.

  7. Finding the Fun First Not fun yet? Alpha/Beta E3 Demo Production Preproduction Design

  8. What is Scrum?Scrum is.. • One of the major Agile Methologies • Iterative • Commitment-oriented • Results-oriented • Disciplined • About making things visible so you can apply common sense

  9. ProductOwner The Scrum Cast ScrumMaster Anyone. Not a lead role Director Artist Artist The Team Animator Marketing QA Programmer Customers Designer Publisher Producer

  10. Product Backlog Jump Product Backlog as prioritized by Product Owner Crouch Defined as User Stories with conditions of satisfaction Run Estimated with relative User Story Points that help track progress

  11. Sprints (Iteration) Change Sprint (Fixed Duration) Sprint Backlog broken out by team Sprint Goals Game Jump New Game (Vertical Slice Added) Crouch Run

  12. Review and Planning Game Jump Fly Crouch Review and Planning Run

  13. Daily Scrum Daily Scrum Game Jump Fly Crouch Run

  14. The War Room CompletedTasks UserStories (Sprint Backlog) Tasks Burndown Chart

  15. Jump User Story Task Mon. Tues. Wed. Thurs. 3 Jump Input Control 8 0 0 16 Jump Tuning 16 10 4 16 Jump Animation 8 16 4 Double Jump Option 8 8 0

  16. Sprint Backlog Burndown Chart Drag works against velocity Slope = Velocity Hours Backlogged Story Days Must hit zero hours by end

  17. Scaling Scrum - The Scrum of Scrums Functional Leadership Support services Teams

  18. Releases – The Product Backlog Iceberg High Sprint Release Value Cost Priority Future Releases Risk Knowledge Low

  19. Release Burndown

  20. eXtreme Programming (XP) Alpha/Beta Cost Of Change Development Design Time

  21. Agile Game Development • Lessons learned • Benefits • Where to go for more info?

  22. Lessons Learned • Start small • One Scrum team doing a prototype would be ideal • Do what the book says from the start • Company dysfunctions can creep in otherwise • Don’t get too dogmatic about it • …but Scrum is meant to be modified (eventually)

  23. Lessons Learned… • Agile planning is harder to start than thought • But XP was easier • Coaching was critical • Onsite and CSM • Publisher buy-in wasn’t difficult • Getting them into reviews and planning took adjustment

  24. Normal Velocity Lessons Learned… Overtime Velocity Overtime value is limited but average intensity is raised • Old Habits Die Hard • Over-design • Delayed integration • Seating by discipline • Command and control Week 1 Week 2 Week 3 Week 4 Week 5 Testing needs to be pushed

  25. Benefits • Improved… • Productivity • Reliability of build • Quality of game • Morale • Ownership • Team work • Communication • Enables low-cost executive awareness • Which means you don’t have to work hard to find out what’s going on

  26. Where to go for more info? • www.agilegamedevelopment.com • Books • Mailing lists – For Game Developers to share info on adopting Agile • AGD Blog – Addressing challenges and news on adopting Agile to Game Development Questions?