Skip to Main Content
Agile Game Development with Scrum
book

Agile Game Development with Scrum

by Clinton Keith
May 2010
Intermediate to advanced content levelIntermediate to advanced
384 pages
8h 51m
English
Addison-Wesley Professional
Content preview from Agile Game Development with Scrum

Chapter 4. Sprints

In the previous chapter, we introduced Scrum practices and roles. In this chapter, we’ll go into more detail about sprints. We’ll see how they are planned, how they are conducted on a day-to-day basis, and how the team and stakeholders review the progress at the end and reflect on how well they worked together. Finally, we’ll see how sprints might fail to achieve their full goals and how the teams and stakeholders deal with that.

The Big Picture

Sprints have the following basic rules:

• They are timeboxed, usually between two to four weeks in length.

• The team commits to completing a sprint goal.

• No additions or changes are made by anyone outside the team.

Figure 4.1 shows the flow of meetings in a sprint.

Figure 4.1. ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Agile Software Development: The Cooperative Game, Second Edition

Agile Software Development: The Cooperative Game, Second Edition

Alistair Cockburn
Large-Scale Scrum: More with LeSS

Large-Scale Scrum: More with LeSS

Craig Larman, Bas Vodde

Publisher Resources

ISBN: 9780321670311Purchase book