Please enable JavaScript.
Coggle requires JavaScript to display documents.
4.2.3.2 How to Conduct a Retrospective - Coggle Diagram
4.2.3.2 How to Conduct a Retrospective
Preparing for a Retrospective
Maintain a Positive Tone
Even during tough conversations, focus on continuous improvements.
Create a comfortable environment for open feedback.
Involve Other Teams When Necessary
Engage adjacent teams if their feedback is relevant to the project.
If they don’t participate, share retrospective findings with them to improve collaboration and communication.
Retrospective Process
Review the Project’s Stages
Go over the events step-by-step as they occurred in real time:
Planning Stage
: What worked and what didn’t?
Execution Stage
: Identify where the team succeeded or faced challenges.
Document
lessons learned
to reflect on risks and areas for improvement.
Example: Delayed Website Launch
Impact of Delays
The sales team missed their targets.
The marketing team had to adjust content and ads.
The sponsor faced pressure from investors.
Lesson Learned
Prioritize tasks with multiple dependencies to avoid future delays.
Action Items and Future Considerations
Action Items Table
Define actions based on lessons learned.
Include:
Type
: Is it a tool, process, team, etc.?
Owner
: Who is responsible for implementing the action?
Links
: Track items with relevant links.
Future Considerations Table
Identify risks or ownership changes for the next phase or quarter.
Include:
Type
: Process, team, or another category.
Contact
: Who can provide support if needed?
Links
: Include relevant documentation (e.g., risk register).
Making the Retrospective Interactive
Innovative Formats
Use tools like sticky notes, color coding, or emoji-based columns to engage participants.
Adapt the structure to suit your team’s needs and preferences.
Carrying Lessons Forward
Implementation of Feedback
Ensure lessons learned are applied to future projects.
Build on the retrospective insights to avoid repeating mistakes and improve outcomes.