Comprehensive and Detailed In-Depth Explanation:
Extreme Programming (XP) emphasizes continuous feedback, early testing, and adaptive planning. When discrepancies arise, XP encourages identifying root causes and taking corrective actions without delaying value delivery.
Option D: Run a spike, identify what went wrong during implementation, and request a change to enhance value delivery (Correct Answer).
A spike is a time-boxed research activity used to explore a problem, test assumptions, and mitigate uncertainty in XP methodology.
By running a spike, the team analyzes what went wrong in implementation and applies the findings to ensure future iterations align with customer needs.
The PMI-RMP Guide states that “proactive risk response planning helps teams course-correct and maintain delivery momentum” (PMI-RMP Exam Prep Study Guide, 2021, p. 142).
The Agile Practice Guide supports the use of spikes, highlighting that “spikes allow agile teams to validate uncertainties in requirements, leading to more informed decision-making” (PMI & Agile Alliance, 2017, p. 89).
Option A: Release this version and leave changes to be done at the end of the project phase (Incorrect).
XP emphasizes continuous improvement and early defect resolution rather than postponing fixes.
Leaving changes until later may increase technical debt and reduce user satisfaction.
Option B: Arrange a workshop where all ideas will be discussed and take corrective actions ensuring value delivery (Partially Correct but Not the Best Answer).
While workshops help gather feedback, they do not provide technical validation of what went wrong.
A spike (Option D) is a better approach because it directly investigates the issue and leads to actionable changes.
Option C: Ask the development team to brainstorm and come up with suggestions that will improve the delivery date (Incorrect).
Brainstorming may generate ideas but does not analyze the root cause of the discrepancies.
Without a structured approach like a spike, there is a risk of guessing rather than using data-driven solutions.
Final Verdict:
The best answer is D (Run a spike, identify what went wrong during implementation, and request a change to enhance value delivery) because a spike provides empirical insights, leading to more effective corrective actions.
[References:, PMI. Agile Practice Guide (2017). PMI & Agile Alliance., PMI. PMI-RMP Exam Prep Study Guide (2021)., , , , , ]
