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.

• ✗

  Enforce a strict 15-minute timebox for future standups

  Why it's wrong here

  Enforcing a strict 15-minute timebox fails to address the root complaint about unproductive content; the team needs facilitation to improve discussion quality, not merely a clock. This option is tempting because timeboxing is a standard Scrum tool for preventing standup drift, and it would be correct if the sole issue were duration rather than perceived value.

• ✗

  Cancel the daily standups and replace them with written status reports

  Why it's wrong here

  Canceling the Daily Scrum fundamentally undermines agile principles of frequent, face-to-face communication and rapid inspection and adaptation. Written status reports lack the immediacy and interactive dialogue necessary for teams to quickly identify impediments, coordinate daily work, and foster collective ownership of the sprint goal. This approach replaces proactive problem-solving with passive information dissemination, hindering real-time collaboration and the team's ability to self-organize effectively.

• ✗

  Move the standup to a later time when team members are more focused

  Why it's wrong here

  Simply moving the Daily Scrum to a different time is a superficial solution that fails to address the underlying complaint about unproductive content or format. If team members perceive the meeting as unfocused or lacking value, the issue likely stems from a lack of clear purpose, ineffective facilitation, or a failure to adhere to its core structure, rather than just timing. A time change might introduce new logistical challenges for some members without improving engagement or the meeting's perceived value.

• ✓

  Ask the team to propose improvements to the standup format and agree on changes

  Why this is correct

  This is the most appropriate agile response, as it empowers the self-organizing team to collaboratively inspect their process and adapt it for continuous improvement. The Sprint Retrospective is precisely the forum for discussing such complaints and collectively devising solutions, fostering a sense of ownership and commitment to the agreed-upon changes. This approach leverages the team's collective intelligence to enhance their working agreements and ensure the Daily Scrum serves its intended purpose effectively.

Go deeper

Related to this question