3 ms·

The good thing about the ceremony is having the whole team see whats being planned and giving input and helping each other out. But there might be a more effici

The good thing about the ceremony is having the whole team see whats being planned and giving input and helping each other out. But there might be a more efficient way to do this. Get everyone to read a published "this is our roadmap" page or something like that.

pstuart 5y ago
The ceremony is usually: what's the status of this Jira ticket?
- deleted 5y ago
  [deleted]
- steveBK123 5y ago
  The worst ceremony is the retrospective. Let's talk about what made us do a bad job this sprint. Some revolving list of "other team __" being slow/unreliable/hard to manage/etc.. The same 1 or 2 senior devs is tasked with taking away some discussion points to have with them. Rinse&repeat.
nicbou 5y ago
I've organised those meetings. You could halve their length by doing most of the grooming yourself, and just saving the remaining questions for the team. The meetings would only take a few minutes with Kanban, assuming the backlog stayed sorted. I just asked where the new tickets had to go in the current sorted list. These meetings would be much faster if project managers didn't clog the backlog with stream-of-consciousness tickets. However I was never an Agile guy. I trimmed the process heavily, and took up most of the backlog maintenance so that others could work.
- steveBK123 5y ago
  This requires the organizer to be organized. If management is running sprint ceremonies but in 5-6 hours/day of meetings, they come in unprepared and ad-lib. Our product manager sits in on the meetings such that he can says yes/no when questioned on tickets, but for all I know could be watching soap operas given his level of engagement.
steveBK123 5y ago
I think it all falls apart above a team size of 5-10. Just a tedious slog. The number of tickets you have to churn thru in backlog review / planning / closing / etc ceremonies is directly proportional to the number of devs..

pstuart 5y ago

The ceremony is usually: what's the status of this Jira ticket?

deleted 5y ago
[deleted]
steveBK123 5y ago
The worst ceremony is the retrospective. Let's talk about what made us do a bad job this sprint. Some revolving list of "other team __" being slow/unreliable/hard to manage/etc.. The same 1 or 2 senior devs is tasked with taking away some discussion points to have with them. Rinse&repeat.

nicbou 5y ago

I've organised those meetings. You could halve their length by doing most of the grooming yourself, and just saving the remaining questions for the team. The meetings would only take a few minutes with Kanban, assuming the backlog stayed sorted. I just asked where the new tickets had to go in the current sorted list. These meetings would be much faster if project managers didn't clog the backlog with stream-of-consciousness tickets. However I was never an Agile guy. I trimmed the process heavily, and took up most of the backlog maintenance so that others could work.

steveBK123 5y ago
This requires the organizer to be organized. If management is running sprint ceremonies but in 5-6 hours/day of meetings, they come in unprepared and ad-lib. Our product manager sits in on the meetings such that he can says yes/no when questioned on tickets, but for all I know could be watching soap operas given his level of engagement.

steveBK123 5y ago

I think it all falls apart above a team size of 5-10. Just a tedious slog. The number of tickets you have to churn thru in backlog review / planning / closing / etc ceremonies is directly proportional to the number of devs..