Summary
Highlights
Scrum involves three distinct roles: Scrum Master, Product Owner, and Development Team. The Scrum Master supports both the development team and product owner, maximizing ROI and empowering the development team through creativity, impediment removal, and coaching. The Product Owner defines vision, requirements, and priorities, making tough choices during sprint planning. The Development Team, typically 5-9 members, self-organizes to meet the Product Owner's goals.
A Scrum Master is a skilled servant leader with little formal authority. They assist teams in achieving outcomes without interfering with autonomy, facilitate Scrum ceremonies (sprint planning, daily stand-ups, reviews, retrospectives), remove obstacles, and serve as a process coach and mentor. Crucially, a Scrum Master shouldn't be a line manager, task master, technical authority, or decision-maker, ensuring team empowerment is preserved.
Effective Scrum Masters are responsible, prioritizing team productivity and removing impediments. They are humble, working in the background and letting the team take credit, often using 'we' statements. They are collaborative, encouraging communication within the team and with stakeholders, and committed to the team's needs. They are influential and skilled communicators, mobilizing resources and navigating organizational politics. Finally, they are knowledgeable in Scrum methods, able to have productive conversations about project work.
Scrum Masters are servant leaders who prioritize their team's needs. They set up and ensure effective Scrum ceremonies, facilitate information flow and collaboration, and resolve issues hindering progress by mobilizing resources promptly. They protect the team from disturbances and unreasonable expectations, acting as peacemakers in conflicts. They also coach the team on Scrum principles, ensuring adherence to agile development.
Scrum teams should be small and nimble (3-9 members, ideally 6±3) to improve productivity and avoid social loafing, ensuring significant work increments each sprint. They must be self-sufficient and cross-functional, possessing all necessary skills (e.g., UI, database, services). Team members should be generalizing specialists, having expertise in one area but also skills to contribute to others. Scrum favors feature teams over component teams and promotes autonomy and self-organization.
When assembling teams, prioritize feature teams over component teams to encourage collaboration. Ensure the right mix of technical and domain expertise, including senior and junior developers, and foster diversity to bring broader perspectives. Teams may take time to develop trust (storming stage), but once formed, they should be preserved and assigned as whole units to projects, avoiding multi-project assignments for individuals. For distributed teams, co-locate members where possible and establish clear rules to overcome communication challenges. Team productivity often follows an S-curve, with the sweet spot being around 6 +/- 3 members.