Timeline for How to detect a potentially failing sprint
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 6, 2020 at 11:06 | comment | added | Thomas Owens♦ | @Yasterfari I just edited that comment (and some more details, too) into my answer itself. Let me know if that's helpful or need more detail. | |
| Mar 6, 2020 at 11:06 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 |
added 913 characters in body
|
| Mar 6, 2020 at 11:03 | comment | added | Thomas Owens♦ | I would ask questions. If I don't hear the team talking about the Sprint Goal or the work associated with Product Backlog Items associated with the Sprint Goal, I'd ask about those. I would also look at time in state, once work starts - is something "in progress" for a long time, or waiting for code review for a long time, for example and ask about those. Some kind of visual aid is nice - I prefer a Kanban board with the Sprint Goal and work item aging visible since it can help focus the discussion on the goal and progress of work items (including blocked items). | |
| Mar 6, 2020 at 10:55 | comment | added | Yastafari | Can you elaborate on what you have done to encourage team members to raise concerns. As you probably know, it is difficult to get people to voice their concerns, especially if those concerns are around the actions of another team member or contributor (such as a BA or a Stakeholder etc). | |
| Mar 6, 2020 at 10:05 | comment | added | Thomas Owens♦ | @Yasterfari I'm saying that Scrum Master's don't use anything to get an early insight into the health and confidence of the Sprint. The closest they would come is coaching the Development Team on how to effectively use the Daily Scrum to assess progress toward or risks/impediments to achieving the Sprint Goal and what to do when such risks/impediments are raised. | |
| Mar 5, 2020 at 19:16 | comment | added | Yastafari | I agree, there is no such thing as a failed sprint. Even a "failed" sprint provides material that can be used for the teams continual improvement. Also, i agree that the team is best placed to know whether a sprint goal is going to be met or not, and that the daily scrum, stand up, call it what you will, is a good indicator of this. I am just trying to get an idea what other scrum masters use to get early insight into the health or confidence of the sprint. | |
| Mar 5, 2020 at 16:40 | history | answered | Thomas Owens♦ | CC BY-SA 4.0 |