Comment on The Great Software Quality Collapse: How We Normalized Catastrophe
ozymandias117@lemmy.world 2 weeks agoWe’ll just set up another retrospective meeting and have a lessons learned.
Then we won’t change anything based off the findings of the retro and lessons learned.
PattyMcB@lemmy.world 2 weeks ago
Post-mortems always seemed like a waste of time to me, because nobody ever went back and read that particular confluence page (especially me executives who made the same mistake again)
shalafi@lemmy.world 2 weeks ago
Post mortems are for, “Remember when we saw something similar before? What happened and how did we handle it?”
monsieur_hackerman@programming.dev 2 weeks ago
They should also include the recommended steps to take to prevent the issue again, which would allow you to investigate why the changes you made (you were allowed to make the changes, right? Manglement let you make the changes?) didn’t prevent the issue