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 answer is B .
In AgilePM, when the end date is fixed , the primary control mechanism is not to move time, but to manage scope intelligently . That is exactly what MoSCoW prioritization is for.
Why B is correct:
* AgilePM protects delivery dates by ensuring that Must Have requirements are delivered first.
* Lower-priority items such as Should Have and Could Have can be deferred, reduced, or reshaped if time becomes constrained.
* This preserves business viability while maintaining control.
Why the other options are weaker:
* A is too narrow. Compliance may be critical, but AgilePM would not automatically prioritize all compliance work ahead of everything else without using agreed prioritization logic.
* C is not the primary AgilePM response. Adding temporary resources is not always effective and may introduce more complexity.
* D conflicts with the principle of protecting time. AgilePM generally fixes time and cost, flexing scope where needed.
So the most appropriate AgilePM response is B .

Explanation:
For each of the descriptions in Column 1, the maintainability objective from Column 2 that each would support is as follows:
* Off-the-shelf software with ready-to-use templates that will need to be customised to fully meet Hoy Hall requirements, after deployment.
* A. Maintainability is a required attribute of the initial delivered solution
* Rationale: Customizing off-the-shelf software indicates a need for the solution to be maintainable from the onset to allow for these adjustments.
* Developing a fully functioning in-house system, developed and hosted by Architecture Angels IT Operations team.
* A. Maintainability is a required attribute of the initial delivered solution
* Rationale: In-house developed systems need to be maintainable to facilitate future changes and enhancements by the team that created them.
* All-in-one web-based reservation and accommodation management system built to Hoy Hall's specification.
* A. Maintainability is a required attribute of the initial delivered solution
* Rationale: A system built to specific requirements will require the ability to maintain and adjust the system as needs evolve, making maintainability a key initial attribute.
* All bookings for Hoy Hall to be scheduled by one of the other two hotels within the group, until a suitable system can be implemented at the site.
* C. Short-term, tactical solution
* Rationale: This is clearly a temporary measure until a proper system is in place, indicative of a tactical solution to address immediate needs.
* A spreadsheet is used to capture customer details manually. Data will then be exported into a fully functional system at a later date.
* C. Short-term, tactical solution
* Rationale: Using a spreadsheet is a stop-gap solution to manage information in the short term, emphasizing the tactical nature rather than long-term maintainability.
Option B is not selected for any of the descriptions as none of them imply an approach of delivering first with the intention to re-engineer later. They all suggest a need for immediate maintainability or a short-term fix, not a re-engineering approach.