Chore %
Work Mix & Quality Balance
%
Shows the percentage of completed work categorized as chores or maintenance.
💡 Like regular home maintenance, you need some chores to keep the house running, but too many means something is broken.
What It Measures
Shows the percentage of completed work categorized as chores or maintenance.
Why It Matters
Ensuring the right amount of capacity goes to upkeep tasks
Monitoring technical debt and infrastructure work
How It's Calculated
Divides chore tickets by total tickets and multiplies by 100.
chore_tickets ÷ tickets × 100Concrete Example
If 3 of 20 tickets were chores (maintenance, refactoring, upgrades), that's 15% chore work, a healthy proportion for keeping tech debt in check.
What Does a Healthy Score Look Like?
Aim for a consistent small percentage, too little means debt is building.
Healthy
10–20% chore work
Watch Out
Under 5% (debt building) or over 30% (something is very wrong)
Needs Attention
Near zero for months, followed by a spike, debt cycles are disruptive
What Moves This Metric?
Goes up when…
Dedicated maintenance or refactoring sprints
Infrastructure upgrades or dependency updates
Tech debt paydown initiatives after fast-paced feature delivery
Goes down when…
Heavy feature push leaving no capacity for maintenance
Maintenance work being deprioritised in planning
Team not tracking or labelling chore work consistently
Start Tracking Chore %
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com