2. Scrum Events

Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. Scrum uses time-boxed events, such that every event has a maximum duration. This ensures an appropriate amount of time is spent planning without allowing waste in the planning process. Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt. [23]

Scrum Events consist of the following: 

  • The Sprint:
    The heart of Scrum is Sprint, a time-box of one month or less during which a "Done", usable and potentially releasable product increment is developed. Sprint have consistent duration, a new Sprint starts immediately after the conclusion of the previous Sprint. 

    Sprints consist of the Sprint Planning Meeting, Daily Scrum, the development work, the Sprint Review and the Sprint Retrospective. 

    During the Sprint no changes are made that would affect the Sprint Goal. Quality goals do not decrease and and scope may be clarified. Sprints are limited to one calender month. 

  • Canceling The Sprint:
    A Sprint can be canceled before the Sprint time-box is over. Only the product owner has the authority to cancel the Sprint. A Sprint would be canceled if the Sprint goal becomes obsolete. Sprint cancellations consume resources as everyone has to regroup in another Sprint Planning Meeting to start another Sprint. It is worth mentioning that Sprint Cancellations are very uncommon. 

  • Sprint Planning Meeting:
    The work to be done in Sprint is planned during the Sprint Planning Meeting. The plan is developed by the work of the entire Scrum team. Sprint planning is time-boxed for eight hours for a one-month Sprint. Sprint Planning meeting consist of two parts. 

    Part 1: What will be done this Sprint?
    In this phase team works to forecast functionality that will be developed during the Sprint. 
        Part 2 : How will the chosen work get done?
        Once the work is selected, the team decides how it will            build the functionality into a "Done" product. 
  • Sprint Goal:
    As the development team works it keeps this goal in mind. In order to satisfy this goal, it implements the functionality and technology. 

  • Daily Scrum: 
    The daily scrum is a 15-minute time-boxed event for the team to synchronize activities for the next 24 hours. The Daily Scrum is held at the same time and place each day to reduce complexity. During the meeting, each Development Team member explains:
    • What has been accomplished since the last meeting?
    • What will be done before the next meeting?
    • What obstacles are in the way?
        The Daily Scrum improves communications, eliminates other meetings and highlights and promotes quick decision making.
  • Sprint Review: 
    A sprint review is held at the end of of the Sprint to inspect increment and adapt the product Backlog if needed. The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted to meet new opportunities. 

  • Sprint Retrospective: 
    The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. 

    By end of the Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint.