Retrospective Conducting Notes

No Fixed Formula:

• Retrospectives are tailored to fit each team's unique needs, experiences, and growth.
• Various tactics may be necessary for different situations and teams.

Setting the Tone:

• Aim to maintain a positive atmosphere during the retrospective.
• Even difficult conversations should focus on improvements for future projects.
• Ensure team members feel comfortable sharing feedback, reinforcing a culture of open communication.

Involve Relevant Teams:

• Engage other partnering teams that may contribute valuable insights to the retrospective.
• If they opt not to participate, share your findings to improve cross-team communication and deliverable processes.

Structure of a Retrospective:

• Utilize templates that facilitate discussion and capture detailed feedback.

• Cover all phases of the project chronologically:

• Planning Stage:

  • Discuss what occurred and areas for improvement.

• Identify ‘lucky’ events and successful decisions.

• Lessons from the planning phase should be documented.

• Execution Stage:

  • Analyze the outcomes and execution against the original plan.
  • Gather feedback on specific challenges faced, such as meeting deadlines.

Lessons Learned:

• Create a section specifically for analyzing risks that materialized during the project.
• Example: Delayed website launch affected various teams and operations.
• Sales numbers declined, marketing needed to adapt, and stakeholders got involved.
• Reflections should lead to future prioritization of tasks with dependencies.

Action Items Table:

• Document actionable steps derived from retrospective insights.
• Include:
• Action item description.
• Type (e.g., tool, process, team).
• Owner responsible for the action.
• Relative links for tracking progress and documentation.

Future Considerations Table:

• Identify potential future risks or issues that need attention.
• Include:
• Need for project ownership transition.
• Type of issue (e.g., process, team).
• Contact resource for future reference.
• Relevant links to documentation or risk registers.

Engagement Techniques:

• Consider more creative and interactive methods for gathering feedback:
• Use color coding, sticky notes, emojis, and other fun elements.
• Ensure lessons learned are incorporated into future projects for continuous improvement.

Next Steps:

• Upcoming recap video will summarize the key lessons from this module, emphasizing the importance of reflective practices.