Scrum Process

Overview

Scrum is an agile framework to manage a software development project. 

Why is it called Scrum?

When Jeff Sutherland created the scrum process in 1993, he borrowed the term "scrum" from an analogy put forth in a 1986 study by Takeuchi and Nonaka, published in the Harvard Business Review.  In that study, Takeuchi and Nonaka compare high-performing, cross-functional teams to the scrum formation used by Rugby teams. (In Rugby - scrum is an ordered formation of players, used to restart play, in which the forwards of a team form up with arms interlocked and heads down, and push forward against a similar group from the opposing side. The ball is thrown into the scrum and the players try to gain possession of it by kicking it backward toward their own side.)

The scrum process:

1. A product owner creates a prioritized wish list called a product backlog.
2. During sprint planning, the team pulls a small chunk from the top of that wish list, a sprint backlog, and decides how to implement those pieces.
3. The team has a certain amount of time – a sprint (usually two to four weeks) – to complete its work, but it meets each day to assess its progress (daily scrum / daily stand-up)
4. Along the way, the Scrum Master keeps the team focused on its goal.
5. At the end of the sprint, the work should be potentially shippable: ready to hand to a customer, put on a store shelf, or show to a stakeholder.
6. The sprint ends with a sprint review and sprint retrospective.
7. As the next sprint begins, the team chooses another chunk of the product backlog and begins working again.

Further Information

Source: https://www.scrumalliance.org/why-scrum