The correct answers are A and C .

Aromatherapy oil sales are a new idea outside the original scope , so AgilePM would handle this through collaborative assessment and prioritization , not automatic acceptance or unnecessary bureaucracy.

Why A is correct

“Hold a workshop to assess feasibility and document assumptions.”

This fits AgilePM very well because new ideas should be:

explored collaboratively,

assessed for feasibility and impact,

discussed across business and technical roles,

and understood before being committed.

A workshop is an agile way to bring together the right perspectives quickly.

Why C is correct

“Use MoSCoW prioritization to determine its importance against existing objectives.”

This is also fully aligned with AgilePM. Once the idea is understood, it should be assessed against:

current business goals,

existing priorities,

available time and capacity,

and the likely value it contributes.

MoSCoW is the right mechanism for deciding whether it belongs in the current increment or later.

Why the other options are incorrect

B is too hasty. Alignment with vision alone does not mean the item should be added immediately.

D is too heavyweight for this kind of incremental scope discussion.

E is too dismissive. AgilePM does not say new ideas must always wait until after delivery.

So the best answers are A, C .

The correct answer is C .

In AgilePM, the strongest way to combine agile leadership with practical delivery control is to create direct collaboration between the Delivery Teams around the work that must fit together. In this case, the Spa infrastructure team and the Spa operations/treatments team are working on interdependent outputs. The best way to keep those outputs aligned is for the teams to agree shared acceptance criteria for the items that depend on one another.

That makes C the best answer because it is both:

agile in leadership style , since it empowers the teams to collaborate and define quality expectations together, and

practical in execution , since shared acceptance criteria give both teams a concrete basis for building compatible deliverables.

For example, if a hydrotherapy treatment is planned, the infrastructure team and treatment team may need shared criteria covering:

space layout,

water systems,

safety controls,

guest flow,

environmental standards,

equipment readiness,

and operational usability.

Without this shared definition, one team could deliver something technically complete but not actually usable by the other.

Why C is correct from an AgilePM perspective:

AgilePM supports:

collaboration across roles and teams ,

shared understanding of requirements and outcomes ,

fitness for business purpose ,

early clarification of dependencies ,

and empowered teams working within a coordinated framework .

Shared acceptance criteria are a very effective mechanism because they:

turn vague alignment into clear, testable expectations,

expose dependency risks early,

reduce rework,

improve communication across teams,

and help ensure the integrated solution works as intended.

Why the other options are less suitable:

A. Empower Team Leaders to resolve dependencies, escalating major issues to Sukra for a solution-wide view if needed.

This is reasonable, but it is not the best answer. It relies on “Team Leaders” rather than direct team collaboration, and it focuses more on escalation management than on creating a shared working agreement. AgilePM prefers empowering the teams themselves and resolving dependencies through collaboration as close to the work as possible.

B. Empower Team Leaders to independently handle alignment through informal discussions, documenting key decisions for later review.

This is weaker because “informal discussions” alone are too loose for managing important inter-team dependencies. Alignment needs something more concrete than conversations that are only documented afterward.

D. Encourage Delivery Teams to define shared acceptance criteria for interdependent deliverables and Brinda approving.

This is close, but the addition of Brinda approving makes it less agile. Brinda, as Business Visionary, is important for vision and business alignment, but she should not be drawn into approving detailed inter-team acceptance criteria unless there is a specific business reason. This risks slowing down delivery and reducing team empowerment.

E. Hold a joint Retrospective after each Sprint to review alignment and identify remedial actions to ensure alignment.

Retrospectives are valuable, but this is mainly reactive . It helps improve after issues appear, whereas shared acceptance criteria help prevent misalignment before or during delivery.

F. Hold a joint Retrospective after each Sprint so Team Leaders can share learning and provide feedback.

Again, useful but not the strongest answer. It supports learning, but not direct practical alignment of interdependent deliverables.

G. Use hierarchical reporting where decisions would be documented collaboratively between Brinda Vyas, Mira Bachar, Hira and Sukra Aroon.

This is not very AgilePM-aligned because it introduces a more bureaucratic reporting structure. AgilePM favors collaboration and timely decision-making over hierarchical control.

