What is the earliest warning sign that a software project will slip?

Open work with due dates after the project end date. It means the plan already does not fit, often weeks before anything is overdue. Scope being added faster than work is finished is a close second.

How much blocked work is too much?

More than about 20% of a project's work items blocked at once is a warning sign, and any item blocked for more than five days without a change needs an owner. Exentras raises a blocked-work alert above 20%.

How often should delivery leaders check for warning signs?

Weekly, at the same time, using the same checks on every project. Trends matter more than single readings: overdue work rising three weeks running is a stronger signal than one bad week.

Can these warning signs be monitored automatically?

Yes. Exentras computes them from Jira, team allocation and leave: they feed every project's risk score and delay forecast, and on Enterprise they also raise alerts ranked by severity.

Early Warning Signs a Software Project Will Slip

Updated 1 November 2026 · All guides

The short answer

Software projects rarely slip without warning; the signs are usually in the project data weeks earlier. The most reliable ones are work scheduled after the end date, overdue work growing week on week, more than about 20% of work blocked, scope added faster than it is finished, key people allocated beyond their capacity, and estimates or due dates missing on a growing share of the work. Check them weekly, on every project, and act when three or more appear together.

In the checks below, replace ABC with your Jira project key and the dates with your own.

Schedule signs

Open work is due after the project end date. The plan already does not fit. This often shows weeks before anything is overdue.
project = ABC AND statusCategory != Done AND duedate > "2027-03-31"
Overdue work is growing week on week. One overdue item is noise; a count that rises three weeks running is a trend.
project = ABC AND statusCategory != Done AND duedate < now()
Progress is behind plan two weeks running. Less work done than planned by now, whether you measure it with a burn-up chart or earned value (a schedule performance index below 1).
Milestone dates move quietly. A milestone that moves without a decision being recorded is a slip that has not been reported yet.

Flow signs

More than about 20% of work is blocked. At that level the team is spending its time waiting, not delivering.
project = ABC AND (status = Blocked OR Flagged is not EMPTY)
Blocked items have not moved in five days. Long blocks usually need someone outside the team to act.
project = ABC AND status = Blocked AND NOT status CHANGED AFTER -5d
Work in progress rises while completed work stays flat. The team is starting more than it finishes.
project = ABC AND statusCategory = "In Progress"
Scope is added faster than it is finished. Compare issues created with issues completed each week.
project = ABC AND created >= -1w against project = ABC AND resolved >= -1w

People signs

Key people are allocated beyond 100% across projects. Each project's plan looks fine on its own; together they cannot all happen. See capacity planning when people are on leave.
Leave clashes with a critical window. Approved leave for the one person who knows the payment integration, in the month it goes live.
The project has gone quiet. Fewer issues updated each week, with no drop in remaining work, usually means attention has moved elsewhere.
project = ABC AND updated >= -1w

Planning data signs

Estimates, due dates or assignees are missing on a growing share of work. The forecast cannot be trusted, so a slip will not be visible until it happens. See how to forecast a delivery date from Jira.
project = ABC AND statusCategory != Done AND (duedate is EMPTY OR assignee is EMPTY)

Signs you hear rather than measure

A task has been "90% done" for more than a week.
Status stays green while the answers to "what do you need?" get vaguer.
The same risk appears in three status reports in a row with no owner.
Questions about the date are answered with the scope ("it depends what we include").

These are worth noting, but confirm them with the data before escalating. The data signs are what make the conversation specific.

A ten-minute weekly routine

Run the checks above for every active project, or look at a tool that runs them for you.
Note which signs are present and whether each is new, the same or worse than last week.
Flag any project with three or more signs, or any single sign that has worsened for three weeks.
For each flagged project, agree one owner and one action with the project manager.
Report the flagged projects, causes and asks in the weekly executive status report.

Counting signs is a simple start. Weighting them into a single number per project is the next step, described in project risk scoring vs RAG status.

How Exentras watches for these signs

Exentras computes these signals from your Jira Cloud projects, team allocation and approved leave, so nobody has to run the searches each week. Overdue work, blocked work, work scheduled after the end date, schedule and cost performance, team overload and team activity all feed each project's 0–100 risk score and delay forecast, and planning data gaps lower the forecast's reliability rating.

On Enterprise, the same signals also raise alerts, ranked by severity: critical delay risk, work due after the project end date, schedule or cost performance below plan, more than 20% of work blocked, and people overloaded across projects. Read what software delivery intelligence is or compare plans.