Scrum Events/Ceremony in agile.

In today’s fast-paced and unpredictable business environment, traditional product development approaches that involve planning out every detail of a product from the beginning are no longer practical. Instead, it is important to embrace a more adaptive and flexible approach that can quickly respond to changes in order to achieve success.

The Scrum framework includes several elements, including the Scrum artifacts, roles, goals, and events which are all customer-centric in their approach. Scrum is implemented by a Scrum team which consists of a Scrum Master, a Product Owner, and Developers. Each member of the team works closely together to achieve the set goals and adhere to the Scrum methodology to stay agile and adaptable throughout the process.

There are three Scrum artifacts such as product backlog, sprint backlog, and increment, while the three Scrum goals are the product goal, sprint goal, and the definition of done.

Scrum is structured but not rigid in its application. Its application & execution can be customized to the needs of any organization. Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.

• Scrum is simple

• Scrum is based in Empirical Process Control Theory, Lean Thinking and Agile Philosophy

• Scrum is purposefully incomplete. Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions.

• Scrum employs an iterative, incremental approach to optimize predictability and to control risk.

Scrum Events/Ceremony:

Each event in Scrum is a formal opportunity to inspect and adapt something.

These events are specifically designed to enable critical transparency, inspection

and adaptation.

Sprint

• Sprints are the heartbeat of Scrum, where ideas are turned into value

• All the necessary work to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints

• A new Sprint starts immediately after the conclusion of the previous Sprint No

• No changes allowed once the scope of sprint is decided

• Length of sprint is decided. it is between 1-4 weeks.

• Scope of sprint can be clarified or negotiated between product owner and developers.

  
  

Sprint Planning

Similar to the Sprint, the Sprint Planning ceremony is also a timeboxed event. The Sprint Planning ceremony is where the Scrum Team comes together to understand the prioritized Product Backlog items and how they map to the Product Goals. This is usually delivered by the Product Owner who should also be emphasizing the value add of the current Sprint. Once the current Sprint’s “why” is defined, the team will focus to “what” work can be done and “how” the work will be done.

There are many factors that are at play when determining what work will get done, such as:

The team’s definition of ‘done’

Their capacity

Their past velocity to deliver each sprint

This helps define how the work gets done, with the developers often decomposing the Backlog Items into small workable tasks.

Daily Scrum

• The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as

necessary, adjusting the upcoming planned work.

• The Daily Scrum is a 15-minute event (regardless of the length of the

sprint) for the Developers of the Scrum Team.

• To reduce complexity, it is held at the same time and place every working day of the Sprint.

• If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.

The team can choose the structure of the meeting, but usually most stick to answering three questions:

1. What did I work on yesterday

2. What am I working on today

3. Are there any blockers/impediments with my work?

   
   

If a developer is facing any blockers/impediments, the Scrum Master will coordinate with the developers and help them to clear these items.

The Sprint Review

On the last day of the sprint, the Sprint Review and Retrospective ceremonies need to occur. The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next.

Sprint Retrospective

Lastly, the Sprint Retrospective is the final timeboxed ceremony in the sprint. The development team participates in the sprint retrospective and the scrum master facilitates the meeting. The idea is to transparently assess performance, identify areas for improvement, and create actionable plans for the upcoming sprint. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved. The entire sprint retrospective is time-boxed to a max of three hours, but it can be less depending on the length of the sprint.

Product backlog refinement

During this meeting, the product owner and some (or all) of the team members review the backlog items together. The purpose of this scrum ceremony is to clean and prioritize the backlog.

Scrum events/ ceremonies summary table