Rework Rate is the percentage amount of issues moved back to an ‘in-progress’ status from a ‘review’ or ‘done‘ status compared with all issues assigned to the interval.

​

No-one likes to spend time going backwards. This is what it can feel like when work is submitted for review, only to be sent back for further re-work. This can feel more acute when work is deemed done, but then returned to an in-progress status because of an issue identified once merged. Umano created Rework Rate to help teams identify patterns relating to issues requiring rework, so they can spend less time going backwards, and more time shipping work their customers love!

Rework rate provides teams with insight into less value being delivered than planned, either through ill-defined requirements, lack of customer engagement during the design and build stage, or quality trade-offs made during the build. It supports teams to identify patterns relating to work that does not meet expected standards. It can also assist teams to strengthen part of their workflow where work may consistently be returned for rework.

Rework Rate is presented as a percentage, where a lower percentage of rework indicates higher quality work and stronger review practices.

TeamX measures the total number of issues reworked relative to the total number of issues assigned in an interval. TeamX presents this percentage as a total of all issues, as well as a percentage by issue type, including stories, tasks and bugs.

TeamX surfaces the stories, tasks and bugs reworked per interval, including time spent in each status over the lifecycle of the issue, and the number of intervals the issue’s life cycle extends.

Activities that contribute to and influence Rework Rate include all of the issues (including defects) assigned to the interval that were moved back to an ‘in-progress’ status from being ‘in review’ or ‘done’.