A. Provision of a secondary exit from the upstairs of the building will ensure compliance with national fire safety regulations.

Rationale:

Compliance with national fire safety regulations is non-negotiable and would be a legal requirement for the operation of the hotel. Therefore, any features required to meet these regulations would automatically be classified as " Must Have " due to their mandatory nature for safety and legal operation.

Advise how the legislation on the transfer of data will affect the requirements and the system.

E. Business Analyst

Agree the changes needed to the corporate technical architecture with the Architecture Angels IT support team.

D. Technical Coordinator

Ensure the information security vulnerability is communicated to the AA Head Office IT Director.

A. Project Manager

Evaluate the impact of proposed security controls on the business and decide on the most suitable solution.

B. Business Sponsor

Reprioritise the requirements on the Prioritised Requirements List associated with the security issue.

C. Business Visionary

Rationale:

A Business Analyst typically has the expertise to understand and communicate how data transfer legislation impacts system requirements.

The Technical Coordinator is usually responsible for technical decisions, including those that impact the technical architecture, and would work closely with the IT support team to agree on changes.

The Project Manager should ensure that key information, such as security vulnerabilities, is communicated to senior management, in this case, the IT Director.

The Business Sponsor, who is ultimately responsible for the project from a business perspective, would evaluate the impact of security measures on the business.

The Business Visionary is often tasked with understanding the strategic view of the project requirements and would be suited to reprioritize requirements, especially those with significant implications like security issues.

The Facilitator should invite the following two individuals to participate in the Workshop:

D. IT Operations Manager (Solution Development Team) E. Marketing Director (Business Visionary)

The rationale for this selection is that the disagreement is between the Marketing Director, who wants the reservation system to have professional photos and video tours (which impacts how the system will be used by potential customers and affects marketing strategy), and the IT Operations Manager, who is concerned with the system ' s technical limitations and maintenance. Both of these individuals are key to resolving the issue at hand, as they represent the conflicting requirements that need to be reconciled for the project to move forward.

C. No, because by the end of Foundations the quality expectations and overall acceptance criteria for at least the first increment should have been set, and high-level acceptance criteria set for later increments.

Rationale:

In Agile Project Management, it ' s important to establish high-level acceptance criteria early in the project to guide development and ensure that the solution meets the business needs and quality expectations. The Foundations phase is when the project ' s scope, objectives, and methods are defined, including the acceptance criteria for the first increment and at a high level for subsequent increments. This ensures that everyone has a clear understanding of what " done " looks like before development begins, reducing the risk of misalignment and rework.

The correct answer is F .

This issue happened because there was a failure of cross-team alignment between business intent and technical implementation . The treatments being developed required a specific infrastructure capability, but that dependency was not properly translated into prioritized, shared understanding during planning.

In AgilePM, the most effective way to prevent this is through active collaboration between the business/value role and the solution/technical role . That is exactly what option F describes.

Why F is correct:

Mira Bachar represents the business need and delivery priorities.

Sukra Aroon ensures solution integrity and technical feasibility.

Hydrotherapy is not just a treatment idea; it has infrastructure implications .

Therefore, during Sprint Planning, they should have worked together to make sure those requirements were:

understood,

prioritized,

communicated clearly,

and reflected in the work of the Infrastructure Team.

This is a strong AgilePM answer because it combines:

Agile leadership through collaboration rather than command-and-control,

practical coordination across dependent work,

and shared responsibility for making sure business goals are technically supported.

In this case, the plunge pool chilling capability was a critical enabling requirement. If Sukra and Mira had aligned early, the infrastructure team would have known that hydrotherapy capability was not optional or implicit, but a necessary requirement for the increment to deliver its intended value.

Why the other options are not the best answer:

A. Mira Bachar and Lee Tan should have worked together to integrate stakeholder feedback into the Product Backlogs before the next Sprint.

This is not the best answer because the issue was not mainly stakeholder feedback. It was a missed dependency between treatment design and infrastructure capability.

B. Mira Bachar should have amended the Product Backlogs to include explicit hydrotherapy infrastructure requirements for both Delivery Teams.

This is partly useful, but too one-sided. Mira alone should not be expected to define technically specific infrastructure requirements without collaboration from Sukra. AgilePM encourages joint work between business and technical roles.

C. Hira should have ensured transparency of the Delivery Plan so each Delivery Team could plan the remainder of their Sprints accordingly.

Transparency helps, but this would not by itself guarantee that the chilling requirement was recognized and built into the infrastructure solution.

D. Hira should have worked with Sukra Aroon to adjust project timelines to give flexibility to the Infrastructure Team and Treatments Teams before the next Sprint.

This is reactive and schedule-focused. The real problem was not insufficient time; it was missing alignment on a critical requirement.

E. Sukra Aroon should have documented hydrotherapy infrastructure requirements in the Solution Architecture Definition so the two Delivery Teams were aligned.

Documentation may help, but this is too document-centric for the best AgilePM answer. AgilePM prefers collaborative communication and shared understanding over relying primarily on formal documents.

G. Brinda Vyas and Hira should have ensured hydrotherapy treatments were align with business strategy.

Business strategy alignment is important, but it does not address the specific technical dependency that caused the failure.

H. Brinda Vyas should have worked with the Treatments Team to ensure hydrotherapy-related treatments are feasible within constraints.

This is not the best role fit. Feasibility is primarily a technical and solution concern, supported by the Solution Architect, not mainly the Business Visionary.

AgilePM perspective:

This question is about preventing integration failure across two Delivery Teams. AgilePM would favor:

early identification of dependencies,

collaboration between business and technical roles,

clear communication of enabling requirements,

and planning based on shared understanding of what is needed to deliver business value.

Hydrotherapy treatments only create value if the supporting infrastructure can actually enable them. So the business priority and the technical solution had to be connected during planning.

Therefore, the best AgilePM answer is F .