Here the task is to identify which AgilePM principle is most significantly compromised in each case, based on the behavior or concern described.

1. Lee Tan is skeptical about agile ways of working and dismisses Sprint Reviews as a waste of time, creating tension and hindering collective alignment.

Answer: G — Communicate continuously and clearly

Sprint Reviews are a core mechanism for transparency, feedback, shared understanding, and alignment. If Lee dismisses them and creates tension around them, the biggest principle being undermined is continuous and clear communication .

Why not just Collaborate ?

That is also affected, but the most direct issue here is rejection of a structured communication and feedback forum. Sprint Reviews exist to keep business and delivery aligned through ongoing communication.

So the most significantly compromised principle is:

1 → G

2. Priya insists that all aspects of the aromatherapy oil, including packaging and marketing, must be fully defined before development, causing concern among teammates.

Answer: F — Develop iteratively

This directly conflicts with AgilePM’s belief that not everything must be fully detailed upfront. AgilePM supports evolving detail over time through learning, feedback, and iteration.

Priya’s position reflects a predictive mindset: define everything first, then build. AgilePM instead encourages starting from sufficient understanding and refining as the team learns more.

So the most significantly compromised principle is:

2 → F

3. Lee Tan is reluctant to release operational staff to act as Business Advisors for the Spa’s booking system, prioritizing short term efficiencies. He assumes business requirements are obvious and Developers can proceed without direct business input.

Answer: A — Focus on the business need

This is a strong violation of the principle of focusing on the business need . AgilePM depends on active business involvement to ensure that what is delivered genuinely meets operational and strategic needs.

If operational staff are not made available as Business Advisors, the team risks building a solution based on assumptions rather than real business understanding. That undermines the ability to ensure the solution is fit for business purpose.

Why not Collaborate ?

That is involved too, but the core failure is the assumption that delivery can proceed without direct business input. That most fundamentally threatens alignment to the real business need.

So the most significantly compromised principle is:

3 → A

4. Many Delivery Team members in Spa operations, marketing, and IT are part-time and their daily responsibilities are taking priority over project roles. Their limited availability raises concerns about meeting Sprint commitments.

Answer: B — Deliver on time

This concern most clearly threatens the AgilePM principle of delivering on time . If part-time participation and competing priorities reduce team capacity, Sprint commitments become unreliable and timeboxes are put at risk.

AgilePM places strong emphasis on protecting time and using prioritization and commitment to ensure timely delivery. If people are not sufficiently available, timely delivery becomes difficult.

Why not Demonstrate control ?

That could also be affected, but the scenario explicitly points to concern about meeting Sprint commitments, which most directly maps to delivery timeliness.

So the most significantly compromised principle is:

4 → B

5. IT developers worry that testing critical booking system integrations can only happen at the end of the Project Increment, rather than being embedded within each iteration.

Answer: D — Never compromise quality

This most directly undermines never compromise quality . AgilePM expects quality to be built in throughout delivery, not deferred until the end. Leaving critical integration testing until the end increases the risk of defects, surprises, rework, and unstable delivery outcomes.

Testing should be integrated into the iterative process so that quality is assessed continuously and problems are found early.

Why not Develop iteratively ?

Iterative development is also relevant, but the main concern here is not iteration itself. It is that quality assurance, especially critical integration testing, is being postponed. That most clearly violates the principle of protecting quality.

So the most significantly compromised principle is:

5 → D