The scrum process is a commonly used development process for agile projects. It was created by Jeff Sutherland in 1993 using an analogy from the sport of Rugby to represent a highly integrated, cross functional team.


scrum process


In the scrum approach a product owner creates a prioritised wish list called a product backlog. This may be prioritised using techniques such as MoSCoW and should be subject to the core principles of requirements management.

During sprint planning, the development team selects a batch of high priority products that it aims to complete during a sprint (timebox) of, typically, 2 to 4 weeks.

The team meets every day to assess progress and this meeting is facilitated by a ‘Scrum Master’. The scrum master’s role is to keep the team focused, track progress and remove obstacles that may affect the achievement of the sprint’s goals. Views on whether the role of scrum master can, or should, be fulfilled by the project manager are controversial.

Progress within a sprint may be monitored using a kanban approach. The progress of product development across multiple sprints may be visualised in a burn down chart.

At the end of the sprint, the chosen products should be ready to demonstrate to the product owner or actually be delivered. Any unfinished products are returned to the backlog.

A sprint should end with a review (much like a post project review but on a much smaller scale). The team then selects the next batch of products for the next sprint.

This process can be used in place of the generic development process in the Praxis method.

20th September 2014Created


Back to top