The correct answer is C .
The key issue here is alignment with the business vision . The Eco-Spa is positioned as a natural, sustainable, mineral-rich wellness experience closely connected to the environment. Adding chlorine may solve one problem, but it risks undermining the core guest promise and the natural quality of the hydrotherapy experience.
Why C is correct:
* It recognizes that hygiene and safety matter.
* It also recognizes that the proposed solution may conflict with the intended product vision.
* AgilePM expects the team to balance business need, user value, technical feasibility, quality, compliance, and vision alignment .
* Therefore, rather than immediately accepting chlorination as a Must Have, the team should explore alternative hygiene methods that preserve the natural mineral experience.
Why the other options are incorrect:
* A sounds plausible, but it assumes chlorination is the right answer before exploring whether it fits the vision or whether acceptable alternatives exist.
* B is too absolute. Not all spa pools must necessarily use chlorine in the same way, and AgilePM would not support such blanket reasoning without considering context and alternatives.
* D is clearly wrong because hygiene cannot be deferred until after launch if it affects safety or compliance.
AgilePM perspective:
AgilePM emphasizes fitness for business purpose . A requirement is not truly valuable if it damages the very experience the project is meant to create. The correct response is to preserve both:
* guest safety and hygiene,
* and the Eco-Spa's natural, sustainable identity.
So the best answer is C .

The correct answer is A .
In AgilePM, stakeholder engagement is a core success factor. When an important business stakeholder such as Lee Tan , acting as a Business Advisor , is disengaged from review events and then complains about lack of visibility, the right response is not to bypass the problem with more reporting or to escalate immediately into command-and-control behavior. The AgilePM approach is to re-engage the stakeholder through communication, education, and collaboration .
That is why meeting with Lee to explain the value of Sprint Reviews and planning his engagement is the best answer.
Sprint Reviews, or their AgilePM equivalent collaborative review points, are not merely "project meetings." They are key opportunities to:
* inspect progress,
* review delivered value,
* gather feedback,
* align stakeholders,
* validate evolving needs,
* and improve the solution based on real input.
Lee's absence means he has missed the primary forum where transparency, feedback, and shared understanding are built. If he now feels unaware, the issue is not that Agile ceremonies failed him; it is that he has not been effectively engaged in them. Hira should therefore address the root cause by helping him understand their purpose and agreeing a practical way for him to participate.
Why A is correct:
This option reflects AgilePM because it:
* promotes active stakeholder involvement ,
* uses collaboration rather than authority ,
* addresses misunderstanding through communication and coaching ,
* treats engagement as a shared responsibility,
* and supports better ongoing participation instead of just compensating for disengagement.
It is also pragmatic. Hira can explore why Lee sees the reviews as a waste of time, clarify what decisions or insights he can gain from attending, and tailor his involvement so it is meaningful and efficient. That is consistent with agile leadership: remove barriers, improve understanding, and increase effective collaboration.
Why the other options are incorrect:
B). Provide Lee with Sprint summaries to keep him informed without wasting his time.
This is weaker because it accepts disengagement instead of improving it. Written summaries may help supplement communication, but AgilePM does not favor passive reporting as a substitute for active collaboration when stakeholder participation is important. Lee's role as Business Advisor means his input is valuable, not just his awareness.
C). Ask Sarah to require Lee ' s attendance at all Sprint Reviews.
This is not the best AgilePM response because it relies on authority and escalation rather than facilitation and engagement. AgilePM encourages commitment and collaboration, not forced participation as the first solution. Compelled attendance may create compliance, but not meaningful contribution.
D). Schedule briefings with Lee before each Sprint using Project Planning insights.
This is also not the best answer because it shifts communication into a more one-way briefing model and focuses before the Sprint rather than on review of actual outcomes. The main issue is Lee's lack of participation in the review and feedback loop. Pre-Sprint briefings do not replace the value of seeing increments, discussing results, and shaping next steps.
AgilePM perspective:
AgilePM places strong emphasis on:
* continuous and active business involvement ,
* collaborative reviews ,
* transparency of progress ,
* frequent feedback ,
* and empowered, informed stakeholders .
A Business Advisor is expected to contribute specialist business insight. If that role disengages, the Project Manager should work to restore useful participation, not simply route around it with more documents or top- down enforcement.
In this case, Lee's complaint about awareness is actually a sign that he needs better engagement with the agile process. Hira should respond by helping him understand that Sprint Reviews are valuable business touchpoints where he can see progress, influence direction, and remain informed in real time.
Therefore, from an AgilePM standpoint, A is the best answer because it reflects facilitative leadership, stakeholder engagement, and the agile principle of improving collaboration rather than replacing it with reports or mandates.

