␡
- The Solutions in This Chapter
- Challenges to Scaling
- Should You Scale Up?
- Scaling the Wrong Process
- The MAGE Framework
- The Product Backlog
- Team Organization
- Product Ownership
- Additional Roles
- Releases
- Sprints
- Managing Dependencies
- Distributed and Dispersed Development
- What Good Looks Like
- Summary
- Additional Reading
This chapter is from the book
This chapter is from the book
This chapter is from the book
This chapter is from the book
Summary
There is no single formula for scaling Agile on a game project. Scrum scales up to projects of any size but drives changes in team structure, roles, and practices. The place where most scaling frameworks fail is in creating massive overhead, process, and layers of communication that undermine the Agile and Scrum principles, which are the reason we adopted them in the first place.
Scaling is hard. No matter what you do you will encounter obstacles and challenges. The organization and the teams must use the built-in Scrum inspect-and-adapt loop to improve how they work together in order to succeed.