After completing this unit, you'll be able to:
- Describe the characteristics of the Scrum framework.
- List the ceremonies and artifacts used in Scrum.
- Summarize the work of the three roles critical to Scrum success.
The Scrum Methodology
Scrum is one of the most popular frameworks for implementing agile. So popular, in fact, that many people think Scrum and agile are the same thing. (They're not.) Many frameworks can be used to implement agile, such as Kanban for example, but Scrum has a unique flavor because of its commitment to short iterations of work.
What’s So Special About Scrum?
With Scrum, the product is built in a series of fixed-length iterations called sprints that give teams a framework for shipping software on a regular cadence. Milestones—that is., the end of a sprint—come frequently, bringing with them a feeling of tangible progress with each cycle that focuses and energizes everyone. (“Continuous inspiration” for the win!) Short iterations also reinforce the importance of good estimation and fast feedback from tests—both recurring struggles in waterfall projects.
Scrum calls for four ceremonies that bring structure to each sprint:
- Sprint planning: A team planning meeting that determines what to complete in the coming sprint.
- Daily stand-up: Also known as a daily Scrum, a 15-minute mini-meeting for the software team to sync.
- Sprint demo: A sharing meeting where the team shows what they’ve shipped in that sprint.
- Sprint retrospective: A review of what did and didn’t go well with actions to make the next sprint better.
Learn more about these ceremonies in the Learn About Agile Ceremonies unit of the Agile Basics module.
During a sprint, visual artifacts (or tools) like task boards and burndown charts, visible to the team and spectators alike, are powerful motivators. They drive a spirit of “we're doing this!” Having the opportunity to show off new work at the sprint demo is equally motivating, and the consistent, incremental feedback the team gets from stakeholders at each demo creates a powerful way to develop products.
Check out this tutorial by Atlassian with step-by-step instructions to set up a Scrum project and run your first sprint with JIRA Software.
Scrum done well—which is to say, not “waterfall with stand-ups”–can be a massive catalyst for improving team productivity and morale, and the product development process as a whole.
Three Essential Roles for Scrum Success
A Scrum team has a slightly different composition than a traditional waterfall project, with three specific roles: product owner, Scrum master, and the development team. And because Scrum teams are cross-functional, “the development team” includes testers, designers, and ops engineers in addition to developers.
The Product Owner
Product owners are the champions for their product. They focus on understanding the business and market requirements and then prioritize the necessary engineering work accordingly.
Effective product owners:
- Build and manage the product backlog.
- Closely partner with the business executives and the development team to ensure everyone understands the work items in the product backlog.
- Give the development team clear guidance on which features to deliver next.
- Decide when to ship the product with the preference toward more frequent delivery.
Keep in mind that a product owner is not a project manager. Product owners are not managing the status of the project. They focus on ensuring the development team delivers the most value to the business. Also, it’s important that the product owner be an individual. No development team wants mixed guidance from multiple product owners.
The Scrum Master
Scrum masters are the champion for Scrum within their team. They coach the team, the product owner, and the business executives on the Scrum process and look for ways to fine-tune their practice of it. An effective Scrum master deeply understands the work being done by the team and can help the team optimize their delivery flow. As the facilitator-in-chief, they schedule the needed resources (both human and logistical) for sprint planning, stand-up, sprint review, and the sprint retrospective.
Scrum masters also look to resolve impediments and distractions for the development team, insulating them from external disruptions whenever possible.
Part of the Scrum master’s job is to defend against an anti-pattern (also known as a problem) common among teams new to Scrum: changing the sprint’s scope after it has already begun. Product owners sometimes ask, “Can't we get this one more super-important little thing into this sprint?” But keeping scope airtight reinforces good estimation and product planning—not to mention fends off a source of disruption to the development team.
Scrum masters are commonly mistaken for project managers, when in fact, project managers don’t really have a place in the Scrum methodology. A Scrum team controls its own destiny and self-organizes around their work. Agile teams use pull models where
the team pulls a certain amount of work off the backlog and commits to completing it that sprint. This is effective in maintaining quality and ensuring optimum performance of the team over the long-term. Neither Scrum masters nor product owners push
work to the team (which, by contrast, tends to erode both quality and morale).
The Scrum Development Team
Scrum teams are the champions for sustainable development practices. The most effective Scrum teams are tight-knit, co-located, and usually five to seven members. Team members have differing skill sets, and they cross-train each other so no one person becomes a bottleneck in the delivery of work. Strong Scrum teams approach their project with a clear “we” attitude. All members of the team help one another to ensure a successful sprint completion.
As mentioned above, the Scrum team drives the plan for each sprint. They forecast how much work they believe they can complete over the iteration using their historical velocity as a guide. Keeping the iteration length fixed gives the development team important feedback on their estimation and delivery process, which in turn makes their forecasts increasingly accurate over time.
This is only a brief introduction to Scrum, but check out the resources for a more in-depth look at this framework. Next we introduce another popular agile framework: Kanban.