Feature %
Work Mix & Quality Balance
%
Shows the percentage of completed work categorized as features.
💡 Think of it as your team's investment allocation, what percentage of your capacity goes to building new things versus maintaining existing ones.
What It Measures
Shows the percentage of completed work categorized as features.
Why It Matters
Balancing investment between feature delivery and other work types
Ensuring adequate focus on new capabilities
How It's Calculated
Divides feature tickets by total tickets and multiplies by 100.
feature_tickets ÷ tickets × 100Concrete Example
If 14 of 20 completed tickets were features, that's 70% feature work, strong new-capability output, though watch that bugs don't accumulate.
What Does a Healthy Score Look Like?
Aim for a sustainable balance, very high or very low values both signal problems.
Healthy
50–70% feature work
Watch Out
70–85%, may be neglecting bugs and debt
Needs Attention
Over 85% or under 30%, either extreme is unsustainable
What Moves This Metric?
Goes up when…
Sprint focus on new feature delivery for a product milestone
Bug backlog being manageable and well-controlled
Clear roadmap driving feature-heavy planning cycles
Goes down when…
Accumulating bug debt requiring more reactive bug-fix work
Technical debt paydown sprints reducing feature output
Post-launch stabilisation periods increasing maintenance work
Start Tracking Feature %
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