The workflow insights provided by Umano include:
Where did I come from?
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.
Having stable requirements increase confidence in planning, accuracy of estimation and the ability to complete a set goal.
Umano measures Stability of Requirements through:
No new tickets added or removed after starting of the sprint
JIRA fields; summary, description, acceptance criteria, story points are not edited, whereby the summary and description fields are weighted less than acceptance criteria and story points.
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
Involve, where possible, the whole team in planning and backlog grooming.
Break stories and task down to smaller tasks.
Discuss dependencies for each tasks.
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.
Umano measures progress through:
Amount of story points or hours completed in a sprint
Add Comment