2.2 KiB
2.2 KiB
| title |
|---|
| Sprints |
Sprints
In Scrum, the Sprint is a period of working time usually between one and four weeks in which the delivery team works on your project. Sprints are iterative, and continue until the project is completed. Each sprint begins with a Sprint Planning session, and ends with Sprint Review and Retrospective meetings. Using sprints, as opposed to months-long waterfall or linear sequential development methodologies, allows regular feedback loops between project owners and stakeholders on the output from the delivery team.
Properties of a Sprint
- A sprint should not be terminated prematurely if at all possible. If the stories within the sprint become obsolete, the team may decide to close them and pull new stories off of the product backlog.
- The team works to break up the User Stories, a non-technical description of what the user expects to see and/or do, to a size that can be completed within the duration of the Sprint without carrying over to the next.
- "Sprint" and "Iteration" are often used interchangeably.
More Information:
- Agile Alliance on Iterations
- Agile Alliance on Timeboxes
- Agile Coach on Sprint vs Iteration
- Scrum Alliance Timeboxing as a Motivational Factor
- Scrum Alliance Sprint is More Than Just a Timebox
- Scrum Inc What is Timeboxing
- Scrum.org What is a Sprint in Scrum