...
| Info |
|---|
Umano’s models use Jira to obtain information on workflow |
Sprint stability
Highlights the ability of a team to maintain stable requirements during development of a sprint. Unstable requirements during a sprint are often a result of not properly planned work, an uncontrolled sprint. This phenomenon often referred to as scope creep and is closely linked to increases in costs and projects going over budget.
...
A score of 100% means that the sprint was executed as planned without updates to requirements or new work.
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 ticket |
Tips for a more stable sprint
| Tip |
|---|
Involve, where possible, the whole team in planning and backlog grooming. |
...
| Tip |
|---|
Invest in stakeholder management to avoid new work being enforced upon the team mid sprint. |
Sprint completion
Sprint completion measures the number of story points or hours completed within a sprint. This allows teams to plan more accurately and replicate their approach.
...