...
Completed Work measures how much of a planned scope of work a team completes during a given interval.
Why it matters
Understanding how much of their planned work planned is completed allows teams a team to plan more accurately and replicate their approach.
...
What ‘good’ looks like
Teams will often set a shared goal for how much of their work they aim to complete, for example a score of 80% of planned items. This acknowledges unplanned items arising can arise during the sprint , and the they need to reprioritise to retain capacity to respond and adapt accordingly.
How Umano measures this
...
Each model looks and specific activities within the tools. Below a list of activities that contribute to Balance of Communication Completed Work and activities that do not have an impact on this metric.
Included | Not included | ||
|---|---|---|---|
All messages in selected public channels in Slack and Mattermost Comments on Jira tickets, Confluence pages and Bitbucket PR's | Direct messages or private channels Creating or editing Jira descriptions, custom fields, labels etc. Creating or editing Confluence pages Creating or editing Bitbucket PR descriptions Any communication from people outside of the linked team members. | work items in Jira that are assigned to a sprint including Stories, Tasks, Sub-Tasks, Bugs and Spikes |
Tips for improving completed work
| Tip |
|---|
During sprint planning, rank Rank the priority of all tickets assigned to the sprint during sprint , planning so it’s clear which items can be deprioritised reprioritised if new and unplanned items need to be prioritised and assigned |
...
| Tip |
|---|
Reprioritise your sprint load , rather than accepting new items into the sprint and not removing or reprioritising other existing items |
Resources
optimism bias