H. Use hierarchical reporting where changes can be escalated and approved quickly allowing the Delivery Teams to progress.

This is also too command-and-control in style. Agile leadership aims to reduce unnecessary hierarchy and enable teams to work together effectively, not depend on approval chains as the main coordination mechanism.

AgilePM perspective:

This question is really about balancing two needs:

leadership through empowerment and collaboration , and

practical governance through clear quality expectations .

Option C does both. It avoids excessive control, but it also avoids vague coordination. It gives the teams a practical tool to align their work while maintaining agility.

Therefore, the best AgilePM answer is C .

The correct answers are B and E .

In AgilePM, risk management is both team-level and project-level . Risks should be handled at the lowest appropriate level first , with collaboration and visibility, and then aligned upward when they could affect wider priorities, architecture, business value, or delivery plans.

This scenario involves a technical integration risk between the Spa systems and the resort’s client management system. That kind of risk should not automatically be pushed upward for others to solve, nor should it be handled in isolation by one person. AgilePM favors a collaborative, transparent, and proportionate response .

Why B is correct

“The Delivery Team should address technical challenges collaboratively while keeping project-level roles informed.”

This is strongly aligned with AgilePM because:

the Delivery Team is closest to the work and best placed to explore the issue first,

technical risks should be surfaced early and addressed collaboratively,

and relevant project roles should stay informed in case the issue affects broader delivery, dependencies, architecture, or business priorities.

AgilePM does not encourage unnecessary escalation of every problem. Teams are empowered to work through delivery issues where possible. At the same time, transparency matters, so project-level roles such as Hira and Sukra should not be left unaware of a risk that could grow.

Why E is correct

“Hira should coordinate with Sukra Aroon and Brinda Vyas to align team risk management activities with overall project priorities.”

This also fits AgilePM very well. If an integration risk has the potential to affect:

solution integrity,

business outcomes,

scope decisions,

sequencing,

or delivery trade-offs,

then Hira, as Project Manager, should help ensure that team-level mitigation is aligned with the wider project context.

Why these specific roles matter:

Sukra Aroon brings architectural and technical oversight.

Brinda Vyas safeguards alignment with the project vision and business priorities.

Hira ensures coordination, visibility, and alignment across the project.

This reflects AgilePM’s principle that risk management is shared , not isolated.

Why the other options are incorrect

A. Escalate immediately to Hira who will devise and implement a mitigation plan.

This is too centralized. AgilePM does not say every identified risk should immediately be handed to the Project Manager to solve personally. The Delivery Team should first engage with the issue directly where appropriate.

C. Hira should instruct Sukra Aroon to resolve the issue independently to ensure there is no risk to the overall solution.

This is not AgilePM-aligned because it isolates the risk with one technical authority. Sukra’s input is important, but integration risks usually need collaboration with the team, not independent resolution in a silo.

D. The Delivery Team should escalate to project level roles and focus on other work until a resolution is found.

This is too passive and reduces team ownership. Unless the risk fully blocks progress, the team should actively collaborate on the issue and continue managing work intelligently rather than simply waiting.

AgilePM perspective

AgilePM encourages:

early identification of risk ,

team ownership where appropriate ,

cross-role collaboration ,

visibility to project leadership ,

and alignment of local actions with overall business and technical priorities .

So the best two answers are:

B, E

The correct answers are C and E .

This is a classic business availability and decision-latency risk in AgilePM. The problem is not just that Brinda is absent. The bigger issue is that the Business Visionary input is missing at a time when strategic adjustments are affecting delivery decisions . That creates a real risk of:

misalignment with the project vision,

unnecessary assumptions,

frustration in the Delivery Teams,

and costly rework.

AgilePM relies heavily on active business involvement . When a key business role becomes unavailable, the right response is to restore decision-making guidance quickly and protect the teams from working blindly on uncertain items .

Why C is correct

“Hira should engage other business stakeholders to assume Brinda Vyas ' responsibilities to ensure the Delivery Teams receives strategic guidance.”

This aligns strongly with AgilePM.

Hira, as Project Manager, should act to restore the missing business guidance by coordinating with suitable business stakeholders who can temporarily support or cover the gap. AgilePM does not encourage leaving teams without access to strategic direction. It also does not assume that work should continue normally when a key business authority is unavailable.

