Engineering delivery guides
Each guide explains what a metric means, why it matters, how to calculate it from Jira, how to interpret it, common mistakes, and what an engineering manager can do about it — with a worked example. Written for engineering managers, directors and heads of engineering, Scrum Masters, TPMs and product managers.
Start with the delivery problem
- Engineering delivery intelligence: connect delivery signals to planning decisions.
- Jira sprint reports and analytics: explain changes to the original commitment.
- Sprint carryover analysis: separate engineering work from release waiting.
- Jira bottleneck analysis: find and investigate growing queues.
- Sprint capacity planning: account for carry-in before new work.
Explore the supporting metrics
Use the guides below to follow a signal into workflow, capacity, scope or epic delivery. Each explains its assumptions and includes a worked example.
Engineering Delivery Intelligence for Agile Teams
Understand missed commitments with Jira delivery signals: carryover, scope growth, capacity, review and QA queues, release waits and requirement-driven rework.
Read guide →Why Sprints Fail: The Seven Patterns Behind Missed Commitments
The recurring, measurable reasons sprints miss their commitments — over-commitment, scope creep, review and QA queues, release backlogs, dependencies, unclear requirements — and how to tell them apart with data.
Read guide →Jira Sprint Health: The Metrics That Actually Explain a Sprint
A practical guide to sprint health for engineering managers: commitment reliability, scope change, carryover and throughput — how to calculate them from Jira and what to do about them.
Read guide →Sprint Carryover: Understand Why Work Keeps Moving Between Sprints
How to calculate sprint carryover from a Jira export, classify it by reason (review, QA, release, blocked), and tell the difference between observed and inferred causes.
Read guide →Sprint Scope Creep: Measuring Work Added After Sprint Start
How to measure sprint scope creep from Jira — original commitment, added, removed, net growth — why CSV exports undercount it, and how engineering managers can control it.
Read guide →Jira Bottleneck Analysis: Find Where Delivery Gets Stuck
How to find delivery bottlenecks in an engineering workflow using queue size and time-in-stage, why arbitrary red/amber/green thresholds mislead, and what to do once you find the constraint.
Read guide →Cycle Time for Engineering Teams: Median, P85 and the Long Tail
What cycle time is, how it differs from lead time, how to calculate median and percentiles from Jira, why averages mislead, and why a CSV export alone cannot give you time per stage.
Read guide →Aging Work in Progress: Spotting At-Risk Work Before It Carries Over
How to measure the age of in-progress work, choose useful age buckets, compare against historical cycle time, and act on old work without turning it into blame.
Read guide →Sprint Capacity Planning with Historical Ranges, Not Guesses
Plan sprint commitments against historical throughput ranges instead of optimistic capacity math. Include existing WIP and typical scope growth, and communicate risk honestly.
Read guide →How to Reduce Sprint Carryover: A Playbook for Engineering Managers
A practical, evidence-first playbook for reducing sprint carryover: diagnose by stage, right-size commitments, limit WIP, and fix the constraint instead of pushing harder.
Read guide →Writing a Jira Sprint Report Leaders Will Actually Read
What a useful sprint report contains beyond the Jira burndown: commitment, scope change, carryover reasons, the constraint, and one or two decisions — with evidence levels stated.
Read guide →Software Delivery Metrics That Help Instead of Hurt
A leader's guide to software delivery metrics: flow metrics, sprint predictability and DORA, what each can and cannot tell you, and how to avoid turning metrics into targets.
Read guide →Engineering Team Capacity Planning: Plan From What You Deliver, Not What You Hope
A practical guide to engineering team capacity planning: capacity vs velocity and throughput, carryover and existing WIP, planned vs unplanned work, median throughput, and the mistakes that make sprints overcommit.
Read guide →Jira Capacity Planning: A Practical Guide
How to do capacity planning with Jira data: which fields to export, how to measure throughput, carryover and scope change from a Jira CSV, what needs sprint dates or change history, and what Jira cannot know.
Read guide →How to Calculate Sprint Capacity
A step-by-step method for calculating sprint capacity from historical throughput: median delivery, existing WIP, room for unplanned work, and why hour-based capacity formulas overcommit teams.
Read guide →Team Capacity vs Velocity: What Each Tells You and How to Use Them Together
Team capacity and velocity are often confused. Learn what each measures, why velocity is not a productivity score, how carryover distorts velocity, and how to combine them for realistic sprint commitments.
Read guide →Sprint Commitment vs Team Capacity: Why Teams Overcommit and How to Stop
Why sprint commitments drift above team capacity — carryover, existing WIP, scope growth — how to measure commitment accuracy without turning it into a performance metric, and how leaders can plan to demonstrated delivery.
Read guide →Planned vs Unplanned Engineering Work: How to Measure It Honestly
How to measure planned vs unplanned engineering work from Jira by when work entered the sprint — not by issue type — why bugs are not automatically unplanned, and how to reserve capacity for unplanned work.
Read guide →Engineering Throughput Explained: Measuring Delivery Without Gaming It
What engineering throughput is, how to calculate it from Jira in issues or points, why median and P75 beat averages, what flat throughput under rising demand means, and why throughput is a team measure.
Read guide →Why Work Keeps Carrying Over Between Sprints (and How to Tell Which Reason Is Yours)
The six recurring reasons work carries over between sprints — overcommitment, interruptions, WIP accumulation, testing and review queues, fragmentation — and how to tell them apart with Jira data.
Read guide →Engineering Interrupt Load: Measuring the Work That Arrives After Planning
How to measure engineering interrupt load from Jira — work added after sprint start as a share of all work handled — why not every addition is an interruption, and how to plan around it.
Read guide →Engineering Work Mix: Where a Team’s Sprint Actually Goes
How to measure an engineering team’s work mix from Jira — features, bugs, testing, review, technical debt, support, operational work and research — and how to use it to plan realistic sprints.
Read guide →WIP Debt: When Carryover Becomes the Same Work, Sprint After Sprint
What WIP debt is, how to measure recurring carryover and carryover age from the Jira Sprint field, why issues that carry three or four times need a decision, and how to pay the debt down.
Read guide →Sprint Context Switching: Measuring Fragmentation Without Tracking Hours
How to see context switching in sprint data without time tracking: work categories per sprint and per engineer, added work and existing WIP as indicators of fragmentation — and the limits of what Jira can show.
Read guide →Sprint Planning for Small Engineering Teams That Do Everything
A sprint planning method for small engineering teams whose engineers build features, fix bugs, test, review and support production: plan total demand, reserve room for interrupts, and pay down recurring WIP.
Read guide →How to Track Epic Progress in Jira (Without Being Misled by Percent Complete)
How to measure Jira epic progress honestly: issue-count and story-point progress, status distribution, why percent complete misleads when scope grows, and how carryover and WIP change the picture.
Read guide →Epic Burn-Up Charts Explained: Seeing Delivery and Scope Growth Together
What an epic burn-up chart shows, why it beats a single percent-complete number, how to build one from Jira history, and how to read changing scope without mistaking it for slow delivery.
Read guide →Engineering Initiative Progress: Tracking Major Work Across Many Sprints
How engineering leaders can track initiatives across sprints: the initiative → epic → story hierarchy, sprint contribution, delivery, scope, carryover and investment — from Jira data.
Read guide →Where Is Engineering Capacity Going? Measuring Investment Allocation
How to measure engineering investment allocation from Jira — strategic initiatives, features, bugs, technical debt, support and operational work — why it matters, and how to keep it from becoming a productivity metric.
Read guide →Epic Scope Creep: When Delivery Is Steady but the Finish Line Moves
How epic scope grows, why percent complete can fall while engineering delivers, how to tell a delivery slowdown from scope growth using Jira history, and what to do about it.
Read guide →Epic Carryover Across Sprints: When Initiatives Accumulate Unfinished Work
Epic-level carryover explained: sprint carryover by epic, recurring WIP, carryover age, why the same issues repeatedly carrying matters, and the questions engineering leaders should ask.
Read guide →Jira Epic Reporting for Engineering Leaders: One View of Progress, Scope, Investment and Flow
How to build a high-level Jira epic report that combines progress, scope growth, sprint investment, carryover, WIP and delivery flow — and avoids the two most misleading conclusions in initiative reporting.
Read guide →Requirements Quality: Find Gaps Before Development Starts
How to review Jira stories and bugs for requirement gaps — acceptance criteria, actor, expected behaviour, error handling, edge cases, testability — and how to connect clarity signals to rework and carryover without treating them as proof.
Read guide →