Project Management Guide
FAQ
← Back to FAQ

What Is Scrum in Agile?

Scrum is a framework of rules, roles, events, and artifacts used to implement Agile projects. It is an iterative approach, consisting of sprints that typically only last one to four weeks. This approach ensures that your team delivers a version of the product regularly. 

Scrum was designed using a software model that follows a set of roles, responsibilities, and meetings. It can be used for any complex project but works best when the result is a concrete product rather than a service.

Scrum in Agile requires particular roles and responsibilities, including the following:

  • Product owner: The product owner is responsible for representing the customer’s best interest. This person has the ultimate authority over the final product.
  • Scrum master: This person is a facilitator, responsible for arranging the daily meetings, improving team interactions, and maximizing productivity. The project manager often takes on the role of Scrum master, but they can delegate it to anyone on the team who is a Scrum expert and strong facilitator. 
  • Backlog: The backlog is a list of tasks and requirements included in the final product. It’s the responsibility of the product owner to create the backlog. 
  • Sprint: A sprint is a set time frame for completing each set of tasks from the backlog. Every sprint should be the same length. Two weeks is typical, but a sprint can be anywhere between one to four weeks long, depending on the team and project’s needs.  
  • Daily meetings: A Scrum project team is expected to meet every day to discuss progress. These meetings are typically referred to as a Daily Scrum or Daily Stand-Up.
  • Retrospective: Each sprint should end with a review meeting, called a retrospective. Here, the team reviews their progress and discusses how they can improve in the next sprint.
Further Reading
blog post

Fundamentals of the Scrum Methodology

article

The Scrum Guide

blog post

Scrum for Newbies: How to Use Scrum to Tame Chaos