3 ms·

True story: A project I was on earlier in the year was full on Agile, with constant meetings - daily standups, weekly retrospectives, weekly scrum-of-scrums, w

True story: A project I was on earlier in the year was full on Agile, with constant meetings - daily standups, weekly retrospectives, weekly scrum-of-scrums, weekly reviews/demos, bi-weekly product backlog refinements, weekly story refinements, weekly product backlog planning, weekly sprint planning, frequent meetings about git branching strategies and near daily "way of working" meetings. And of course there were some relatively meaningful small meetings closely related to actual development work. Everyone was losing the will to live, including myself - there simply wasn't enough time to actually work! I had a word with the project manager, and with a totally casual manner he said: "OK, let's have a meeting with the whole team to discuss it".

pc86 7y ago
It's easy to poke fun but this seems like a 100% reasonable response when the alternative is changing the entire schedule of the entire team based on the feedback of a single person. And it doesn't seem like any one person should be attending all of these meetings (agreed it's definitely too many though).
- GordonS 7y ago
  > It's easy to poke fun but this seems like a 100% reasonable response when the alternative is changing the entire schedule of the entire team based on the feedback of a single person So, it's meant to be an amusing anecdote on HN; I haven't told the entire story of the project :) The PM had heard this from several other team members alread, several times. The difference is I was tech lead, so he listened a bit more to me, and I was also quite adamant this time (I'd tried to tell him more politely numerous times). > And it doesn't seem like any one person should be attending all of these meetings Bingo, this was the biggest problem - the project manager in particular was bad for telling irrelevant people to join meetings.
mr-ron 7y ago
All those meetings are necessary if you do by the book scrum. But usually it's the tech lead role that's most important to have attend. Did the whole team attended each of these?
- GordonS 7y ago
  Often, yes, or if not the whole team it was most of it.

pc86 7y ago

It's easy to poke fun but this seems like a 100% reasonable response when the alternative is changing the entire schedule of the entire team based on the feedback of a single person. And it doesn't seem like any one person should be attending all of these meetings (agreed it's definitely too many though).

GordonS 7y ago
> It's easy to poke fun but this seems like a 100% reasonable response when the alternative is changing the entire schedule of the entire team based on the feedback of a single person So, it's meant to be an amusing anecdote on HN; I haven't told the entire story of the project :) The PM had heard this from several other team members alread, several times. The difference is I was tech lead, so he listened a bit more to me, and I was also quite adamant this time (I'd tried to tell him more politely numerous times). > And it doesn't seem like any one person should be attending all of these meetings Bingo, this was the biggest problem - the project manager in particular was bad for telling irrelevant people to join meetings.

mr-ron 7y ago

All those meetings are necessary if you do by the book scrum. But usually it's the tech lead role that's most important to have attend. Did the whole team attended each of these?

GordonS 7y ago
Often, yes, or if not the whole team it was most of it.