What are the different ceremonies in Agile?

 

  1. Sprint planning: These sessions are what initiate each sprint. Your team decides what work from the product backlog can be completed in the time period, who will complete what tasks, and how you’ll be successful.
  2. Daily scrum (or daily stand-up): These daily check-ups help teams stay on track and mark progress. Each morning, team members discuss what they worked on yesterday, what they’re doing today, and what’s blocking them from moving forward.
  3. Sprint review: At the end of each sprint cycle, teams meet to demo what they’ve shipped and get early feedback from stakeholders. These review sessions can be informal ‘show and tell’ sessions or more formal meetings.
  4. Sprint retrospective: At the end of each sprint cycle, the team also meets to discuss what’s working (or not) on a process level, including blockers, communication issues, or a lack of resources.
  5. Product backlog refinement: While not always listed as an ‘official’ ceremony, product backlog refinement is a continuous process of cleaning up, adjusting, and updating your task and feature list. Some teams set specific times to go through and clean up the backlog, while others do it continuously throughout each sprint.

Comments

Post a Comment

Popular posts from this blog

How to log a defect/bug with a detailed description etc?

  Effectively reporting a bug is essential for the development team to resolve the issue promptly and accurately. A well-constructed bug report should be concise, comprehensive, and comprehensible.  The following steps can be taken to submit a bug report: Attempt to replicate the bug consistently and systematically. Gather data on the environment, such as the browser type, operating system, and applicable software versions. Construct explicit instructions outlining how to reproduce the bug. Include screenshots or videos that may assist in illustrating the issue to developers. Articulate what outcome was anticipated and differentiate it from what occurred in reality. Outline the severity and priority of the bug: Describe how the bug impacts the software’s functionality and determine its level of urgency. Check for duplicates: Investigate the bug tracking system to ascertain if it has already been reported. Assign the bug to a relevant developer or team and follow up Monitor pro...
Read more