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 .

The correct answers are C and E .
AgilePM estimation should be:
* collaborative,
* proportionate,
* realistic,
* and open to refinement.
Why C is correct
"Allow flexibility and accept uncertainty in estimates that may be refined later." This is central to AgilePM. Estimates are expected to evolve as understanding improves. Early estimates are not fixed promises; they are informed forecasts based on current knowledge.
Why E is correct
"Use team-based estimation techniques as collective knowledge will improve accuracy." This also aligns strongly with AgilePM. Estimation benefits from the combined knowledge of the team because different people understand different aspects of the work, risks, and dependencies.
Why the other options are incorrect
* A is too detailed and heavy for the likely stage and context.
* B is wrong because Planning Poker supports relative/team-based estimation, but not "precise" early certainty.
* D is contrary to agile estimation. Estimates are not meant to be fixed and artificially precise.
So the best answers are C, E .

Topic 1, XAN Insurance Company Web Project
XAN Insurance Company Web Project
(Note:
Xan is a medium-sized insurance company with a worldwide
customer base and a strong presence on the internet. Its website
has been in operation for fifteen years. It operates from one location
- a large, open-plan office in the centre of a city. It is a friendly
company with no separate private offices for individual managers.
Staff members prefer to wander around the office space and have
one-to-one chats rather than use email or have lots of meetings.
The Marketing Director is considering a project to develop a new
area on the current web site to sell a new type of insurance directly
to the proprietors of coffee bars, insuring them against minor
accidents to staff and customers. The targeted coffee bars are
privately-owned franchises and are mostly situated in railway
stations, airports and shopping centres.
The Marketing Director has not yet decided whether the system will
just provide information about insurance policies online and give
quotations, the policies then being set up later by normal mailing
and telephone contact. Alternatively, it may be possible for the
system to provide the complete set-up and sale of an insurance
policy online. In this case the system would need to enable the
online capture and processing of credit card details and the issue of
an insurance policy.
The Finance Director has budgetary control over all projects in the
company and is reluctant to release finance for projects where the
outcome, timeframe and benefits are not clear.
Because of the uncertainty about the amount of development and
the length of time it may take, it is difficult to set a timeframe on this project. The Sales Manager, who reports to the Marketing Director, has insisted that the website extensions needed for this project must be operational within 12 weeks. The Sales Manager has a You have been brought in to give advice on how an Agile Project Management approach can be used to keep control of this project and to ensure that it delivers something useful to the business within 12 weeks.
After a brief feasibility assessment, conducted by the Sales
Manager, the Finance Director has decided to authorise a 12-week
project with the objective of producing a prototype system for
insurance for coffee bars, with a release at the end of that time. Six
selected coffee bars have agreed to complete an insurance
application form online, to trial the released website.

The correct answers are B and C .
During the Foundations phase in AgilePM, the goal is not to fully specify everything in exhaustive detail.
Instead, the aim is to establish enough shared understanding, scope, priorities, feasibility, and estimating confidence so the project can proceed sensibly.
Why B is correct
"Host a stakeholder workshop to prioritize integrating the Spa into the resort experience." This is strongly aligned with AgilePM because Foundations emphasizes:
* collaboration,
* shared understanding,
* business engagement,
* and early prioritization.
A stakeholder workshop helps clarify what matters most, align the increment with the business vision, and ensure the work is focused on delivering value.
Why C is correct
"Develop high-level estimates of effort and cost for Spa facilities and IT systems." This also aligns well with AgilePM. In Foundations, estimates should be:
* useful,
* proportionate,
* and appropriate to the current level of knowledge.
High-level estimates are exactly what AgilePM expects at this stage. They help planning and viability assessment without pretending to offer premature precision.
Why the other options are not the best answers
* A is incorrect because it pushes toward a fixed, fully analyzed specification, which is not AgilePM's approach.
* D may be useful in a general sense, but it is not as directly aligned with defining and estimating work as B and C.
* E is too detailed for Foundations. Work should be defined enough to begin sensibly, but not fully elaborated into detailed design-ready form across everything.
So the best answers are B, C .

The correct answer is A .
In AgilePM, the business case does not depend on having a fully fixed and detailed scope from the start.
Instead, it is based on:
* the business need ,
* expected benefits ,
* viability,
* and confidence that sufficient value can be delivered within agreed constraints.
Why A is correct:
* It correctly explains that AgilePM focuses on goals and benefits , not exhaustive detail upfront.
* It also correctly brings in MoSCoW prioritization , which helps ensure that the most important value is delivered first within fixed time and cost.
* This allows flexibility in lower-priority scope while maintaining investment control.
Why the other options are incorrect:
* B introduces incremental funding in a way that is not the core explanation here.
* C describes a predictive, fixed-scope model rather than AgilePM.
* D is too vague and does not directly explain how a business case can exist without detailed delivery certainty.
So the best answer is A .