Skip to main content

Project status versus actual progress: how to measure the gap

Every project has two states: the status someone reports and the progress the work actually shows. Most of the time they roughly agree. When they do not, decisions get made on the wrong one. This guide explains the difference, how to measure it and what leaders can do about it.

By the Tarivra team · · 6 min read

Two different things

Project status is a summary someone chooses: Green, Amber or Red, a percentage complete, a line saying on track. It reflects what the person reporting believes, and what they are comfortable saying.

Actual progress is what the work shows: how much is done, how fast work is finishing, what is stuck and how much has been added since the start. It lives in the team's tools, in Jira, Azure DevOps, ServiceNow, GitHub or GitLab.

Status reporting accuracy is how closely the first matches the second. A team with high accuracy reports Amber when the work turns Amber. A team with low accuracy reports Green until the deadline.

Why they drift apart

  • Percent complete is measured by effort spent, not work finished. Ninety percent of the budget gone does not mean ninety percent done.
  • The last part takes longest. Testing, integration and fixes arrive at the end, when the status already says nearly done.
  • Scope grows quietly. New items are added to the backlog, but the date and the status stay the same.
  • Reports are written from memory, once a week, by someone who is also doing the work.
  • Nobody wants to be the first Amber. Optimism is rewarded until it is not.

How to measure actual progress

A handful of measures, taken from the work itself, tell you more than any report. Use the same ones for every project so they can be compared.

Finish rate

How many items does the team finish each week, and is that number rising or falling?

How to check:
Count items moved to Done per week for the last six to eight weeks.
Red flag:
A falling finish rate under a Green status.

Work left versus time left

At the real finish rate, will the open work be done by the target date?

How to check:
Divide the open items by the average weekly finish rate and compare with the weeks left.
Red flag:
More weeks of work left than weeks on the calendar.

Scope added

How much work has been added since the project started?

How to check:
Count items created after the start date as a share of the total.
Red flag:
Scope up by a fifth or more with no change to the date.

Stuck work

How much of the work in progress is blocked, overdue or untouched?

How to check:
Count open items flagged blocked, past their due date, or not updated in two weeks.
Red flag:
Stuck work growing week after week.

Measuring the gap itself

Once you have the measures, turn them into the status the work supports: Green when all are healthy, Amber when one or two are slipping, Red when the date cannot be met at the real pace. Then put that beside the reported status.

  • Same status: the report can be trusted this week.
  • Reported one step better than the work: worth a question, not an alarm.
  • Reported Green while the work says Red: the conversation to have today.

Track the gap over time. A team whose reports match the work most weeks has earned trust. A team whose reports run ahead of the work needs help, not blame: usually more support, a smaller scope or a new date.

How to close the gap

  • Report the evidence with the status: the finish rate, the work left and what is blocked.
  • Measure progress in finished items, not effort spent.
  • Re-forecast the date from the real pace whenever scope changes.
  • Make an early Amber safe and expected.
  • Check the same way across every tool your teams use, so nothing hides between them.

Where Tarivra fits

Tarivra does this comparison continuously. It reads the work in Jira, Azure DevOps, ServiceNow, GitHub and GitLab every 15 minutes, works out the status the work supports, puts it beside the status the team reports and scores how well they agree, with the items behind every check.

Questions

What is the difference between project status and project progress?

Status is the summary someone reports, such as Green or 80% complete. Progress is what the work shows: items finished, the finish rate, work left and work stuck. Status should follow progress; often it does not.

Why is percent complete misleading?

It is usually based on effort or budget spent, not on work finished. The hardest work often comes last, so a project can be 90% spent and far less than 90% done.

How do I measure status reporting accuracy?

Work out the status the work supports from a few measures, such as finish rate, work left against time left, scope added and stuck work, then compare it with the reported status week by week.