Blog‎ > ‎1. Scrum‎ > ‎

6.Scrum Events


Scrum Events

Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the 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.

Sprint planning meeting

At the beginning of the sprint cycle (every 7–30 days), a “Sprint planning meeting” is held.

  • Select what work is to be done
  • Prepare the Sprint Backlog that details the time it will take to do that work, with the entire team
  • Identify and communicate how much of the work is likely to be done during the current sprint
  • Eight-hour time limit
  • (1st four hours) Entire team: dialog for prioritizing the Product Backlog
  • (2nd four hours) Development Team: hashing out a plan for the Sprint, resulting in the Sprint Backlog

Daily Scrum meeting

A Daily Scrum meeting in the computing room. This choice of location lets the team start on time.

Each day during the sprint, a project team communication meeting occurs. This is called a Daily Scrum (meeting) and has specific guidelines:

  • All members of the development team come prepared with the updates for the meeting.
  • The meeting starts precisely on time even if some development team members are missing.
  • The meeting should happen at the same location and same time every day.
  • The meeting length is set Timeboxed to 15 minutes.
  • All are welcome, but normally only the core roles speak.

During the meeting, each team member answers three questions:

  • What have you done since yesterday?
  • What are you planning to do today?
  • Any impediments/stumbling blocks? Any impediment/stumbling block identified in this meeting is documented by the Scrum Master and worked towards resolution outside of this meeting. No detailed discussions shall happen in this meeting.
  • The advantages of the Daily Standup meetings are
G  : It Gets the team together
I    : Information is Shared
F   : Helps the team to focus 
T   : It Builds the team

Best Practices in a Scrum Standup meeting

  • The daily standup should be 15 minutes or less
  • Everyone should Stand during the meeting (so that the meeting is short!)
  • Even if the participants are remotely located, they should stand
  • No side conversations till the meeting is over

Sprint Review Meeting

At the end of a sprint cycle, two meetings are held: the “Sprint Review Meeting” and the “Sprint Retrospective”. This section describes the Sprint Review Meeting and next section describes the Sprint Retrospectives. One must understand that the objectives of both meetings are very different.

At the Sprint Review Meeting:

  • Attended by Product Owner, Scrum Master, team and other stakeholders as required
  • The objective of this meeting is
  • To review the work that was completed
  • The planned work that was not completed
  • If the team is on track
  • Get Feedback
  • Present the completed work to the stakeholders (“the demo”)
  • Incomplete work cannot be demonstrated
  • Four-hour time limit
  • Feedback from participants are reviewed and recorded. The product owner should consider the feedback as potential backlog items
  • Best Practices at the end of Sprint review
  • Items which were not completed are added back to the Sprint backlog
  • The newly added items are prioritized again before the new Sprint
  • Product Owner should assess the priorities of feedback and add to backlog if necessary
  • If the customer wants to feel the product, the Product owner should consider making a partial release (Alpha or Beta release) so that the customer can play around with the product.
  • It is a good practice to record the demo and make it available to the participants who could not attend the review

Sprint Retrospective

The Retrospective is the event in Scrum which brings in the iterative nature into picture. The team reflects upon the previous timebox with a view to learn some lessons, adjust the behavior or environment in order to improve their experience.

Backlog Grooming Meeting

Backlog refinement is the ongoing process of reviewing product backlog items and checking that they are appropriately prioritised and prepared in a way that makes them clear and executable for teams once they enter sprints via the sprint planning activity. Product backlog items may be broken into multiple smaller ones, acceptance criteria may be clarified, or new preparatory work such as clarification on client needs or technical spikes may be identified.

Backlog refinement is not a core Scrum practice but has been adopted as a way of managing the quality of backlog items entering a sprint.

Sample Scrum Agile Video by Amit Kulkarni

Sample Training Video by Sateesh Kamat

 

Amit Kulkarni conducting Planning Poker Estimation Exercise

 

EPMC - Project Foundational Concepts by Sateesh Kamat