PMP Process — Managing Technical Aspects Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Ask the team to accommodate the changes and work overtime to meet the original commitment

  Why it's wrong here

  In agile, demanding overtime to accommodate unmanaged priority changes directly contradicts the principle of sustainable pace and can lead to team burnout, reduced quality, and decreased morale. This approach fails to address the underlying issue of frequent changes and places an unsustainable burden on the development team, undermining the long-term health and productivity of the project.

• ✓

  Facilitate a retrospective where the team can discuss the impact of changing priorities and agree on a process

  Why this is correct

  A retrospective is the appropriate agile event for the entire team, including the Product Owner, to inspect and adapt their processes. By openly discussing the impact of frequent priority changes on sprint goals, team morale, and predictability, they can collaboratively identify root causes and agree on actionable improvements or a revised process for managing changes, embodying continuous improvement and self-organization.

• ✗

  Escalate to the project sponsor that the product owner is interfering with the team

  Why it's wrong here

  Prematurely escalating to the project sponsor bypasses the agile principle of self-organizing teams and collaborative problem-solving. This action can damage the relationship between the Product Owner and the development team, fostering an environment of distrust rather than partnership. As an agile leader, the primary role is to facilitate resolution within the team first, before resorting to hierarchical intervention.

• ✗

  Tell the product owner that scope changes are not allowed during a sprint

  Why it's wrong here

  While maintaining a stable sprint backlog is crucial for team focus and predictability, simply imposing a rule that scope changes are not allowed during a sprint is not an agile leadership approach. This ignores the Product Owner's accountability for maximizing value and responding to change. Instead, the agile leader should facilitate a discussion to educate the Product Owner on the impact of mid-sprint changes and collaboratively establish guidelines for managing emergent requirements, perhaps through backlog refinement or negotiation.