Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
81 lines (58 sloc) 3.22 KB

Template from: Jane Miceli Ths accompanies the blog post [here|] Start every retrospective stating the following

  1. This is a blameless retrospective.
  2. We will not focus on the past events as they pertain to "could've", "should've", etc.
  3. All follow up action items will be assigned to a team/individual before the end of the meeting. If the item is not going to be top priority leaving the meeting, don't make it a follow up item.
  4. Please stick to the fact using nuetral langage; leave emotion and intention and inflamatory language out of this conversation.
  5. We want to talk about both the good and bad, pretty and ulgy. We do want to highlight advances we want to take.

Postmortem Template


Incident Summary
Incident Number Incident Severity
Postmortem Date War-room Required
Incident Lead Developer Lead

Postmortem Attendees

Name Role In attendence

Incident Timing

Start Time Incident Detected By(User-reported/ Ad-hoc monitoring/ Alerting system)
Detection Time Time to Detect (TTD)
Mitigation Time Time to Mitigate (TTM)
Resolution Time Time to Resolve (TTR)

Incident Timeline

| Date/Time | Who | What | Action | |-----------|-----|----_-|----------------| | | | | | | | | | | | | | | |

Customer / Business Impact

Internal Productivity Impact

What were the major contributing factors


Process Breakdown(s)

Root Cause(s)

Mitigation & Resolution

Open Questions

Person Question/ Answer
Q (who): A (who):
Q (who): A (who):
Q (who): A (who):

Lessons Learnt

What went well

What went badly

Where did we get lucky

Action Items & Followups

Action Item Type (Mitigate/ Prevent/ Process/ Other) Who Priority Bug # Due Date
Add item to postportem list Leader ASAP

Supporting Documents and References

[Best example ever|]

You can’t perform that action at this time.