...
Completed Work measures how much planned work a team completes during a given interval.
Use Cases
GOAL: Help teams improve and/or stabilise how much work they can complete, and set guardrails around:
How much total work a team generally can complete to better manage everyone’s expectations
How much capacity a team needs to realistically ‘plan for the unplanned' and build greater agility into their workflow by being able to absorb ‘unplanned’ work
Make unplanned work visible, so teams can choose the type of work they can complete rather than react to what they’re working on
AS Mo, I want to be able to understand my total completion rate to know my team’s capacity and plan accordingly.
As Mo, I want to know, of the the work my team completes, how much is planned or unplanned (potential hidden work, reactive, customer, bugs etc) so that I can again, plan accordingly or change the process where it’s holding us back.
As Mo, I want to understand what type of unplanned work our team completes (tickets [sized or unsized], bugs, rework) so that I can improve our planning and review workflow.
Chart
Complete (Total line + Rolling) or (Cumulative - planned & unplanned)
Incomplete (Cumulative - planned and unplanned)
Callouts
As is
Surfacing
Complete
Item Title_Type_Assignee > Estimate > Date completed > Planned_Unplanned
Incomplete
Item Title_Type_Assignee > Estimate > Time in Status> > Planned_Unplanned
Why Completed Work matters
...