Sprint planning is typically an industrious, productive process. Teams refine the backlog, set a target velocity, select user stories for the upcoming sprint, estimate effort and define tasks. Done correctly, teams leave planning with clear sprint goals and a clean sprint plan. Feels good, right?
Despite all this planning, developers often leave planning without tasks assigned to them – and that can be a good thing.
For newer scrum teams, assigning tasks during sprint planning acts as something of a safety net – it’s reassuring to know who’s responsible for which items, and assigning every task can help ease worries that stories will get left behind. While this approach increases individual accountability, it sacrifices team accountability. After all, the team committed to certain stories together; they should share the responsibility for claiming and completing the tasks throughout the sprint...
For newer scrum teams, assigning tasks during sprint planning acts as something of a safety net – it’s reassuring to know who’s responsible for which items, and assigning every task can help ease worries that stories will get left behind. While this approach increases individual accountability, it sacrifices team accountability. After all, the team committed to certain stories together; they should share the responsibility for claiming and completing the tasks throughout the sprint...
RSS Feed