Contents
Who manage the teams work during a sprint?
As the sprint gets underway, scrum teams use a task board to manage their work. Progress is tracked using a sprint burndown chart. Each day the team meets for a short standup meeting, known as as the daily scrum.
How do you manage a sprint?
- Set the sprint goal.
- Prioritize the stories that fulfill the sprint goal.
- Arrange an informal sprint planning preparation meeting.
- Meeting arrangements.
- Introduction of the candidate stories.
- Sizing of the stories.
- Breakdown stories into tasks.
- Agreement on the bug fixes and support work.
How to deal with unplanned work during sprint?
‘How do I deal with unplanned work?’ is a question I hear quite often from the teams I train or coach. The answer is not as simple as it may seem. First thing to understand is that unplanned work is rarely a problem per se. Usually, it’s just a symptom of the true issues that are hidden from sight.
What happens when you report a bug in a sprint?
A team has planned a sprint and started development. In a few days, a user reports a high priority bug. The team replaces a planned user story with the bug and carries on. In a few more days a couple more bugs are found. The situation repeats several times and a large chunk of the sprint backlog ends up not being delivered.
What happens in the middle of a sprint?
In the middle of a sprint, a product owner comes to a team with a request. She has discovered that a new feature must be completed with top priority and asks to add it to the sprint. A new user story is added to a sprint at the expense of another user story.
Why is a sprint important for a team?
One of the crucial concepts behind a sprint is to let the team focus on the work. Changes that are big enough may and will break the team’s flow. The other reason is to prevent local scope creep.