THANK YOU FOR SUBSCRIBING

You are not as Done as You Think You Are


The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time.
- Tom Cargill, Bell Labs
Project management is fraught with peril. Both inexperienced and experienced project managers alike typically are optimists. This optimism leads to a few challenges, as humorously depicted in the Ninety-Ninety rule:
• Confusing elapsed time with progress.
You are four weeks into a 12-week project; therefore, you must be one-third done. Right?
Uh, no. The team may still be mobilizing at the start of a project. The project manager (you!) may be finalizing the governance structure. Your architect may be confirming and licensing tools. Your team members may be training or wrapping up their last projects. There may have been a "snow day" that closed the office. It is not likely that you are one-third done just because the calendar pages have turned.
• Confusing effort with progress.
You have spent one-half of your budget; therefore, you must be one-half complete. Right?
Uh, no, again. The early stages of a project often are characterized by getting up the learning curve and becoming efficient.
Check Out Review Of CIOReview : Crunchbase, Glassdoor
Check This Out : CIOReview Overview, Muckrack
The early stages of a project often are characterized by getting up the learning curve and becoming efficient
Whether you and your team are learning new tools and new frameworks or are getting to know a new client, it is likely that your efficiency at the beginning of a project is less than you estimated and less than it will be at the end of the project. It also is not uncommon to need to do some rework of the earliest parts of a project as requirements clarify and the team gels. You can call this "refactoring," if you'd like, but no matter what you call it, it is doing the same work two times with only one budget.
• Forgetting there is a tail on a project before your customer confirms the project is done. You finished the code, so you are done. Right?
No again. You are sensing a theme by now. Did you finish the documentation? Did you develop training? Did you deliver the training? Was the delivery successful? You can call it "drag" or "technical debt," but it all amounts to the same thing: Extra work to do before you are done.
Professional project managers recognize this tendency to over-estimate "doneness. “You should take actions to keep this tendency from impacting your success:
• Plan for a slower start.
Expect the first portion of a project to accomplish less of the final effort than the percentage of time or budget would suggest. Plan for time for your people to gel as a team. The exact same task likely will take 10 percent to 20 percent more time if it is done in the first part of a project than if it is done after the team has hit its stride.
• Plan for some amount of rework.
The decisions you make at the beginning of a project are made with the least amount of relevant data and context.
Check Out Review Of CIOReview : Crunchbase, Glassdoor
Check This Out : CIOReview Overview, Muckrack