The SCRUM Process | SCRUM Framework

This article gives a very quick executive summary of the Scrum process / framework.

It should be noted that referring to the Scrum Process above is somewhat of a misnomer. This is because Scrum is a framework, not a process. What this means is that rather than providing a detailed process, many of the decisions within the Scrum Framework are left up to the team to decide.

So without further ado, let’s get stuck in. Here is a diagrammatic summary of the Scrum framework:

scrum framework diagram

Scrum Framework Explained

The diagram above can be described as follows:

  • The Product Owner builds the product backlog and they prioritise it.
  • The team then looks at this backlog and they pull work from it. It’s a pull system just like Toyota’s Lean Manufacturing operation. If you have managers getting involved at this stage (pushing) then it slows things down. This is why the team decides how much stuff they can take into the scrum and what they can deliver in a cycle (the sprint backlog).
  • A Sprint cycle is no more than 4 weeks. Usually a Sprint will last between 2-4 weeks.
  • Inside the cycle the team must have a daily meeting. This is used to synchronise everyone within the team.
  • At the end of the cycle the team have to produce working software, and potentially shippable working software.

There you have it. A very basic introduction to the Scrum framework. Below you’ll find some definitions to further clarify the basic components of Scrum.

SCRUM Defined: Documents / Ceremonies / Roles

1. Documents

Product Backlog: This is a document containing high-level descriptions of all features to be developed in business priority order. This document is owned by the Product Owner. Typically, each item on the list will contain a rough estimate of both business value and development effort.
Sprint backlog: This is simply the list of things (again in priority order) that the team thinks they can do in the current Sprint. This is chosen by the team (pull) not by managers (push).
Burndown Chart: These simply show the amount of work remaining – they show in an instant wheather we are on or off target. They can work either at a Sprint level or a Release level. An example Burndown Chart is shown below:

 

2. Ceremonies

Sprint Planning: This happens on day 1 of the Sprint and is where the team members create the Sprint Backlog.
Daily Scrum Meeting: These are used to synchronize the work of the team. The meeting should last no more than 15 minutes. Each team member discusses what they worked on yesterday, what they’re working on today, and any blockers they’re facing.
Sprint Retrospective: (aka Sprint Review) This occurs at the end of the Sprint and gives the entire team the opportunity to examine the Sprint just completed and identify improvement opportunities for the next Sprint.

3. Roles

Product Owner: Owns the Product Backlog. Essentially the Product Owner directs the team to ensure they are working on the right requirements.
Scrum Master: This role does not direct the team like a Project Manager and allocate tasks, instead they shield the team from outside distractions and remove blockers to enable the team to work as quickly as possible.

Conclusion

I hope this article has given you a good basic understanding of the Scrum Framework, and that you understand why it’s a framework and not a process. Additionally, you will understand that the team is self-organizing, in that the team as a whole determines its own destiny, one Sprint at a time.