Scrum Process : The Scrum Process Flow

Before I dive into the details, I want to give you a high level overview of a typical scrum process.

So that you will better understand the roles, the events and the artifacts that  I will be showing you in the next sections of the course

The process flow, It’s all on one slide and here it is…

Product Backlog

The process starts when the product owner creates the product backlog, that is

A list of all the features and functions and requirements that might be needed in the final product of the project.

It’s a prioritized list. The items with the highest business value have high priority.

Low value, add-on functionality has low priority.

Scrum Process: Sprint Backlog

The scrum team get together in a sprint planning meeting and decide what items in the product backlog they can work on and complete during the next time period.

This list of items is called the sprint backlog.

The development team immediately set to work completing the items in the sprint backlog in a set time frame called a sprint.

Scrum Process: Daily Scrum

Every day during the sprint the development team and the scrum master meet in a short 15 minute stand up meeting, called the daily scrum, discussing their individual progress, synchronizing their activities, identifying any issues that will stop them from working; and planning for the work to be completed in the next 24 hours

Scrum Process: Sprint Review

Towards the end of the sprint, the development team demonstrate to the product owner and other stakeholders, the output of the work they’ve done during the current sprint and all previous sprints. Demonstrating the latest increment of the product.

And this latest increment is a potentially shippable product.

Product Backlog Grooming

And all the while the product owner supported by the scrum master reviews the latest product increment and the potential business value and refine the product backlog in preparation for the next iteration or sprint.

And the process begins again

Now Looking at the process in another way, in the form of a bar chart for you traditionalists out there

And again only one slide…

Product Backlog

It starts with the product backlog

And the scrum team decide what Product Backlog Items can be delivered in the next time-boxed sprint

Scrum Process: Sprint Backlog

This list of Product Backlog Items is frozen in a sprint backlog

Scrum Process: Daily Scrum

The sprint begins and the development team meet every day at the same time, same place to plan for the next 24 hours

Scrum Process: Sprint Review

At the end of the sprint the development team demonstrate to the product owner and other stakeholders what they’ve done so far. That is In this current sprint plus all previous sprints. This is called an increment and is a potentially shippable product

Sprint Retrospective

After the sprint review the scrum team get together and discuss what went well and what didn’t go so well in the last few weeks and make plans to include process improvements in the next sprint

Product Backlog Refinement

And while all the work is in progress, the product owner is reviewing, adding to, subtracting from and fine tuning the remainder of the product backlog

This product backlog grooming is kind of stopped while the planning meeting for the next sprint takes place

And the cycle continues.

Iterative, Incremental with a Little Empiricism

So there you have it a typical scrum process that’s iterative, cyclical and another word that’s coming soon “empirical”