The Scrum process – in detail

When a Scrum project is started there is already a set of ideas for what you want to achieve – a vision is formulated, a Product Owner has been appointed and he has gathered all ideas and wishes in a list that we call the Product Backlog. So let us begin:

The Product Owner has prepared a prioritized Product Backlog. Every Item has been given a Business Value and an estimate on how big this job is.

Product Owner and the Team will sit down together and assess how many of the topics from the top of the Backlog can be done in the next Sprint. For how long will the Sprint be running? How many Team members are there? Is anyone on vacation? etc. The Team commits itself to deliver the choosen Items. This is called Sprint Planning 1.

The next thing to be done is that the Team breakis the Items down into duties. Every duty should be so small that it can be solved in one day. This is called Sprint Planning 2. The list we get from this is what we call the Sprint Backlog or the taskboard.

Then the Sprint is ready to start. The Team go to work to solve thir duties without any interference. Each day the Team has a Daily Scrum meeting. Each Team member answers these three question in turn:

  • What have I finished since yesterday?
  • What will I finish for tomorrow?
  • Are there anything that prevents me from working optimally? Are there any stones on my road?

Same time, same place every day – it only takes 10-15 minutes. This meeting is public but al lare welcome but only the Team and the Scrum Master speaks.

The Scrum Master notes if there are any kind of obsticals andhe also reposrts on the Daily Scrum meeting which obsticals he has removed since yesterday and what he will be working on today.

All Team members get back to work on the duties from the Sprint Backlog that they divide among themselves. The Scrum Master go to the rest of the organization (or the world) to take care of obsticales that are blocking for the Team.

When the Sprint is done the Team will present the finished Items on a meeting – this is what we call Sprint Review. The Product Owner is or course present and accepts deliveries the Items from the Backlog. The Team will only present finished Items which means that they must be tried and tested. All other stakeholders a more than welcome. All with interest in what is going on shuld be here. What you see here is what you can expect to get delivered.

Items and topics are diskussed others might have comments or gets new ideas, suggestions for improvement etc. All mental resources are pointing at one common goal here. New input is put into the Backlog.

Now it is time for the Team and the Scrum Master to have their own debriefing – how did this Sprint go?

  • Facts are on the table, a timeline shows what went down and when
  • What went well in this Sprint?
  • What can be improved? Who can do something about this? The Team (maybe it has to be put on the backlog) or the organization (then it is up to the Scrum Master if he can get it implemented).

The Team chooses a few thing – the most important to address. This meeting is called the “Retrospective“. Here everything comes full circle and we get our improvement process going.

The Product Owner has been busy adjusting the Backlog with the new input from the Sprint Review and maybe also from the Retrospective.

During the Sprint the Product Owner has been working with the next Items that is relevant. He has to put business value on them and not to mention he must put an estimate on the cost. The Team has been involved too they are after all the ones to solve the assignment and they can give the best estimates. It might be necessary a straight-out estimation meeting during the Sprint.

And now we’re ready to start the nect Sprint with a new Sprint Planning 1 meeting.