This response is good because it:

maintains business engagement,

reduces decision delays,

protects alignment with the vision,

and helps the Delivery Teams continue with informed guidance.

In AgilePM, if a critical role is unavailable, the project should adapt so the necessary business input remains accessible.

Why E is correct

“The Delivery Teams should focus on backlog items with clear business direction and pause tasks that require Brinda Vyas ' input until guidance is available.”

This is also very AgilePM-aligned.

It is a practical risk response that avoids reckless progress based on guesswork. Teams should keep moving where the direction is already clear, but they should avoid pushing ahead on items that depend on missing strategic clarification.

This balances:

maintaining momentum,

avoiding unnecessary delay across all work,

and reducing the risk of rework on unclear items.

That is exactly the kind of sensible, adaptive delivery behavior AgilePM supports.

Why the other options are incorrect

A. Continue increment work based on the backlog, assuming adjustments can be made when Brinda Vyas returns.

This is not a good AgilePM response because it normalizes working with outdated or incomplete strategic guidance. If recent strategic changes have not been communicated, continuing as normal increases the risk of building the wrong thing.

B. Mira Bachar and the Delivery Teams should document assumptions behind decisions and continue progress without validation.

Documenting assumptions is better than ignoring them, but continuing without validation is still too risky in this scenario. AgilePM values transparency, but it does not support knowingly progressing on uncertain strategic assumptions when better escalation and stakeholder engagement are possible.

D. Hira should escalate to Sarah Lark, the Business Sponsor, to replace Brinda Vyas with another qualified Business Visionary.

This may become necessary if the absence is prolonged or the project is materially threatened, but it is too strong as the best immediate response here. AgilePM would first look to restore business guidance through practical engagement and controlled work selection before moving to formal replacement.

AgilePM perspective

AgilePM expects:

active and timely business input,

collaborative response to risks,

continued delivery where direction is clear,

and escalation or substitution when critical decision-making is missing.

So the best way to handle this risk is to:

restore business guidance through other suitable stakeholders , and

limit work to items that have clear direction until ambiguity is resolved .

Therefore, the correct answers are:

C, E

The correct answers are A and E .

In AgilePM, effective risk management depends on shared responsibility, continuous awareness, and proactive behaviour across the whole team. Risk is not something handled only by one role, one document, or one event. It is woven into the way the team works every day.

Why A is correct

“Team members should adopt a collaborative mindset, sharing responsibility for identifying and mitigating risks.”

This aligns strongly with AgilePM. Risks emerge from many areas:

business priorities,

technical feasibility,

compliance,

dependencies,

stakeholder engagement,

and delivery constraints.

Because of that, the best way to manage risk is for the team to work collaboratively and raise concerns early. Different people see different risks:

Mira may see value or prioritization risk,

Sukra may see architecture or integration risk,

Hira may see coordination or dependency risk,

Wanida may see compliance risk,

Developers may see delivery feasibility risks.

AgilePM encourages a culture where risks are surfaced openly and addressed together rather than left to a single person.

Why E is correct

“Risk management should be proactive and part of daily activities, not a separate process.”

This is also a core AgilePM principle. Risk management is most effective when it is:

continuous,

visible,

built into team discussions,

and handled as part of normal delivery activity.

That means risks should be considered during:

planning,

backlog discussions,

reviews,

daily collaboration,

dependency conversations,

and stakeholder feedback.

AgilePM does not treat risk as something only reviewed in occasional formal meetings. The team should be alert to emerging issues and respond before they become major problems.

Why the other options are incorrect

B. Hira should have sole responsibility for managing all risks with clear accountability.

This is incorrect. Hira, as Project Manager, has an important role in coordinating risk management, but AgilePM does not place all risk responsibility on one person. Risk management is shared across business, technical, and delivery roles.

C. Developers should resolve all risks collaboratively and promptly without escalation.

This is incorrect because some risks should be escalated. AgilePM encourages teams to resolve issues at the right level, but not to avoid escalation when broader decisions, sponsorship, governance, or cross-team intervention are needed.

D. Sukra Aroon should handle all technical risks independently to ensure the solution is fit for purpose.

