Free guide
Find out when a project is slipping two weeks in, not two weeks before the deadline.
Get the free 11-page PDF to see how continuous forecasting exposes changes in delivery risk while there is still time to respond.
Inside the guide
The guide follows a forecast from the project kickoff to the first warning that delivery is off track.
- Why can the initial forecast become unreliable?2
- What changes after the project begins?3
- Why are delays often discovered too late?5
- What changes when the forecast is updated continuously?6
- What can you do when the warning arrives earlier?9
- What does a continuous forecasting dashboard show?10
The problem with a one-time forecast
Your delivery date can stay fixed while the work underneath it keeps changing.
A forecast reflects what is known when it is run. Once the project begins, new work, split items and defects can change the delivery picture without changing the date you have committed to.
The project begins with a forecast
A delivery date is set using the scope and delivery data available at kickoff.
The work changes
New work arrives, items are split and defects are discovered as delivery continues.
The warning arrives late
The original forecast can be outdated before the schedule problem becomes visible.
About the author
The guide is written by Sonya Siderova, Founder and CEO of Nave.
Nave grew out of a product development team that was delivering just 25% of what it committed to. After adopting Kanban, the team began making decisions from delivery data instead of opinions. That experience eventually became Nave, a flow analytics platform trusted by 7,000+ delivery teams worldwide.
We’ll send the complete guide to your inbox.
Enter your first name and email to get the 11-page How to See Project Delays 2 Weeks In PDF at no cost.