Home > Articles

Scaling Agile Game Teams

  • Print
  • + Share This

There is no single formula for scaling Agile on a game project. Clinton Keith presents practices that have been successfully used with game teams of more than 1,000 developers spread across dozens of studios.

Save 35% off the list price* of the related book or multi-format eBook (EPUB + MOBI + PDF) with discount code ARTICLE.
* See informit.com/terms

This chapter is from the book

Although the ideal Scrum team size is five to nine people, modern game development efforts typically require far more developers (see Chapter 1, “The Crisis Facing Game Development”). Sometimes these developers are distributed across multiple locations. Although Scrum is designed to be scalable, large teams need to add practices, realign roles, and take precautions in how they organize teams and foster communication so that the increasing challenge of getting large groups of humans to align can be overcome.

The Solutions in This Chapter

This chapter explores a framework of scaling that is unique to game development. The main areas of focus are

  • Product Backlog organization

  • Team formation

  • Product ownership

  • Release and Sprint practices

  • Managing dependencies

  • The practices of distributed and dispersed teams

Together, the practices described here have been successfully used with game teams of more than 1,000 developers spread across dozens of studios.

  • + Share This
  • 🔖 Save To Your Account