This is incorrect because even technical risks often require collaboration. Sukra contributes architectural leadership, but technical risks may affect priorities, cost, compliance, usability, and business outcomes, so they should not be handled in isolation.

AgilePM perspective

AgilePM supports team behaviour where:

everyone is alert to risk,

risks are discussed early,

people collaborate across roles,

escalation happens when needed,

and risk thinking is part of everyday delivery.

So the two statements that best describe appropriate team behaviour for effective risk management are:

A, E

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 .

For the XAN Insurance Company Web Project and considering the Agile Project Management approach, particularly the Dynamic Systems Development Method (DSDM) framework which emphasizes business value and active user involvement, the Business Case should justify the project in terms of cost, benefit, and risk.

Selected Statements for the Business Case:

D. The Sales Manager has calculated that the new coffee shop insurance product will increase revenues by 10% each week.

E. Market research shows that the number of coffee shop patrons taking legal action against retailers has increased by 200% over the past two years.

D. This statement provides a clear financial projection for the benefits of the project, which is a critical component of a Business Case. It quantifies the expected revenue increase, offering a tangible benefit to justify the project investment.

E. This statement outlines a market trend that necessitates the project, highlighting the increased demand for insurance due to rising legal actions against coffee shops. It underscores the relevance and timeliness of the project, adding to the justification for undertaking the project.

Why Other Statements Are Excluded:

A. While high-level functional and non-functional requirements are essential for project planning, they typically belong in project requirements documentation or the Project Brief, rather than the Business Case.

B. This statement provides market insight but does not directly justify the project from a cost-benefit-risk perspective. The relevance of selling Fairtrade products and alcohol to the insurance product project is tangential.

C. The request for a report on past sales provides background information but does not in itself justify the project investment. It might be used to inform the Business Case but is not a direct component of it.

In the context of Agile Project Management, it is crucial to have clear commitments regarding team members ' availability to ensure that project planning and execution can be as accurate and effective as possible. By securing a formal agreement on the hours the marketing assistants can dedicate to the project each week, the Project Manager can better plan tasks and allocate resources, thereby optimizing the team ' s capacity and ensuring that project timelines and deliverables are realistic and achievable.

To lead the Solution Development Team effectively during the first Structured Timebox, the Project Manager should:

C. Attend the Daily Stand-up and discuss any problems at the end.

Attending the Daily Stand-up meetings allows the Project Manager to stay informed about the team ' s progress, challenges, and any blockers they might be facing. It offers an opportunity for the Project Manager to provide support, guidance, and decision-making where necessary, without disrupting the team ' s autonomy and self-organization. This approach encourages open communication, quick resolution of issues, and maintains the Agile principle of collaboration and continuous improvement. Discussing problems at the end of the meeting ensures that any issues are addressed promptly, keeping the Timebox on track.

For the XAN Insurance Company Web Project, the plan for Post-Project activities should include actions and measures that will be undertaken after the project ' s deliverables have been implemented to ensure sustained benefits, monitor performance, and facilitate continuous improvement.

Selected Statements for the Plan for Post-Project Activities:

D. A report showing the number of application forms completed online through the website for coffee shop insurance policies will be produced weekly.

E. Once the new system has been deployed, the time it takes to process sales online will be compared with the time it takes to process new policies sold through telephone sales.

D. Producing a weekly report on the number of application forms completed online is a clear post-project activity. It provides ongoing monitoring of the project ' s impact and the effectiveness of the online system in attracting coffee shop insurance policies.

E. Comparing the processing times of online sales to telephone sales after the new system ' s deployment is an essential post-project activity. It evaluates the efficiency and effectiveness of the new online system, offering insights into improvements and adjustments that may be needed.

Why Other Statements Are Excluded:

A. Creating a company-wide email to show the number of policies sold by each sales assistant weekly is more related to internal sales performance monitoring and motivation rather than a specific post-project activity tied to the project ' s objectives.

B. Circulating a copy of the revised sales procedure before product deployment is a preparation step for the transition to the new system, rather than a post-project activity.

C. The Project Manager attending Daily Stand-up meetings is part of the ongoing project management and team coordination activities during the project, not a post-project activity.