During the Foundations phase, Brinda Vyas organized a workshop that Hira facilitated. It was attended by Sukra Aroon, Mira, Lee Tan, and Developers from the two Delivery Teams. The goal was to define and align on what would be available for guests at the end of Project Increment 4.

Comprehensive and Detailed Step-by-Step Explanation:
Facilitating a productive workshop requires careful planning and management of participant interaction and focus. Option D is the most effective approach because it sets the tone for collaboration and alignment early in the workshop.
1. Importance of Establishing Principles for Interaction:
* Establishing basic principles for interaction ensures that participants understand the expectations, goals, and structure of the workshop.
* It helps create a positive environment where participants are encouraged to collaborate, contribute ideas freely, and stay on track.
* This aligns with AgilePM principles, which stress the importance of clear communication, collaboration, and shared understanding.
2. Analysis of the Options:
* Option A: Work through items without any limitations on the solution
* Allowing unlimited exploration may lead to unproductive discussions, scope creep, or a lack of focus. Agile workshops require time-boxing and prioritization to maintain direction and ensure results.
* Option B: Postpone discussion on practical changes until after the workshop has finished
* Deferring discussions on practical implementation undermines the purpose of the workshop, which is to co-design actionable solutions. Agile encourages iterative discussions and addressing practicalities in real-time.
* Option C: Place a time-limited focus onto the delivery of the workshop ' s outputs
* While time-limiting focus is a good practice, this option overlooks the critical role of setting expectations and fostering collaboration. Without clear principles for interaction, time limits alone may not lead to productive outcomes.
* Option D: Establish and discuss basic principles for interaction at the start of the workshop (Correct Answer)
* Setting ground rules ensures participants remain aligned with the goals and are motivated to contribute productively. It minimizes potential conflicts, distractions, and misaligned expectations, fostering a collaborative atmosphere.
3. Application in UniCo's Scenario:
* In the UniCo case, where integration and cultural shifts are key, establishing principles such as respect for diverse viewpoints (Selco vs. UniCo staff) and focusing on actionable outputs would encourage productive discussions.
* Discussing principles ensures buy-in from participants and helps reduce resistance to change.
4. Agile Practitioner Documentation References:
* Workshops in AgilePM: AgilePM emphasizes creating structured workshops with defined roles, expectations, and interaction principles to maximize productivity.
* Agile Values - Individuals and Interactions: Clear guidelines for collaboration are foundational to achieving meaningful results in workshops.
* Facilitation Techniques: Best practices include setting principles such as time-boxing, respecting all inputs, and focusing on actionable outputs.
References:
Agile Project Management Handbook, Chapter 7: Facilitation and Workshop Best Practices Agile Manifesto Principle: Individuals and Interactions Over Processes and Tools Agile Facilitation Guidelines: Establishing Ground Rules for Effective Workshops

A: Yes, because acceptance criteria can only be understood at a high level during Foundations and will always need further investigation.
Rationale:
In Agile Project Management, while the Foundations phase does involve setting high-level expectations and a prioritized requirements list, the detailed acceptance criteria are often refined during the actual Solution Development iterations or timeboxes. This is because, as the work progresses, the team's understanding of the product grows, and they are better equipped to define detailed acceptance criteria that align closely with the customer's needs and the project's evolving context. It's a collaborative and iterative process, allowing for greater precision in defining what will make a particular feature or requirement acceptable.