How is a team's estimating typically performed?

How is a team's estimating typically performed?

• A. Using hours
• B. Using capacity planning only
• C. Using guesswork
• D. Using relative estimating and normalizing story points

Answer: (D)

In scaled agile estimation, teams size work using a relative measure rather than clocking hours. They assign story points to backlog items to reflect relative effort, complexity, and risk compared with a baseline item. By normalizing these points across all teams, you create a common velocity that can be used for reliable forecasting and planning across the program and PI horizon. This approach handles differences in team speed and context, making it easier to compare work and forecast capacity. Using hours ties estimates to individual pace and calendar availability, which can vary widely between teams and over time, making aggregation and cross-team planning messy. Capacity planning alone misses the size and complexity of work, so it can't reliably forecast throughput. Guesswork is unpredictable and wastes alignment time. Relative estimating with normalized story points avoids these pitfalls and provides a consistent, scalable way to plan, forecast, and coordinate large initiatives.

In scaled agile estimation, teams size work using a relative measure rather than clocking hours. They assign story points to backlog items to reflect relative effort, complexity, and risk compared with a baseline item. By normalizing these points across all teams, you create a common velocity that can be used for reliable forecasting and planning across the program and PI horizon. This approach handles differences in team speed and context, making it easier to compare work and forecast capacity.

Using hours ties estimates to individual pace and calendar availability, which can vary widely between teams and over time, making aggregation and cross-team planning messy. Capacity planning alone misses the size and complexity of work, so it can't reliably forecast throughput. Guesswork is unpredictable and wastes alignment time. Relative estimating with normalized story points avoids these pitfalls and provides a consistent, scalable way to plan, forecast, and coordinate large initiatives.