According to the PMBOK® Guide and the Agile Practice Guide, projects characterized by high uncertainty (such as those using adaptive, agile, or hybrid lifecycles) require a different approach to budgeting and estimation than traditional, predictive projects.
Lightweight Estimation: In high-uncertainty environments, detailed, long-term estimates are often inaccurate because requirements change frequently. Instead, teams use lightweight estimation methods. This involves high-level forecasts based on macro-level data, such as " T-shirt sizing " (Small, Medium, Large) or story points.
Just-in-Time Planning: Rather than spending significant time upfront on a detailed budget that will likely become obsolete, lightweight estimation allows for quick, iterative updates as more information becomes available. This is often referred to as " progressive elaboration. "
Flow and Velocity: Budgets in these environments are often based on the team ' s historical velocity or the cost per iteration, providing a flexible framework that can adapt to the " unknowns " of the project.
Why other options are incorrect:
Option A: Detailed estimation: This is also known as " bottom-up " estimating. While highly accurate for projects with stable, well-defined scopes, it is extremely inefficient and prone to error in high-uncertainty projects where the scope is constantly evolving.
Option C: Parametric estimation: This uses a mathematical model based on historical data and project parameters (e.g., cost per square foot). While useful for repetitive work, it lacks the flexibility needed to handle the unique uncertainties and " emergent " requirements of complex, adaptive projects.
Option D: A mix of them: While hybrid projects do exist, the specific recommendation for the " high uncertainty " component is to move away from rigid, heavy processes toward lightweight methods to maintain agility and avoid wasted planning effort.
