What is the 90 90 rule?
In this article9 sections
The 90/90 rule is a project management technique focused on accurate estimation, suggesting that the first 90% of a project takes 90% of the time, and the remaining 10% takes the other 90%. This highlights the common tendency to underestimate the final stages of a project, often due to unforeseen issues or scope creep.
Understanding the 90/90 Rule in Project Management
Have you ever wondered why projects often run over schedule, even when they seem close to completion? The 90/90 rule offers a compelling explanation. It’s a humorous yet insightful observation about the estimation process in project management.
This rule points out a common pitfall: the tendency to believe a project is nearly finished when it’s actually much further from completion than initially anticipated. This phenomenon can lead to significant deadline extensions and budget overruns if not properly managed.
What Exactly is the 90/90 Rule?
Coined by Tom Cargill of the Software Engineering Institute, the 90/90 rule is a pithy statement about the reality of completing complex tasks. It states:
"The first 90% of the code takes 90% of the time. The last 10% takes the other 90% of the time."
While originally applied to software development, this principle resonates across many industries and project types. It speaks to the human tendency to underestimate the time and effort required for the final, often intricate, details.
Why Does the 90/90 Rule Happen?
Several factors contribute to this estimation challenge. Understanding these reasons is key to mitigating their impact on your projects.
- Unforeseen Issues: As a project progresses, new problems inevitably arise. These could be technical glitches, integration challenges, or unexpected dependencies.
- Scope Creep: Client requests or team ideas can expand the project’s scope beyond the original plan. Each addition, no matter how small, can impact the timeline.
- Testing and Refinement: The final stages often involve rigorous testing, bug fixing, and fine-tuning. These activities can be time-consuming and difficult to predict accurately.
- Integration Complexity: Bringing together different components or systems can reveal compatibility issues that require significant effort to resolve.
- Optimism Bias: Project managers and teams may have an overly optimistic outlook, leading them to underestimate the effort needed for the final push.
Practical Examples of the 90/90 Rule
Imagine you’re building a custom website. You’ve completed all the design mockups, coded the main features, and populated the content. This might feel like 90% of the work.
However, the remaining 10% could involve:
- Cross-browser compatibility testing: Ensuring the site looks and functions correctly on all major browsers.
- Mobile responsiveness adjustments: Fine-tuning the layout for various screen sizes.
- Performance optimization: Speeding up load times through code and image optimization.
- Security audits and implementation: Addressing potential vulnerabilities.
- User acceptance testing (UAT): Gathering feedback from stakeholders and making final tweaks.
Each of these tasks, while seemingly small individually, can collectively consume a substantial amount of time, often exceeding initial expectations.
How to Mitigate the Impact of the 90/90 Rule
While you can’t eliminate the 90/90 rule entirely, you can implement strategies to manage its effects and improve your project estimations.
1. Break Down Projects into Smaller Tasks
The more granular your project breakdown, the more accurate your estimations are likely to be. This allows for better tracking of progress and identification of potential bottlenecks early on.
2. Build in Contingency Time
Always allocate buffer time for unforeseen issues. A common approach is to add a percentage (e.g., 15-25%) to your estimated timelines for each phase.
3. Involve the Entire Team in Estimations
Those closest to the work often have the most realistic understanding of the effort involved. Encourage team members to contribute to estimations for their respective tasks.
4. Use Historical Data
Review past projects to understand where delays typically occurred. This data can inform future estimations and highlight common pitfalls.
5. Prioritize and Manage Scope Effectively
Clearly define project scope from the outset and establish a robust change management process. This helps prevent uncontrolled scope creep.
6. Regular Progress Monitoring
Frequent check-ins and status updates are crucial. This allows for early detection of deviations from the plan and enables timely corrective actions.
The 90/90 Rule vs. Traditional Estimation Methods
Traditional estimation methods, like PERT or expert judgment, can be useful. However, they often struggle with the inherent uncertainty of the final project stages. The 90/90 rule serves as a reality check for these methods.
Consider a comparison of estimation approaches:
| Estimation Method | Strengths | Weaknesses | How it Addresses 90/90 Rule |
|---|---|---|---|
| Expert Judgment | Quick, leverages experience | Subjective, prone to optimism bias | Limited, relies on experience with final stages |
| Analogous Estimating | Based on similar past projects | Accuracy depends on similarity, may miss unique project aspects | Can be improved with data on final stage effort |
| Parametric Estimating | Data-driven, scalable | Requires reliable historical data, may not fit unique tasks | Can be applied to specific, repeatable tasks |
| Three-Point Estimating | Accounts for uncertainty (optimistic, pessimistic, most likely) | Still relies on accurate input for each point, can be complex to apply | Better than single-point, but still can underestimate the "last 10%" |
| Agile/Iterative | Adaptable, continuous feedback | Can be harder to predict long-term deadlines upfront | Embraces uncertainty and allows for re-estimation |
The 90/90 rule doesn’t replace these methods but rather complements them by highlighting a specific area of potential underestimation.
Who Benefits from Understanding the 90/90 Rule?
Anyone involved in planning and executing projects can benefit from this insight. This includes:
- Project Managers: To set more realistic expectations and timelines.
- Team Members: To better understand the challenges of project completion.
- Clients and Stakeholders: To have a clearer picture of project timelines and potential delays.
- Software Developers: The original audience, to improve their coding and estimation practices.
By acknowledging the 90/90 rule, you can foster a more realistic project environment. This leads to better planning, improved communication, and ultimately, more successful project outcomes.