AgilePM Practitioner Exam Preparation Material | Agile Project Management (AgilePM) Practitioner

Explanation:
The correct answer is A.
If the Developers have estimated work using Planning Poker and story points, the right next step is to use a planning approach that helps Hira understand how much work the teams can realistically complete in a Sprint. This supports forecasting the likely number of Sprints required.
Why A is correct:
It keeps estimation in the same agile framework.
It uses the team’s practical delivery capability to forecast Sprint outcomes.
It avoids false precision while still giving Hira a useful basis for planning.
Why the other options are incorrect:
B is incorrect because converting story points directly into person-days undermines the purpose of relative estimation and can create misleading precision.
C is incorrect because assigning average time allocations to every item is too mechanical and not how AgilePM typically uses story-point-based estimation.
D is incorrect because Planning Poker is already an appropriate technique. There is no need to discard it simply because Hira needs a forecast.
So the best answer is A.

Explanation:
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.

Explanation:
The best answers are B and E.
B is correct because AgilePM’s strongest reassurance comes from visible, embedded quality control. Making quality criteria explicit and ensuring teams confirm compliance before calling work “Done” shows that quality is being managed proactively, not assumed.
E is also correct because stakeholders are specifically worried due to problems in the India project. Reviewing those past issues and showing how Project Increment 4 is handling them differently directly addresses their concern with evidence and learning.
Why the others are weaker:
A is helpful, but it is more about visibility than about the strongest quality assurance mechanism.
C is too absolute; AgilePM helps manage quality, but it does not guarantee quality issues can never happen.
D introduces a heavier control layer that is not the primary AgilePM approach.
So the correct answers are B, E.