Agile Ceremonies

Agile ceremonies #

Daily Stand-up (Daily Scrum) #

Purpose: To align the team and identify any potential obstacles or dependencies.

Duration: 30 minutes per day.

Participants: Scrum Team (Developers, Product Owner, and Scrum Master/Project Manager).

How participants should be prepared for these meetings: Participants should be ready to answer three questions: What did I do yesterday? What will I do today? Are there any blockers impeding my progress?

Refinement Session #

Purpose: To review and update the product backlog, ensuring that upcoming work is well-defined and ready for inclusion in future sprints.

Duration: Typically 2-3 hours per week, depending on team size and backlog size.

Participants: Scrum Team (Developers, Product Owner, and Scrum Master/Project Manager).

How participants should be prepared for these meetings: Product Owner/Project manager should have the backlog prioritized. Participants should review backlog items before the meeting and come prepared to discuss, refine user stories and estimate the user stories or tasks.

Sprint Planning #

Purpose: To determine what can be delivered in the upcoming sprint and how that work will be achieved.

Duration: Typically 2 hours for a two-week sprint.

Participants: Scrum Team (Developers, Product Owner, and Scrum Master/Project Manager).

How participants should be prepared for these meetings: Participants should review the product backlog items estimated during Refinement. Product Owner/Project manager should have the backlog prioritized. During the session, they should clarify requirements if left unresolved during Refinement, estimate effort and commit upcoming sprint backlog.

Sprint Review & Demo #

Purpose: To demonstrate the work completed during the sprint and gather feedback.

Duration: Typically 2 hours for a two-week sprint.

Participants: Scrum Team (Developers, Product Owner, and Scrum Master/Project Manager), stakeholders, and anyone else interested in the product.

How participants should be prepared for these meetings: Participants should ensure that the increment is ready for demonstration and gather feedback. Product Owner/Project manager should have the product backlog ready for reprioritization based on feedback.

Sprint Retrospective #

Purpose: To reflect on the past sprint and identify opportunities for improvement.

Duration: Typically 1.5 to 2 hours for a two-week sprint.

Participants: Scrum Team (Developers, Product Owner, and Scrum Master/Project Manager).

How participants should be prepared for these meetings: Participants should reflect on what went well, what didn’t go well, and what actions can be taken to improve in the next sprint.