4 ms·

How is this a postmortem? Everything seems to have gone well and nobody/nothing died... Edit: I was under the impression that postmortem was usually used to me

How is this a postmortem? Everything seems to have gone well and nobody/nothing died... Edit: I was under the impression that postmortem was usually used to mean a discussion of a failure of some sort. I was not aware of the project management version.

nanny 10y ago
Just a popular buzzword that they used without understand the meaning.
- dang 10y ago
  Please don't post acerbic swipes.
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.
justathought2 10y ago
The game jam itself has died, of natural causes at old age, and now it can be analyzed.
- hyperpallium 10y ago
  It is no more. It has ceased to be. It's expired.
alkonaut 10y ago
Agree. Stop using postmortem for neutral retrospectives. Postmortem ("after death") is a term used for diagnosing what went wrong, when something went wrong. It's the right term to use to report on a service outage on a website, for example. From Wikipedia project post mortem: "is a process, usually performed at the conclusion of a project, to determine and analyze elements of the project that were successful or unsuccessful. " Why use "after death"? it's not like latin words don't have meaning...
- startling 10y ago
  The game jam is over, and so is dead.
- Kronopath 10y ago
  "…usually performed at the conclusion of a project…" Conclusion, not unsuccessful conclusion. It's not incorrect to use it for any retrospective for a project that has concluded, regardless of whether it's successful or not.
  - alkonaut 10y ago
    But did it die? Is it referring to "after the lifetime" of the project, rather than during?
- tylorr 10y ago
  You could think of it as "death of the author". Also could be thought of as death of production.
- TeMPOraL 10y ago
  Prescriptive vs. descriptive. It's how this term is used already. I remember seeing it as a kid, when I first started dabbling in building games. If we want to enter fights about prescriptive definitions, then - at the risk of committing tu quoque fallacy - I'd like to ask the JS and nouveau-functional-programming crowd to stop renaming things that already have established names. Signed, Don Quixote.

nanny 10y ago

Just a popular buzzword that they used without understand the meaning.

dang 10y ago
Please don't post acerbic swipes.

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.

justathought2 10y ago

The game jam itself has died, of natural causes at old age, and now it can be analyzed.

hyperpallium 10y ago
It is no more. It has ceased to be. It's expired.

alkonaut 10y ago

Agree. Stop using postmortem for neutral retrospectives. Postmortem ("after death") is a term used for diagnosing what went wrong, when something went wrong. It's the right term to use to report on a service outage on a website, for example. From Wikipedia project post mortem: "is a process, usually performed at the conclusion of a project, to determine and analyze elements of the project that were successful or unsuccessful. " Why use "after death"? it's not like latin words don't have meaning...

startling 10y ago
The game jam is over, and so is dead.
Kronopath 10y ago
"…usually performed at the conclusion of a project…" Conclusion, not unsuccessful conclusion. It's not incorrect to use it for any retrospective for a project that has concluded, regardless of whether it's successful or not.
- alkonaut 10y ago
  But did it die? Is it referring to "after the lifetime" of the project, rather than during?
tylorr 10y ago
You could think of it as "death of the author". Also could be thought of as death of production.
TeMPOraL 10y ago
Prescriptive vs. descriptive. It's how this term is used already. I remember seeing it as a kid, when I first started dabbling in building games. If we want to enter fights about prescriptive definitions, then - at the risk of committing tu quoque fallacy - I'd like to ask the JS and nouveau-functional-programming crowd to stop renaming things that already have established names. Signed, Don Quixote.