What is it
Sprint Stability highlights the ability of a team to maintain stable requirements during development of a sprint.
Why it matters
A core principle of remaining agile is that teams welcome change in requirements, even late in development
Unstable requirements during a sprint are often a can 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 increases confidence in planning, accuracy of estimation and the ability to a team’s ability to plan, accurately estimate and 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 Conversely, changing requirements may also 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’ looks likeWhat ‘good’ 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.
...
| Tip |
|---|
Invest in stakeholder management to avoid new work being enforced upon the team mid sprint. |
Resources
predictability/ reliability
Atlassian playbooks