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.

• ✗

  Reduce the sprint length to two weeks to increase focus.

  Why it's wrong here

  Reducing the sprint length without first understanding the root causes of current project challenges is a superficial intervention. While shorter sprints can theoretically increase focus, they also increase overhead for planning and review, and can exacerbate existing issues like technical debt or unclear requirements by compressing the time available for quality work and problem-solving. This approach fails to address systemic inefficiencies and may lead to increased pressure without improved outcomes.

• ✗

  Add more developers to the team to increase velocity.

  Why it's wrong here

  Adding more developers to a struggling software development team is often counterproductive, a phenomenon known as Brooks' Law. New team members require significant onboarding, increase communication paths exponentially, and divert existing team members' time for training and integration. This typically leads to a temporary decrease in productivity and does not resolve underlying issues such as technical debt, unclear requirements, or process inefficiencies that are likely contributing to the project's difficulties.

• ✓

  Facilitate a retrospective to identify root causes and implement process improvements.

  Why this is correct

  Facilitating a retrospective is the most appropriate and effective agile practice for addressing project challenges like technical debt and unclear requirements. This dedicated event provides a structured forum for the entire team to collaboratively inspect their past sprint, identify root causes of impediments, discuss what went well and what could be improved, and commit to specific, actionable process improvements. This empowers the self-organizing team to find sustainable solutions and fosters continuous improvement.

• ✗

  Ask the scrum master to enforce stricter timeboxing for daily standups.

  Why it's wrong here

  Asking the Scrum Master to enforce stricter timeboxing for daily standups is an inadequate response to fundamental project issues like technical debt and unclear requirements. While effective time management in standups is beneficial, this action only addresses a potential symptom of inefficiency, not the underlying systemic problems. It does not resolve technical complexities, clarify ambiguous requirements, or improve the team's ability to deliver value, thereby failing to impact the core challenges.

Go deeper

Related to this question