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

New way of product development

Today is the era of fast-paced world and competitive world. Companies are realizing that the old sequential approach to developing new products won’t get the job done and product can’t be reached to market when compared to competitors. The 4 stages of product development are as follows – R&D, Growth, Maturation, and Decline. Instead of sequential approach, companies are using holistic approach – as in rugby game, the ball gets passed within the team as it moves as a unit up the field. This holistic approach has six characteristics: 1)     Build-in-instability 2)   Self-organizing project teams 3)   Overlapping development phases 4)   Multi-learning 5)   Subtle (very clear and strong) control 6)   Organizational change to explore and learning The above six characteristics forming a fast and flexible process for new product development with advantage of act as a change agent, creative, market driven ideas, flexi...
Post a Comment
Read more

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.      Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: ...
Post a Comment
Read more

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more