Project retrospective: Add feature name
👩🏻‍💻 Project lead/manager: @someone
đź‘Ą Project members: Role: @someone, Role: @someone
đź—’ Related specs: Type plus (+) to link a Paper doc
đź’¬ Discussion in Team communication app: đź”—Link to channel

Goal

This document aims to help writing a project launch post mortem and start a discussion with all project team members. Everyone should share their own experience with everyone.

Start a new thread to start a discussion

The project leader tags/addresses everyone who took part in the project with a new thread with the following structure:

Thread Structure:

Initial words like “Hi everyone”…

Project timeline and what happened when:
C1902: (Research, design exploration)
  • Reviewing research material
  • Discussions and agreeing on problem statement
  • Redesigned system messages
  • Started design exploration spec

C1903:(Finalising designs, feedback, copy)
  • Finalise all designs and prototypes, ask for feedback from designers and developers
  • Asked for copy feedback

C1904-C1905: (Polishing design spec; Implementation)
  • Mostly implementation

C1906: (QA& Release)
  • Finishing implementation
  • Polishing, reviewing, internal testing
  • Release preparation: In-app education, blog post, HC article etc.
Did we meet our primary goal?
  • Did we ship the feature in its planned form or did we have to make sacrifices in the scope?
  • Are we and our users satisfied with the result?
Write away!…


Did we have enough resources?
  • Were there enough people on the team to fulfil our goal?
Write it down…


What went well and what can we take away?
  • Was the internal feedback timely, have feedback loops been short?
  • How was the work between all team members from developers, designers, marketing, support?
  • Was there enough communication or delays?
  • Anything that stood out and made the project itself and the launch a success? 
Write away, give people props!…