The correct answer is A .

AgilePM supports progressive estimation , and relative estimation is one of the best ways to do that. It allows the Developers to provide useful estimates early without pretending to have a level of precision that is unrealistic at this stage.

Why A is correct:

Relative estimation is well suited to AgilePM because it supports early forecasting .

It accepts uncertainty while still giving the project enough information for planning.

Estimates can then be refined later as more detail emerges.

This fits AgilePM’s balance between:

planning and adaptability,

usefulness and realism,

and early direction without false precision.

Why the other options are incorrect:

B is incorrect because estimating everything in precise hours and days too early creates false certainty and is not consistent with AgilePM’s iterative approach.

C is weaker because although higher-priority work often gets more attention, AgilePM still needs a workable overall view of scope and effort. Ignoring lower-priority items entirely is not the best guidance.

D is incorrect because AgilePM does not say estimation is impossible in uncertain environments. It says estimation should be practical, transparent, and proportionate.

So the best answer is A .