Explain Change Postmortem Like I'm Five

twitter logo github logo ・1 min read


Our new I.T. Contractors keep talking about a Change Postmortem and no one is explaining to us what this actually means, or what it benefits. Can someone explain simply what it is and why it's important to the change request process?

Edit: I've also heard this being called a "Change Moratorium"

twitter logo DISCUSS (2)
markdown guide

Process for Change Moratorium:

  1. Receive email saying someone has pushed a new change to source control.
  2. Receive alert from PagerDuty saying production system is down
  3. Place head in hands and sob.

You have now completed a Change Moratorium.

I don't know about the other thing.

Classic DEV Post from Oct 1 '18

Who's looking for open source contributors? (October 1st edition)

It's #hacktoberfest, so several folks have spun up similar threads. Follow that...

Ross Henderson profile image
Oracle Developer using SQL, PL/SQL and Web Development to build Application Express apps. Musician, gamer and dog lover.