A Scrum Team has been consistently meeting its Sprint Goals, but the Scrum Master observes that the Developers are primarily focused on completing their individual tasks, and there's minimal collaboration or knowledge sharing, even when team members are struggling. What aspect of a healthy Scrum Team is MOST lacking, and how should the Scrum Master address it?
- ALack of technical expertise; the Scrum Master should recommend external training for specialized skills.
- BLack of clear individual accountability; the Scrum Master should implement a peer review system for tasks.
- CLack of cross-functionality; the Scrum Master should coach the team on the benefits of T-shaped skills and collective code ownership.
- DLack of a strong Product Owner; the Scrum Master should advise the Product Owner to assign tasks more explicitly.
Show answer & explanationAnswer & explanation
Correct answer: C. Lack of cross-functionality; the Scrum Master should coach the team on the benefits of T-shaped skills and collective code ownership.
The problem describes a lack of collaboration and knowledge sharing, even when the Sprint Goal is met, indicating a deficiency in cross-functionality and collective responsibility. Coaching on T-shaped skills and collective code ownership directly addresses this by encouraging broader skill sets and shared accountability for the entire Increment, fostering a more cohesive and adaptable team.
Why the other options are wrong
- A. While technical expertise is important, the core problem is not a *lack* of skills but a lack of *sharing* and *applying* those skills collaboratively across the team. Training is a reactive measure for skill gaps, not collaborative gaps.
- B. Individual accountability is important, but the issue is a lack of *team* accountability and collaboration. A peer review system might address quality but not necessarily foster proactive knowledge sharing and support.
- D. The Product Owner assigns items to the Product Backlog, not tasks to individuals. This would undermine the Developers' self-management and is not the PO's role.
Cross-functional Team
A Scrum Team is cross-functional, meaning the Developers have all the skills necessary to create value each Sprint without depending on others outside the team.
- Possesses all skills needed to turn Product Backlog Items into an Increment.
- Promotes collaboration and knowledge sharing within the team.
- Reduces external dependencies and bottlenecks.
Memory trick: Cross-functional, self-managing, always improving.