PMI-ACP Practice Questions #80
Your team is working on a mobile banking app with a critical release scheduled in two weeks. During a daily stand-up, a developer reported delays in integrating a third-party API since it is not working as expected. Further investigation by the scrum master revealed that the integration failed due to outdated documentation used by the team. When analyzed using the Five Whys technique, it was found that the vendor’s documentation updates were not regularly reviewed by the team. Additionally, frequent last-minute requirement changes diverted focus from verifying critical dependencies, leading to missed testing opportunities.
What should the team do to ensure such issues are avoided in the future, considering the release timeline remains unchanged?
A. Assign a dedicated team member to review all vendor documentation regularly.
B. Increase the sprint duration to allow more time for integration.
C. Conduct a root cause analysis in each retrospective for such failures.
D. Establish a norm to verify vendor dependencies and documentation while planning the work.
Analysis
The issue in this scenario stems from outdated vendor documentation, which caused integration failure and led to project delays. The Five Whys analysis revealed two primary root causes: (1) the team was not regularly reviewing vendor documentation updates, and (2) frequent last-minute requirement changes diverted attention from verifying dependencies. Since the release timeline remains unchanged, the team needs a preventive approach that ensures such issues do not recur without significantly altering the current workflow.
Analysis of Options:
A: Assign a dedicated team member to review all vendor documentation regularly.
This is not an ideal solution because it creates a single point of failure—if the assigned person misses an update or is unavailable, the issue could arise again. Agile teams focus on shared ownership rather than assigning responsibilities to a single individual.
B: Increase the sprint duration to allow more time for integration.
This option is not feasible because the release timeline is fixed. Extending the sprint does not address the root cause; it only provides temporary relief. The issue lies in missing dependency verification, not in the lack of time. Agile teams should focus on improving processes rather than modifying sprint durations arbitrarily.
C: Conduct a root cause analysis in each retrospective for such failures.
While retrospectives are valuable for continuous improvement, this option does not provide an immediate preventive solution for the critical release. Additionally, simply analyzing failures without implementing a concrete action plan does not prevent the issue from occurring again. A more direct solution is needed.
D: Establish a norm to verify vendor dependencies and documentation while planning the work.
This is the best option because it introduces a preventive measure without disrupting the workflow. By making vendor documentation verification a standard part of planning, the team can systematically check for updates and avoid last-minute surprises. This ensures that API integrations are planned with the latest information, reducing rework and integration failures.
Conclusion
The best approach is Option D (Establish a norm to verify vendor dependencies and documentation while planning the work) because it directly addresses the root cause and prevents recurrence. Option A creates dependency on one person, Option B does not fix the actual issue, and Option C lacks a proactive resolution.
PMI – ACP Exam Content Outline Mapping
| Domain | Task |
| Leadership | Empower Teams |
Topics Covered:
- Establish a norm to verify vendor dependencies and documentation as part of planning.
- Encourage proactive risk management by incorporating dependency verification into sprint planning.
- Foster a culture of shared responsibility instead of assigning critical tasks to a single individual.
- Ensure continuous improvement by integrating lessons learned into team practices.
- Minimize last-minute surprises by addressing external dependencies early in the development cycle.
If you’re preparing for the PMI Agile Certified Practitioner (PMI-ACP)® Exam, we highly recommend enrolling in our PMI-ACP® Exam Prep Program. Designed to provide a comprehensive Agile learning experience, this program not only helps you ace the PMI-ACP® exam but also enhances your Agile mindset, leadership skills, and ability to deliver value-driven projects. Ensure exam success and career growth with our expert-led, structured preparation program tailored for Agile professionals.
