4 ms·

I like some of the principles of agile but like the problem is the ceremonies chew up so much time. I have an none technical project manager who is absolutely i

I like some of the principles of agile but like the problem is the ceremonies chew up so much time. I have an none technical project manager who is absolutely in love with everything agile. I am in a project where basically 3 of us are going to do the work. I sit next to one of the people but we still have to have daily stand ups. I am one of those people who works in longish chunks, I can sit for two solid hours or more and not move if I am in the zone. But now because Agile says we need all these meetings and ceremonies I feel like half my week in is in the agile meetings or preparing for these meetings. Yes I have raised these issues but been overwritten by management. I am in Africa so I cannot just get another job.

baq 7y ago
Ceremonies are part a process to get shit done. Being agile doesn’t mean to follow a strict process but to create a process that suits all stakeholders and the dev team in particular. I’m trying to say your team isn’t agile, it’s using a cookie cutter process template most likely. Print out the agile manifesto and tape it to the cofee machine.
- GiorgioG 7y ago
  That's all well and good if you don't work in a large organization. Taping anything to the coffee machine in my organization requires committee approval.
mcv 7y ago
In Scrum, and doubly so in Agile, meetings should not be taking up much time. Meetings are to make clear what needs to be done, because otherwise you end up wasting time on things that don't need to be done. Dailies should take a maximum of 15 minutes. Sprint review, retrospective and planning take more time, but that's only once per sprint, and they're still meant to be productive meetings. If the process isn't working for you, the retrospective is the time to bring that up, and together you can decide how to change your process so that it works better for you. If your concerns are being overridden by management, your process is neither Agile nor Scrum.

baq 7y ago

Ceremonies are part a process to get shit done. Being agile doesn’t mean to follow a strict process but to create a process that suits all stakeholders and the dev team in particular. I’m trying to say your team isn’t agile, it’s using a cookie cutter process template most likely. Print out the agile manifesto and tape it to the cofee machine.

GiorgioG 7y ago
That's all well and good if you don't work in a large organization. Taping anything to the coffee machine in my organization requires committee approval.

mcv 7y ago

In Scrum, and doubly so in Agile, meetings should not be taking up much time. Meetings are to make clear what needs to be done, because otherwise you end up wasting time on things that don't need to be done. Dailies should take a maximum of 15 minutes. Sprint review, retrospective and planning take more time, but that's only once per sprint, and they're still meant to be productive meetings. If the process isn't working for you, the retrospective is the time to bring that up, and together you can decide how to change your process so that it works better for you. If your concerns are being overridden by management, your process is neither Agile nor Scrum.