As a scrum team, the intent is to complete all stories that are planned and committed for a sprint. The reality is though that not everything will get done for all kinds of reasons, to name a few,
incorrect estimates, where in something turned to be a lot bigger than anticipated. Perhaps the stories were not broken down enough
sudden loss in team capacity or changes in team makeup due to inclusion of some one new, or exclusion of someone
a number of customer issues popping up suddenly
technical resources suddenly unavailable
sudden priority changes to sprint stories or improper prioritization
The key is though teams have to deliver on what is promised, particularly if there an important customer waiting. We have been trying out these measures with some success, and continue to work on improving,
Breaking down stories as much as possible and not committing to anything that is over a certain number of points (generally 8).
Upto date team calendars with advance vacation plans and a buffer for unexpected absences
a bucket of hours for handling customer issues that pop up
Anticipate a sprint ahead of the type of technical resources needed and have it ready
On board team members in future sprints after a sprint of learning for new member
This entry was posted in
.NET,
Management,
Mentoring,
Scrum,
Team. Bookmark the <a href="https://sujatad.net/net/completing-stories/" title="Permalink to Completing stories…" rel="bookmark">permalink</a>.
