Duration Estimates: Range, Probability, and Progressive Elaboration

PMBOK v8 Definition

Duration estimates are quantitative assessments of the likely number of work periods required to complete an activity, work package, or project. These estimates do not include any lags and may include an indication of the range of possible results. For example, a range of 2 weeks ± 2 days indicates the activity will take at least 8 days and not more than 12 (assuming a 5-day work week), or a 15% probability of exceeding 3 weeks indicates an 85% probability that the activity will take 3 weeks or less. Duration estimates are progressively elaborated as more detailed and precise data become available, improving accuracy and quality.

Why It Matters for the Exam

Duration estimates are frequently tested in PMI exam questions related to Schedule Management, particularly in questions about estimating techniques, accuracy ranges, and the distinction between effort and duration. Expect scenario-based questions where you must interpret duration ranges, identify what influences estimates, or recognize progressive elaboration.

Key Points to Remember (for the exam)

• Definition: Duration estimates = number of work periods (hours, days, weeks) to complete an activity with estimated resources. No lags included.
• Range Examples: "2 weeks ± 2 days" = 8 to 12 days (5-day work week). "15% probability of exceeding 3 weeks" = 85% probability of ≤ 3 weeks.
• Progressive Elaboration: Accuracy improves as more detailed and precise data become available about project engineering and design work.
• Key Inputs: Scope of work, required resource types/skill levels, estimated resource quantities, resource calendars.
• Influencing Factors: Constraints on duration, effort involved, type of resources, team experience, risk involved, schedule network analysis technique used.
• Effort vs. Duration: Effort = work required; Duration = work periods needed. Estimating both uses effort estimates and available resources.
• Fixed Duration Work: Some activities have intrinsic nature (e.g., 24-hour stress test) that takes predetermined time regardless of resource allocation.

Typical PMI Exam Example

A project manager estimates an activity will take 2 weeks ± 2 days. The team has 5-day work weeks. What is the range of possible completion times?
Answer: At least 8 days, not more than 12 days. This is a classic PMI question testing interpretation of range estimates.

PMI Exam Traps

• Trap: Confusing duration estimates with effort estimates
  Reality: Duration = work periods needed; Effort = amount of work required. They are different and require separate estimation.

• Trap: Thinking duration estimates include lags
  Reality: PMBOK v8 explicitly states "Duration estimates do not include any lags."

• Trap: Assuming all activities can be shortened by adding resources
  Reality: Some activities have intrinsic nature (e.g., 24-hour stress test) that takes predetermined time regardless of resource allocation.

• Trap: Ignoring progressive elaboration when accuracy improves
  Reality: As more detailed data become available, duration estimates improve in accuracy and quality.

Important PMI Connections

Quick Review Questions

1. A duration estimate of "4 weeks ± 5 days" with a 5-day work week represents what range of possible completion times?

2. What is the key benefit of the Estimate Activity Durations process?

3. Name three factors that may influence duration estimates according to PMBOK v8.

4. What does a "15% probability of exceeding 3 weeks" indicate about the likelihood of completing within 3 weeks?

5. Why might a 24-hour stress test take the same duration regardless of how many resources are assigned?

PMBOK v8 Reference

Section 2.4 - Schedule Performance Domain (Estimate Activity Durations process)

Note: The content above is derived exclusively from the PMBOK v8 RAG context provided. Duration estimates are part of the Schedule performance domain and involve determining the number of work periods needed to complete individual activities with estimated resources, using information from scope, resources, and calendars.