3 ms·
> We do that in software too. It’s called an agile retrospective. A retrospective is not an incident postmortem, very different things. A retrospective tries
by jjav 3y ago
> We do that in software too. It’s called an agile retrospective.
A retrospective is not an incident postmortem, very different things.
A retrospective tries to look at how the agile process went wrong again this past sprint, but is not focused specifically about one production incident.
Companies should be doing incident postmortems on any incident of significance to identify action items to improve what went wrong on that specific case.
- TheNewsIsHere 3y agoWholeheartedly agreed. A retrospective’s documentation is essentially the smallest opaque piece of what an investigation would draw upon working backward. It happens fairly quickly after the causal factor is introduced and is likely to be completed before the software actually causes harm in production at a scale like this. The results of a retrospective could make for a good source for recommendations, but only if it covered the causal factors.