How effective are your agile ceremonies?

From the Easy in theory, difficult in practice Blog
by
My musings on project management, project portfolio management and change management. I'm a firm believer that a pragmatic approach to organizational change that addresses process & technology, but primarily, people will maximize chances for success. This blog contains articles which I've previously written and published as well as new content.

About this Blog

RSS

Recent Posts

Justify yourself!

Projects are like springs…

How effective are your agile ceremonies?

“Medium” is another way of saying “Don’t make me choose”

Improving organizational culture through retrospective recognition


Categories: Agile


We hope that by conducting effective ceremonies we will achieve the agile trinity of improved value delivery, better quality and more fun.

But these objectives might be reached via multiple paths so we might not be able to prove causality between our ceremonies and those objectives.

We could ask our team members to tell us whether they see the value in the ceremonies and their perceptions are certainly important but is that enough? Can we identify measures which we could directly attribute to specific ceremonies so that we know if they are generating sufficient value?

Each agile framework provides its own ceremonies but given that Scrum is still the most commonly referenced one, let's focus on that framework's events.

The Scrum Guide calls sprints the heart of Scrum as these time boxes set the cadence for all other events. But to know if the Scrum heart is healthy we could track achievement of goals and value delivered sprint-over-sprint.

Sprint planning should answer the "what" and "how" of delivery for an upcoming sprint. Measuring its duration, quantifying the variation between what was expected to be delivered and what was actually delivered, and confirming whether the team is working at a sustainable pace might help assess the ceremony's effectiveness.

The daily scrum helps the team align themselves towards the accomplishment of sprint goals and to collaborate better. It should also reduce bad surprises and the need for traditional status meetings. To see if it is adding value, we could check how many work items are completed and measure how many unanticipated impediments are encountered each day.

The sprint review provides an opportunity to inspect what was accomplished and adapt the backlog accordingly. We can measure how many new requirements and course corrections emerged from the discussions. We could also conduct regular surveys with key participating stakeholders to gauge their satisfaction with the product and with the team.

Finally we come to the sprint retrospective. To gauge whether this ceremony is more than just a frequent "lessons learned" session, we could track the ratio of improvement ideas generated compared with how many were actually executed and provided expected benefits.

Agile ceremonies should add value. If not, we are just adopting the form of agility with none of its substance.

Posted on: December 02, 2018 07:00 AM | Permalink

Comments (7)

Please login or join to subscribe to this item
Good post Kiron. It's easy to become complacent even with great initiatives like Agile.

Good reminders Kiron and would like to add that in Retrospectivesm it is not necessary that we pursue all improvements at once, we can prioritize them and deal with them accordingly and track their progress and added value.

Good one, Kiron and thanks for sharing.

Hi Kiron, very valuable insights, and thanks for continuously enlightening us.

Please Login/Register to leave a comment.

ADVERTISEMENTS

"Outside of a dog, a book is a man's best friend. Inside of a dog, it's too dark to read."

- Groucho Marx

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events