PMP · Question #1310
While managing a project using a hybrid approach, the project manager realizes that there is a high level of rework due to quality issues. Because of that, each feature is taking longer than initially
The correct answer is A. Address the issue during the next sprint planning meeting.. In a hybrid project experiencing rework and quality issues causing feature delays, the project manager should address these concerns during the next sprint planning meeting.
Question
Options
- AAddress the issue during the next sprint planning meeting.
- BExtend the dates for future project milestones.
- CInitiate a change request to extend the project end date.
- DEscalate the issue to the project sponsor.
How the community answered
(32 responses)- A75% (24)
- B6% (2)
- C16% (5)
- D3% (1)
Why each option
In a hybrid project experiencing rework and quality issues causing feature delays, the project manager should address these concerns during the next sprint planning meeting.
In a hybrid or agile context, issues like rework and quality problems causing delays are best addressed at the earliest possible iterative planning session, such as a sprint planning meeting. This allows the team to collectively analyze the root causes, adjust the sprint backlog, refine estimation, and implement corrective actions for upcoming work cycles, aligning with agile principles of continuous improvement and adaptation.
Extending future milestones is a reactive measure that doesn't address the root cause of rework and quality issues, potentially allowing the problems to persist.
Initiating a change request to extend the project end date is a consequence management action, not a proactive step to resolve the underlying quality and rework problems that are causing delays.
Escalating to the project sponsor without first attempting to resolve the issue within the team's operational rhythm is premature and bypasses the project manager's responsibility for daily issue resolution in a hybrid environment.
Concept tested: Agile issue resolution in hybrid projects
Topics
Community Discussion
7A is your answer here. Think SPRINT for the exam: Sprint Planning Restores INspection and Team accountability. Rework and quality issues belong in the next sprint planning meeting, where the team can inspect, adapt, and fix the root cause before taking on new work.
Good call on A, and the SPRINT mnemonic is gold for memorization, though just a heads up that some exam questions will try to tempt you toward the sprint retrospective since that is technically where process inspection and adaptation happen, so read the stem carefully to see if the focus is on the work itself or the process.
Confirmed A on exam last week. In a hybrid setup you tackle quality problems at the next sprint planning meeting when the team can inspect the issue and adjust the approach together, rather than just pushing dates out.
Confirmed A on my exam last month. In a hybrid setup you handle rework and quality problems at the next sprint planning meeting when the team can adjust estimates and revisit the definition of done, rather than pushing dates around before fixing the root cause.
Agreed on A, and worth adding that you can simulate this exact scenario in Azure DevOps by creating a quick board, moving a story back to active mid-sprint, and watching how the burndown reacts, which makes the reasoning stick better than just memorizing it.
Going with C. Rework blowing the schedule means a formal change request is warranted.
Actually it is A. Rework means you are fixing something that did not meet quality requirements, so the quality management plan is where you look for the process to handle it, not the change control process.