3 ms·
> Retros are essential for running an effective agile workflow retros are very difficult to get right: many issues brought up cant be fixed by those attending
by andrekandre 4y ago
> Retros are essential for running an effective agile workflow
retros are very difficult to get right: many issues brought up cant be fixed by those attending (company policies, group okrs, platform issues, immovable deadlines etc), so the result many times is either self-flagellation or "improvement plans" that don't go anywhere... the end result being even more demotivating for a team....
if retros arent going to be effective at real improvement, then its better not to do them imo*
*there are other ways to improve teamwork/processes anyways
- bluGill 4y agoMy team always puts a 'general complainy pants' column on our retros so we can acknowledge things we have no control over and move to things we can.
- apocalyptic0n3 4y agoYeah, that's fair. I guess "Effective retros are essential" would be more accurate. It's just like any other step of the process: if the retro isn't working, figure out a different way to get the feedback. Nothing needs to be set in stone. You pick a starting point (i.e. Scrum + Retros) and make changes until things work as well as you need them to.
- icedchai 4y agoI've been in software development for just over 25 years. "Scrum" didn't start becoming a major thing until 2010-ish. Since that time, I could count the number of useful "retros" on one hand. It is almost always a waste of time. "What should we stop doing?" "This." (The retro.)
- siva7 4y agoSeems more like you never experienced a good scrum process. The retros were one of the most valuable things that always resulted in concrete actions taken otherwise i agree that it would be a waste of time.