3 ms·

I feel like I've experienced similar situations with post mortem and sprint retrospective processes. Sometimes shit goes wrong in a sort of unique way and peopl

I feel like I've experienced similar situations with post mortem and sprint retrospective processes. Sometimes shit goes wrong in a sort of unique way and people go too far with wanting to have the outcome always be "we will do X to make sure Y never happens again", even though X is more costly than Y in terms of engineering effort and business value. So I think this is also applicable to software design.

paxys 5y ago
This is so common in software jobs. Weird edge case escalation happens, engineering team spends a couple days handling it. In sprint planning/retro – "we have to make sure we never waste time over this again". Team spends weeks coming up with an optimal solution to address this very specific case. Original problem was rare enough that it doesn't happen again. A different edge case happens. Rinse and repeat.