Timeline for How to detect a potentially failing sprint
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 7, 2020 at 3:34 | history | edited | Vicki Laidler | CC BY-SA 4.0 |
Rephrased title to more clearly signal questioner's intent explained in more detail in body of question
|
| Mar 6, 2020 at 15:41 | answer | added | Ashok Ramachandran | timeline score: 1 | |
| Mar 6, 2020 at 12:00 | history | tweeted | twitter.com/StackProjects/status/1235898082056863744 | ||
| Mar 6, 2020 at 7:32 | answer | added | Bart | timeline score: 0 | |
| Mar 5, 2020 at 23:22 | history | became hot network question | |||
| Mar 5, 2020 at 19:17 | comment | added | Tiago Peres | I see the difference and similarities. In that other question there's at least one example of a failed sprint. To answer your question, we would need to know such things. | |
| Mar 5, 2020 at 19:07 | comment | added | Yastafari | @Tiago Martins Peres: This does not answer the question because it asks "What is a failed sprint". I myself suggested an answer that is similar to that provided by Thomas Owens below. What this is about is trying to identify the indicators that would suggest a sprint is "failing" that would enable a scrum master to address those issues before the sprint completes, or at least prep the product owner that a "failure" is likely. | |
| Mar 5, 2020 at 18:55 | review | Close votes | |||
| Mar 5, 2020 at 19:20 | |||||
| Mar 5, 2020 at 18:39 | comment | added | Tiago Peres | Does this answer your question? What is a failed sprint? | |
| Mar 5, 2020 at 16:40 | answer | added | Thomas Owens♦ | timeline score: 8 | |
| Mar 5, 2020 at 15:13 | history | asked | Yastafari | CC BY-SA 4.0 |