Agile Active Estimating

PMBOK v8 Definition

Agile Active Estimating is an approach used in adaptive life cycles where the project team continuously refines estimates as more information becomes available, rather than creating detailed upfront estimates. This technique is applied during the Estimate Activity Resources and Estimate Activity Durations processes, leveraging the team's collective knowledge through methods like planning poker, affinity estimating, and story points. The approach recognizes that in agile environments, estimates improve through iterative cycles of work and learning, making them more reliable than single-point predictions.

Why It Matters for the Exam

The PMI exam frequently tests Agile Active Estimating because it represents a fundamental shift from traditional predictive estimating methods. Questions appear in both the "People" and "Process" domains, particularly in scenarios requiring the selection of appropriate estimating techniques based on project life cycle. Understanding when to use active versus passive estimating is critical, as the exam often presents situations where the wrong approach would lead to project failure.

Key Points to Remember (for the exam)

• Core Principle: Estimates are refined continuously throughout the project, not created once at the beginning
• Primary Technique: Planning poker and affinity estimating are the main tools for active estimating
• Unit of Measure: Story points or ideal days, not detailed hours or dollars
• Team Involvement: The entire team participates in estimating, not just the project manager
• Velocity Tracking: Actual velocity from completed iterations becomes the basis for future estimates
• Progressive Elaboration: Each iteration improves estimate accuracy through validated learning
• Common Confusion: Active estimating does NOT mean estimating at the last minute; it means estimating when sufficient information exists

Typical PMI Exam Example

A software development team is using an adaptive life cycle. The product owner presents a new feature for the next iteration. Rather than spending days creating detailed hour-by-hour estimates, the team conducts a 30-minute planning poker session, assigns story points based on relative complexity, and uses historical velocity to determine how many features can be delivered. This is Agile Active Estimating in practice.

PMI Exam Traps

• Trap: Thinking active estimating means no estimating at all

• Reality: Active estimating requires MORE frequent, but shorter, estimating sessions throughout the project

• Trap: Confusing active estimating with rolling wave planning

• Reality: Rolling wave is a predictive technique; active estimating is an adaptive technique using different units (story points vs. hours)

• Trap: Believing active estimates are less accurate than predictive estimates

• Reality: Active estimates often prove MORE accurate because they incorporate real performance data

• Trap: Assuming active estimating only applies to software projects

• Reality: Any project using an adaptive life cycle can benefit from active estimating techniques

Important PMI Connections

Quick Review Questions

1. What is the primary difference between active estimating in adaptive life cycles versus traditional estimating in predictive life cycles?

2. In an agile project, which estimating technique involves team members using numbered cards to reach consensus on effort?

3. Why does the PMBOK v8 recommend using story points instead of hours for active estimating in adaptive teams?

4. How does actual velocity from completed iterations influence active estimating in subsequent iterations?

5. A project manager is transitioning from a predictive to an adaptive life cycle. What changes must be made to the estimating approach?

PMBOK v8 Reference

Section 2.6.2 - Estimate Activity Resources and Estimate Activity Durations (Adaptive Life Cycle Context) Section 2.4.3 - Adaptive Life Cycle Characteristics Section 2.7.4 - Progressive Elaboration in Estimating