Sprint Backlog Updates

Correct Answer: Log the impediment in the Sprint Backlog to enhance visibility, ensure it's tackled promptly, and communicate any potential effect on the Sprint Goal to the Product Owner.

The Sprint Backlog is intended to be a dynamic artifact that evolves throughout the Sprint based on the team’s understanding of the work needed to achieve the Sprint Goal. Adding impediments to the Sprint Backlog increases transparency and ensures that they are addressed promptly. It is incorrect to wait until the Daily Scrum to address impediments, track them outside the Sprint Backlog, or halt work without the team's assessment and adaptation. The Scrum Team should collaboratively work on impediments, with the Scrum Master facilitating the removal of impediments and the Product Owner informed about any impacts on the Sprint Goal.

Correct Answer: The development team communicates with the Product Owner about the issue, discusses potential solutions, and makes necessary modifications to the sprint backlog.

The best resolution when the development team realizes they are not able to finish a task within the set time in the middle of a sprint is to communicate with the Product Owner about the issue, discuss potential solutions, and make necessary modifications to the sprint backlog. This answer is the most suitable because it aligns with Scrum principles of transparency, inspection and adaptation. Scrum encourages teams to identify problems or issues, then adapt their plans accordingly, so this answer aligns well with Scrum principles. The other answers are not appropriate solutions: Working overtime to finish the task disrupts sustainable development and can lead to burn-outs. Suspending the task and proceeding to the next one disrupts the sprint goal and ignores the problem rather than solving it, and ignoring the issue contradicts the Scrum values of openness, courage and focus. Hence, these options do not reflect the best practices in Scrum framework.

Correct Answer: Explain to the stakeholder that while their input is valuable, the sprint backlog is fixed for the duration of the sprint to maintain focus and stability. However, their request will be reviewed and possibly included in the product backlog for consideration in future sprints.

The practice of adding features to the current sprint without team consensus disrupts the sprint goal and undermines the Scrum framework's principles. The correct approach involves respecting the sanctity of the sprint backlog once the sprint has commenced while ensuring stakeholder requests are considered for future sprints, maintaining both the stability of the current sprint's objectives and the flexibility to adapt to changing product needs.