PMI-ACP · Question #720
The amount of information captured in the project's defects is varying within the development team. Team members are becoming frustrated with the defect quality inconsistencies and the frequent…
The correct answer is C. Generate insights at the next retrospective and adjust processes as decided by the team. The retrospective is the designated agile ceremony for inspecting and adapting team processes. Generating insights there and letting the team decide on solutions respects team autonomy and self-organization - a core agile principle. Stopping the iteration (A) is disruptive for…
Question
The amount of information captured in the project's defects is varying within the development team. Team members are becoming frustrated with the defect quality inconsistencies and the frequent clarification required. What should be done to address the issue?
Options
- AStop the current iteration to discuss defect quality issues and explore solutions.
- BDiscuss and explore solutions in the next planning meeting and take corrective actions as
- CGenerate insights at the next retrospective and adjust processes as decided by the team.
- DAssign corrective actions to the backlog for the team to identify the mandatory defect information.
How the community answered
(21 responses)- A5% (1)
- C86% (18)
- D10% (2)
Explanation
The retrospective is the designated agile ceremony for inspecting and adapting team processes. Generating insights there and letting the team decide on solutions respects team autonomy and self-organization - a core agile principle. Stopping the iteration (A) is disruptive for a process issue, not a blocking technical one. The planning meeting (B) is for sprint planning, not process improvement. Adding items to the backlog (D) treats a team process issue as a product task, which is the wrong venue and may indefinitely defer resolution.
Topics
Community Discussion
No community discussion yet for this question.