Timeline for What to do when mid-sprint, you realize some stories won't be done?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 3, 2017 at 18:18 | comment | added | Alan Larimer | The Scrum Guide "A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense." The Development Team forecasts the items it believes it can complete, this plan can be negotiated with the Product Owner and adjusted as needed. | |
| Aug 22, 2017 at 21:23 | answer | added | Todd A. Jacobs♦ | timeline score: 4 | |
| Aug 19, 2017 at 10:09 | comment | added | Muhammad | With new teams, its normal for large chunks of the sprint backlog not being achieved. This is why Scrum encourage sprint-wise release planning, estimation, and so on. As you mature, your estimation, plans, and so on become more accurate. By your and you, I mean the whole team, of course. So the first action you take is discuss the issue with the product owner. If the sprint goal is unaffected, you continue working. Maybe the PO can make the sprint goal less ambitious? IMO, sprint is only cancelled by the PO if the business needs change dramatically, rendering the sprint obsolete. | |
| Aug 18, 2017 at 19:19 | vote | accept | otc | ||
| Aug 18, 2017 at 18:43 | answer | added | Sarov | timeline score: 5 | |
| Aug 18, 2017 at 18:38 | history | edited | Sarov | CC BY-SA 3.0 |
added 119 characters in body; edited title
|
| Aug 18, 2017 at 18:03 | review | Low quality posts | |||
| Aug 18, 2017 at 18:38 | |||||
| Aug 18, 2017 at 17:47 | history | asked | otc | CC BY-SA 3.0 |