Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
To Be Accurate...
Curt Finch is the CEO of Journyx.
By paying attention to the time spent in the requirements and specifications phases, and correlating estimates to timesheet data, you can more accurately predict and track overall project length. If more companies did, fewer undoable projects would ever start.
Have you ever worked in a place where 10 percent of 10 projects got done instead of 100 percent of one project? Ultimately, nothing is accomplished and everyone is totally stressed out. Inaccurate estimates cause over-commitment of time, yet not much gets done. Inaccurate estimates also cause bad decisions. “Inaccurate” usually means “too low.” When this happens, the return on investment (ROI) calculation shows the project as ‘worth it’ when it is not.
How can you stop wasting your company’s resources on projects that are not worth corporate time? Robert Grady’s book, Practical Software Metrics for Project Management and Process Improvement, gave us the answer more than a decade ago. In it, Grady provides a few insightful rules of thumb that are backed up by real numbers, such as: 6-8 percent of software project time is spent in the requirements and specifications phase. This is based on statistics from numerous software projects at Hewlett-Packard, so the percentage at your company may be different. The good news is that for projects of a particular flavor, you will find that the percentage usually doesn’t vary …
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"Judge a man by his questions rather than his answers." - Voltaire |