Ace the 2025 CSPO Challenge – Unleash Your Scrum Mastery!

When a Developer cannot complete their assigned work during a Sprint, the most appropriate action is to notify the team and reprioritize tasks. This approach aligns with the collaborative nature of Scrum, where the team is responsible for managing their workload and outcomes together.

By informing the team, the Developer enables a discussion that allows the group to assess the situation collectively. It's important for the entire team to understand the progress and any impediments faced by team members. Reprioritizing tasks, if necessary, helps the team focus on what can be realistically achieved within the Sprint, potentially allowing for adjustments to meet their Sprint Goal.

This process fosters openness and transparency, which are core principles of Scrum, and ensures that all team members are aligned on current priorities and workloads. It also encourages a culture of collaboration where members support each other to overcome challenges.

In contrast, simply asking for help from the Scrum Master does not fully engage the team in problem-solving. Making adjustments to the Product Backlog or finishing the work after the Sprint could undermine the time-boxed nature of Sprints, affect commitments, and compromise the integrity of the Scrum framework.