Scrum Events

Developed with


Scrum Master
The Sprint
The Daily Scrum

The course is part of this learning path

The Sprint

Module 4  The Scrum Events  

This module introduces the five different events that happen in Scrum: Sprint Planning, the Daily Scrum, The Sprint, the Sprint Review and the Sprint Retrospective. This module is made up of Videos, followed by a quiz to help support your understanding.   

  • Sprint Planning
  • The Daily Scrum  
  • The Sprint  
  • Sprint Review  
  • Sprint Retrospective  

- the athletic related names may seem to not make sense at first, the idea of working in sprint is to make a big task much more manageable. Instead of thinking about project as a big marathon, if you place project creation into smaller manageable sprints the project becomes much more doable. Lets find out more about the sprint. Past the athletic analogy its essential to think of the sprint as the heart of the scrum. It is set in a time-box of up to 1 month but some scrum teams work in smaller sprints. The team that created this learning course that your viewing works in 2 weeks sprints for example the purpose of the sprint is to release a usable and potentially a releasable product, it's not about releasing the whole product just a usable one. The product released is an increment, the work that goes into creating that increment happens in The Sprint. They have a consistent duration throughout development, that means The sprint team will always have the same length script. This can however be changed if the scrum team decides the is too long or too short for example. When a sprint ends a new sprint immediately begins. As mentioned the majority of the sprint is made up of a development team working during the sprint to release the product increment. However the other scrum events occur within a sprint we'll cover each of these in more depth in later videos but here's and overview, the first event is the print planning where everything that's going to be worked on is decided. The second, are the daily scrums, where the team updates the rest of the team in the progress, well, daily. Third, is the sprint review where the product increment are created are reviewed by the team, the product owner and the stake holders. Finally is the sprint retrospective or retro this is where the development team reflects on the previous sprint and team then makes adjustments for future sprints, each sprint has a goal, this is normally to reduce a product increment. As mentioned the core purpose of the sprint is to produce a product increment. The team works towards meeting the sprint goal set during the sprint planning which is normally to produce a particular increment. Changes can't be made that may put the sprint goal in danger. Any quality goals don't get decreased the scope of the sprint that is all of the work that makes up the sprint aiming to meet the sprint goal can be renegotiated with product order. This is mostly the case if the deaf team find out more about a particular task and that means it may take more or less work to get a task done. If you have a sprint that's longer then a month you can often lose sight of what's supposed to get done. Any task that's too long often faces procrastination or loss of motivation, and setting a goal that's too far away can often create that sort of environment. The sprint can essentially be considered a project with up to one month window. And remember, the purpose of the sprint is to get stuff done, don't get

About the Author
Paul Williams
Senior Learning Consultant
Learning Paths

Paul Williams is a Senior Learning Consultant for QA, based in Manchester, UK. He is a member of the Agile, Lean & DevOps Trainer Team.