...
What is Sprint Stability
Sprint Stability highlights the ability of a team to maintain work with a stable set of requirements during development of a sprint.
Why
...
Sprint Stability matters
This is a measure that entirely depends on your team’s context.
A core principle of applying the agile method is that teams welcome change in requirements, even late in development. As such, changing requirements may reflect legitimate shift in priorities, or a response to discoveries that require a change in approach. It can also be reflective of a team’s adaptability in responding to the changing needs of their product manager or customer.
Unstable requirements during a sprint are often a however may be the result of insufficiently planned work, an uncontrolled sprint. This phenomenon often can also be referred to as scope creep and is closely linked to increases in costs and projects going over budget.
Having stable requirements increase confidence in planning, accuracy of estimation and the ability to complete a set goal.
Stable requirements provide a team with a stable goal (fixed scope) to work towards. This can build confidence and lead to a team being able to ship features more predictably.
Changing requirements may reflect legitimate shift in priorities, or a response to discoveries that require a change in approach. It can also be reflective of a team’s adaptability in responding to the changing needs of their product manager or customer.
It is important to build and maintain high levels of sprint stability if they choose to experiment with different practices to improve how they deliver their product to their customer.
...
What ‘good’ Sprint Stability looks like
Your team’s context is the best arbiter of what ‘good’ looks like for your team.
When a team focuses on improving their speed or progress, high levels of stability are favoured. Use Umano to manage the expectations of your team and peers with a clear eye on the assigned tasks, and work with your Product Manager to document and requested changes so they can be reviewed and prioritised when planning for your next sprint.
If your team has prioritised being responsive to customers, low lower levels of stability can be expected.
...
What’s included?
Included | Not included | |
|---|---|---|
Adding or updating the Jira description, story points or acceptance | Adding comments to a Jira ticket Adding or updating a label or tag on a Jira ticketAll tickets assigned to the sprint while the sprint is in progress | Sub-tasks within tickets that is inside the sprint Change of labels, related tickets or components |
Tips for a more stable sprint
...
| Tip |
|---|
Invest in stakeholder management to avoid new work being enforced upon the team mid sprint. |
Resources
...
predictability/ reliability
...