Alternative to "autopsy" for software

Solution 1:

A post-mortem is the term I'm familiar with:

An analysis or discussion of an event held soon after it has occurred, especially in order to determine why it was a failure

I've participated in more than a few software post-mortems myself.

Solution 2:

Both post-mortem and retrospection work as stated by other answers, but first, some context from an English speaker in the industry from Silicon Valley.

Where I work, we use post-mortem for the end of a release, and we use retrospection for the end of a Sprint.

So really, this comes down to context. If you're talking about the end of a release, I advise post-mortem. If it's just a Sprint, go with retrospection. Technically, retrospection works for both, but it can get confusing depending on your work environment and workflow.