From 935e96a66232a321c91c2ec0765712ab42af8ca8 Mon Sep 17 00:00:00 2001 From: Barbara Kryvko Date: Mon, 29 Oct 2018 13:03:07 -0500 Subject: [PATCH] Clarification of sprint work (#21031) --- guide/english/agile/sprints/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/guide/english/agile/sprints/index.md b/guide/english/agile/sprints/index.md index a3b78d9ba6..f0b9ad85dd 100644 --- a/guide/english/agile/sprints/index.md +++ b/guide/english/agile/sprints/index.md @@ -6,9 +6,9 @@ title: 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 --Sprints should remain the same pretetermined length of time throughout the length of the project. --The team works to break up the User Stories 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. +- 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 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: