The 0/100 rule in project management is a straightforward method for tracking the completion of work elements, particularly useful in earned value management (EVM). It dictates that a task or work package is only considered complete for reporting progress once it is 100% finished.
Understanding the 0/100 Rule
Based on the reference provided, using the 0/100 rule, no credit is earned for an element of work until it is finished. This means that even if a significant amount of effort has been put into a task, it contributes nothing to the reported progress until it is fully completed and delivered.
This approach provides a conservative view of project progress, as it avoids claiming partial credit for work in progress. It's especially effective for tasks that have a clear, single endpoint or deliverable.
How the 0/100 Rule Works in Practice
When applying the 0/100 rule to tasks or work packages:
- Start: When a task begins, its earned value (EV) is 0% of its planned value (PV).
- In Progress: As the task is being worked on, the earned value remains at 0% of its planned value. No partial credit is given.
- Completion: Only when the task is fully completed and meets all defined criteria does its earned value immediately jump to 100% of its planned value.
This binary approach simplifies progress reporting for individual items but requires clear definition of what constitutes "finished."
0/100 Rule vs. 50/50 Rule
The reference mentions a related approach: the 50/50 rule. Understanding the difference is key to choosing the right method for different types of tasks or projects.
| Feature | 0/100 Rule | 50/50 Rule |
|---|---|---|
| Credit Earned | 0% until 100% complete; then 100% | 50% upon start; remaining 50% upon 100% completion |
| Conservatism | More conservative view of progress | Less conservative, acknowledges work started |
| Task Suitability | Short tasks, tasks with clear finish points | Longer tasks, tasks where acknowledging 'started' is valuable |
As the reference states, a related rule is called the 50/50 rule, which means 50% credit is earned when an element of work is started, and the remaining 50% is earned upon completion. This contrasts directly with the 0/100 rule's all-or-nothing approach.
When to Use the 0/100 Rule
The 0/100 rule is often best suited for:
- Short-duration tasks: Where the time between starting and finishing is relatively brief, making partial credit less meaningful.
- Tasks with tangible, discrete deliverables: Such as writing a specific document, coding a module, or installing a piece of equipment.
- Milestones: While not tasks themselves, the principle applies – a milestone is either achieved (100%) or not (0%).
- Providing a conservative outlook: When project stakeholders prefer to only count completed work towards overall progress.
While simple, relying solely on the 0/100 rule for an entire project might mask potential issues on tasks that are started but stalled for long periods. Therefore, it's often used in conjunction with other methods or for specific types of tasks within a project.
