2 ms·
Postmortem is the de facto name for blog posts summarising how things went after a, typically, game development jam. Nothing bad has to go wrong, it's just call
by grenoire 10y ago
Postmortem is the de facto name for blog posts summarising how things went after a, typically, game development jam. Nothing bad has to go wrong, it's just called that.
- ronjouch 10y ago> Nothing bad has to go wrong, it's just called that. Correct. > Postmortem is the de facto name for blog posts summarising how things went after a, typically, game development jam. Not just this. Postmortem is a generic Project Management term. A process/meeting after the project's end (or the end of a part of the project) where collaborators discuss what went right/wrong is called a postmortem. This is formalized by the bible of Project Management, the PMBOK, and Wikipedia has a nice article about the notion: https://en.wikipedia.org/wiki/Postmortem_documentation https://en.wikipedia.org/wiki/Postmortem_documentation Programmer's TL;DR: your scrum sprint retrospective and its "what went wrong" / "what could have been better" is a Postmortem.