If you Google Scrum methodology, you will get hundreds of results talking about it’s definition etc… However, when we talk about Scrum in the real world, it means we are actually interested in the execution of scrum.

Scrum consists of number of sprints that will take place for incremental delivery of potentially shippable product. Let’s have a look at how this sprint cycle works.

Sprint Planning

This is the first event/activity that takes place at the start of sprint. Product Owner, Scrum Master and the Team have a look at the requirements and create a stack of work called as Sprint backlog that they can complete within a sprint. Sprint Backlog is a set of tasks that team commits to complete and deliver by the end of the sprint.

Sprint backlog takes the shape of user stories and then user stories are further converted into tasks.

Daily Scrum

These tasks are then further being given to the team for implementation. Teams are self managed. They meet everyday for 15 minutes and talk about 3 items. What they did yesterday? What are they working on today? Any impediments or challenges they are facing? These meetings are time-boxed and are never extended. If further discussion is required, then follow up meetings are being scheduled.

It is the responsibility of Scrum Master to take care of these impediments team is facing and log them to project management tool. Report to the product owner and work on getting these resolved.

Ending the Sprint

Sprints always end on time. They are time-boxed. It’s the responsibility of the team to complete the work with the definition of “Done” within the sprint. Definition of Done is the agreed upon definition for completion of the work ¬†between product owner and the team. Generally it includes that the product will be fully developed and tested and is potentially shippable product increment.

Sprint Review

This is the event that takes place at the end of the sprint. Team gathers together along with Scrum Master and the Product Owner and inspect and adapt the product and the quality of the potentially shippable product increment. They meet and review together, Product Owner provides it’s feedback if any.

Sprint Retrospective

This is another event for looking after how the previous sprint was. Whole team inspect and adapt the process. They note down the changes they can make for making the upcoming sprints better.

And the Sprint cycles goes own with each sprint delivering the potentially shippable product increment thus resulting into Product Development and successful deliveries of the project.