Scrum: Process & Examples

An error occurred trying to load this video.

Try refreshing the page, or contact customer support.

Coming up next: Scrum: Rules & Best Practices

You're on a roll. Keep up the good work!

Take Quiz Watch Next Lesson
Your next lesson will play in 10 seconds
  • 0:03 What Is Scrum?
  • 1:08 Scrum Team Roles
  • 2:28 Sprint Planning &…
  • 3:55 Refinement or Grooming
  • 4:25 Sprint Review & Retrospective
  • 4:56 Lesson Summary
Save Save Save

Want to watch this again later?

Log in or sign up to add this lesson to a Custom Course.

Log in or Sign up

Speed Speed
Lesson Transcript
Instructor: CaSandra Minichiello

CaSandra has a bachelor's degree in Computer Information Systems and has taught Agile along with Scrum and Kanban for over 10 years.

Scrum: It sounds like a silly word, but it's an effective, popular software development framework. This lesson explains the scrum process and provides examples.

What Is Scrum?

While searching for project management jobs, Laurie stumbled upon a job opportunity for a scrum master. Unfamiliar with scrum, she calls her friend Robert, a software developer who is part of a scrum team, for some guidance.

Robert explains that scrum is a framework that guides small teams to break complex products into small, functional pieces of work that can be coded and delivered in small increments of time known as iterations or sprints. The benefit is that working software is delivered to customers quickly.

Scrum is a term borrowed from the sport rugby and is short for scrummage, which is a way of starting play again. The goal of rugby is to play continuously without any time-outs or other interference.

As in rugby, in scrum, a delivery team must deliver working, quality software by the end of the sprint. A sprint is usually two weeks in length, but can be shorter or longer. The delivery team continues to work in sprints until the end of the product or project. Team members work together, without any outside interruptions, while the sprint is in process.

Scrum Team Roles

The scrum team incorporates three roles:

  1. Delivery team
  2. Scrum master
  3. Product owner

Let's look at each in further detail, starting with the delivery team.

The Delivery Team

The delivery team is accountable for choosing which work it will deliver at the end of the sprint. Team members are self-organizing and empowered to make all decisions on how they'll complete their work. They're also fully dedicated to the product.

Laurie's friend Robert is part of a delivery team, sometimes referred to as a development team. The team size is kept small, usually only five to seven people, so that collaboration and communication is easier. Robert's team has four developers, two testers, and one designer, but their skills are fairly balanced or cross-functional.

Scrum Master

The scrum master is the servant-leader to the delivery team. His or her main responsibility is to remove any roadblocks that are preventing the team from completing work and to protect the team from all outside interference. The scrum master also teaches others, including the product owner and other organization employees, about scrum and ensures that everyone adheres to its principles.

Product Owner

Finally, the product owner is responsible for creating and prioritizing the work listed in the product backlog, which is a list of work that needs to be completed. This person serves as the one voice for the product and works closely with the development team on a daily basis.

The Five Ceremonies

Robert seems fairly excited to explain how scrum teams engage in five standard ceremonies or events, traditionally known as meetings.

These include:

  1. Sprint planning
  2. Daily stand-up
  3. Refinement or grooming
  4. Sprint review
  5. Retrospective

Again, let's look at each in further detail.

Sprint Planning & Daily Stand-Up

The scrum team attends sprint planning, which happens on the first day of the sprint. The purpose of this ceremony is to choose which high-priority product backlog items will be developed in the sprint.

The product owner then describes the top-priority product backlog item, and the delivery team discusses and plans out what needs to be completed in order to consider the product backlog item completed. The product owner then describes the next item and the team continues to discuss and commit until they are no longer able to commit to any more work in their sprint.

To unlock this lesson you must be a Member.
Create your account

Register to view this lesson

Are you a student or a teacher?

Unlock Your Education

See for yourself why 30 million people use

Become a member and start learning now.
Become a Member  Back
What teachers are saying about
Try it risk-free for 30 days

Earning College Credit

Did you know… We have over 200 college courses that prepare you to earn credit by exam that is accepted by over 1,500 colleges and universities. You can test out of the first two years of college and save thousands off your degree. Anyone can earn credit-by-exam regardless of age or education level.

To learn more, visit our Earning Credit Page

Transferring credit to the school of your choice

Not sure what college you want to attend yet? has thousands of articles about every imaginable degree, area of study and career path that can help you find the school that's right for you.

Create an account to start this course today
Try it risk-free for 30 days!
Create an account