It’s humorous. Software program improvement groups (whether or not they instantly observe agile rules or not) usually try to enhance their processes over time. For the agile-oriented of us, that is performed in retrospectives. For others, it may be a unique assembly with the identical objectives — iterative enchancment.
It’s a straightforward dialogue to have, actually. It’s fairly a pure course of to zero in on the failings of how work is finished, particularly for such a logic-oriented group of people.
And everyone knows — there’s a lot that doesn’t go completely, which ought to be addressed.
However for some purpose, as an alternative of bettering, nothing appears to ever change. The identical points come up repeatedly, and issues worsen and worse over time.
Irrespective of how a lot there’s a sense of wanting to enhance, irrespective of how a lot the workforce talks about all the issues, irrespective of how a lot they formalize the advance course of to formally enhance the method… progress appears to be painfully gradual, if not utterly unachievable.
Okay, perhaps it’s not so humorous.
If the above sounds in any respect just like the experiences you’ve had with retros (or comparable), let’s…