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.

• ✗

  Escalate the issue to the project manager immediately.

  Why it's wrong here

  In a Scrum framework, the Scrum Master is primarily responsible for facilitating the removal of impediments that hinder the Development Team. Immediately escalating to a "project manager" is incorrect because a dedicated project manager role does not exist in pure Scrum; the Scrum Master fulfills many coordination aspects. The first step is for the Scrum Master to help the team address the impediment, not to immediately pass it on, especially to a non-Scrum role, as this bypasses the team's self-organizing capabilities.

• ✓

  Help the team assess the impact and discuss options to adjust the sprint backlog, then inform the product owner.

  Why this is correct

  As a Scrum Master, the primary responsibility is to serve the Development Team by removing impediments and facilitating their self-organization. This option correctly identifies the Scrum Master's role in guiding the team to assess the impact of the third-party dependency and collaboratively explore solutions or adjustments to the Sprint Backlog. Subsequently, informing the Product Owner is crucial for transparency and to enable them to make informed decisions regarding product value and potential scope changes for the current Sprint, ensuring alignment with the Sprint Goal.

• ✗

  Remove the task from the sprint and add it to the backlog.

  Why it's wrong here

  Arbitrarily removing a task from the Sprint Backlog and moving it to the Product Backlog without proper consultation is inappropriate. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Development Team and has the final say on Product Backlog content and prioritization. Such a significant change to the Sprint Goal or scope requires collaboration and agreement between the Development Team and the Product Owner, facilitated by the Scrum Master, to ensure alignment with product goals.

• ✗

  Tell the developer to work overtime to complete the task on time.

  Why it's wrong here

  Mandating overtime for a developer to meet a deadline is contrary to Agile principles, which emphasize sustainable pace and long-term team well-being. Such a directive can lead to burnout, decreased quality, and reduced team morale, ultimately hindering productivity and predictability. Agile frameworks prioritize delivering working software at a sustainable pace over short-term, unsustainable pushes, ensuring the team can maintain high quality and consistent output without compromising their health or the product's integrity.

Go deeper

Related to this question