According to the PMBOK® Guide and the Agile Practice Guide, managing costs in an adaptive (Agile) environment differs significantly from predictive environments due to the high frequency of change and the focus on value-driven delivery.
Lightweight Estimation: Because requirements in Agile are progressively elaborated and subject to frequent change, detailed, bottom-up cost estimates for the entire project are often inaccurate and wasteful. Instead, teams use lightweight estimation methods such as Story Points, T-shirt Sizing, or Relative Sizing. These methods allow for quick " high-level " forecasts that can be refined as more information becomes available.
Embracing Change: In Agile, cost management is integrated into the iterative cycle. As new requirements arise or priorities shift during a Sprint, the " lightweight " nature of these estimates allows the project manager and team to adjust the forecast without the heavy administrative burden of a formal, rigid change control process for every minor cost deviation.
Fixed Budget/Variable Scope: Often, Agile projects operate with fixed costs (based on the team ' s burn rate per iteration) and a variable scope. Cost management focuses on ensuring that the team is working on the highest-value items first, ensuring the best return on investment (ROI) for the spent budget.
Analysis of Other Options:
B. Agile environments make cost aggregation more difficult: This is incorrect. Cost aggregation is often simpler in Agile because costs are typically tracked by the iteration (Sprint) or team velocity, rather than through complex, thousands-of-line-item WBS structures.
C. Agile environments make projects more costly and uncertain: Agile is specifically designed to reduce the financial risk of uncertainty by delivering value in small increments and allowing for early pivots. While it deals with uncertainty, it does not inherently make projects " more costly. "
D. Detailed cost calculations benefit from frequent changes: Frequent changes are actually the enemy of " detailed " cost calculations. If you perform a highly detailed cost analysis and the scope changes the next day, the effort spent on that calculation is wasted. This is why " lightweight " methods are preferred.
