https://agilesoftdev.com/tags/agile-ceremonies/ Recent content in agile ceremonies on Agile Software Development Hugo -- gohugo.io en-us Sat, 02 May 2026 00:00:00 +0000 https://agilesoftdev.com/the-daily-standup-has-three-failure-modes-and-teams-hit-all-of-them/ Sat, 02 May 2026 00:00:00 +0000 https://agilesoftdev.com/the-daily-standup-has-three-failure-modes-and-teams-hit-all-of-them/ The daily standup is fifteen minutes. It is the shortest ceremony in the sprint cycle and the one with the highest ratio of complaints to duration. Most of the complaints are legitimate, and they cluster around three patterns that are distinct enough to be worth naming separately. The first is the status report disguised as a standup. Each team member addresses the scrum master or manager rather than the team, describes what they did yesterday and what they will do today, and waits for the next person to do the same. https://agilesoftdev.com/the-sprint-review-is-not-a-demo/ Sat, 02 May 2026 00:00:00 +0000 https://agilesoftdev.com/the-sprint-review-is-not-a-demo/ The sprint review is consistently misunderstood as a presentation event. The team demonstrates what was built, stakeholders applaud or raise concerns, and everyone moves on to the retrospective. Run this way, the review produces polished demos and no feedback that the team can act on. It is theater with a product backlog. The sprint review is a working session. Its purpose is inspection and adaptation at the product level: the team shows what was built, stakeholders engage with it substantively, and the conversation that follows informs the backlog.