Skip to main content

Scrum Ceremonies

 Scrum defines several events (sometimes called ceremonies) that occur inside and outside each sprint:


1) Product Backlog Grooming:

Backlog grooming is the only ceremony in scrum that doesn’t have a defined time box or even a frequency. 

It is, however, a critical responsibility of the product owner with the help of their team to add new items to the list and order them based on their priority. 

At the same time, outdated, redundant or non-valuable items should be removed from the backlog to keep it clean, valuable and actionable. 

We call this as Release plan meeting happens quarterly once.

Action taken from grooming meeting:

    1) Estimate user stories

    2) Insert new user stories

    3) Re-Prioritize user stories

    4) Refine user stories

    5) Remove user stories

2)  Sprint Planning:

A sprint planning meeting is when the team (including the Scrum Master, Scrum Product Manager, and Scrum Team) meets to determine which backlog items will be handled in the next sprint.

The sprint planning Scrum ceremony is a collaborative process that allows team members to have a say in when work happens.

3) Daily Scrum:

During this meeting, each team member should briefly provide the answers of the following three questions:

    1) What has he/she accomplished since the last daily Scrum meeting?

    2) What is he/she is going to accomplish until the next Scrum meeting?

    3) What are the impediments that prevent him/her from accomplishing his/her tasks?

4) Sprint Review:

Sprint reviews focus on the product being developed, specifically on the potentially shippable product increment created during the sprint.

During a sprint review, the scrum team invites stakeholders to discuss what was completed during the sprint. 

They adapt the product backlog as needed based on this feedback. The product owner has the option to release any of the completed functionality. 

Though a demo might be part of this meeting, the primary purpose of the sprint review is the inspect and adapt capability provided by the discussion. 

5) Sprint Retrospective:

The sprint retrospective is a recurring meeting held at the end of a sprint used to discuss 

1) what went well during the previous sprint cycle?

2) what went wrong during the previous sprint cycle? 

3) what can be improved for the next sprint?

The Agile sprint retrospective is an essential part of the Scrum framework for developing, delivering, and managing complex projects.

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Empiricism (Scrum)

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Pillars of  Empiricism . Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism . In complex environments, what will happen is unknown. Only what has already happened may be used for forward-looking decision making. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal. ● For the Sprint Backlog it is the Sprint Goal. ● For the Increment it is the Definition of Done. These commitments exist to reinforce empiricism . The sum of the Increments is presented at the Sprint Review thus supporting empiricism .
Post a Comment
Read more