Timeline for How can a SAFe team end a failing sprint early?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 4 at 18:07 | vote | accept | Toby Speight | ||
| Apr 26 at 2:08 | comment | added | Thomas Owens♦ | @ToddA.Jacobs Yeah. The issue I have is around Sprint Review in particular. If you have 2 week or longer Sprints and cancel in the middle, you could easily be off by a week. Your key external stakeholders who anticipated a Sprint Review on a certain day may not be able to participate or have to shift their calendar. Cancelling a Sprint, especially without guidance, seems to either lead to breaking the rules of Scrum (having gaps between Sprints) or causing a lot of pain for stakeholders. Neither seems good. | |
| Apr 26 at 1:37 | comment | added | Todd A. Jacobs♦ | If a Sprint is canceled, the Scrum Team returns to Sprint Planning and selects a new Sprint Goal. By the book, "canceling the Sprint" means you don't hold any of the other events within a Sprint, and a new Sprint is supposed to start right after the previous Sprint. It seems like teams should at least do some sort of post-mortem before replanning, but as you say it's undefined. If you have one week Sprints, I'd say respect the cadence. If you have one-month Sprints, the cost of maintaining cadence for its own sake seems higher. The intent is to make the cost of major change visible, though. | |
| Apr 24 at 11:47 | history | answered | Thomas Owens♦ | CC BY-SA 4.0 |