Design Manager Hub
Product Design Reference
  • Welcome
  • Leadership Foundations
    • Leadership Blueprint
    • Good Managers
    • Bad Managers
    • Change Management
    • Leadership Styles
  • Managing People
    • Roles
      • Design/UX
      • Engineering
      • Product & Agile
      • Management
      • Levels
      • Soft Skills
    • Hiring
    • Onboarding
    • Culture
    • Performance Management
    • Feedback
    • Retention
    • Employee Exits
    • Managing Up
  • Meetings
    • Overview
    • One-on-Ones
    • Agile Meetings
    • Design Critiques
    • Stakeholder Meetings
    • Retrospectives
    • Workshops
    • Performance Reviews
    • All-hands
    • Skip-level Meetings
    • PIP Meetings
    • Exit Interviews
    • Public Speaking
  • Strategy
    • Overview
    • Vision & Goals
      • Product Vision
      • Goal Setting
      • Big Hairy Audacious Goal (BHAG)
      • Product Innovation Charter (PIC)
      • Product Trio
    • Prioritisation
      • Reach, Impact, Confidence, and Effort (RICE)
      • ICE Scoring
      • MoSCoW
      • Impact-Effort Matrix
      • The Kano Model
    • General Analysis
      • Cost-Benefit Analysis (CBA)
      • SWOT Analysis
      • The 5 Whys
      • The Sunk Cost Fallacy
    • Market Analysis
      • Product-Market Fit (PMF)
      • PEST Analysis
      • Customer Acquisition Cost (CAC)
      • Customer Lifetime Value (CLTV)
      • 6 Forces
    • Canvases
      • Business Model Canvas
      • Value Proposition Canvas
      • Lean UX Canvas
      • UX Research Canvas
      • Product Canvas
    • Customer Insights
      • User Journey Mapping
      • Net Promoter Score (NPS)
      • Customer Satisfaction Score (CSAT)
      • A/B Testing
      • Funnel Analysis
      • Jobs-to-be-Done (JTBD)
    • Organisational Alignment
      • McKinsey 7S
      • Weisbord's 6 Box Model
      • Balanced Scorecard
  • Process
    • Overview
    • Agile
    • Waterfall
    • Lean UX
    • Design Thinking (DT)
    • Design Sprint
    • DevOps
    • Cross-Functional Teams
    • Double Diamond
    • Reverse Double Diamond
    • GTD Methodology
    • Jobs-to-be-Done (JTBD)
    • Kaizen
    • Object-Oriented UX
    • Responsible, Accountable, Consulted, Informed (RACI)
    • Six Sigma
    • Work Breakdown Structure (WBS)
  • Cognitive Toolkit
    • Overview
    • Prioritisation
      • 6 Box Framework
      • Eisenhower Matrix
      • Impact-Effort Matrix
      • The Pareto Principle
    • Problem Solving
      • First Principles Thinking
      • Systems Thinking
      • Inversion Thinking
      • Abstraction Laddering
      • Occam's Razor
      • Divergent & Convergent Thinking
    • Decision Making
      • The Map Is Not the Territory
      • The Cynefin Framework
      • Second-order Thinking
      • System 1 & System 2 Thinking
      • The Hard Choice Model
      • OODA Loop
    • Managing People
      • Skill-Will Matrix
      • The 4 Worker Types
      • The 9 Employee Types
      • Maslow's Hierarchy of Needs
      • The Peter Principle
      • Dunning-Kruger Effect
      • Circle of Competence
      • Hanlon's Razor
      • Johari Window
      • The Minto Pyramid
  • Insights
    • Insightful Articles
    • Research Foundations
    • Design Roles
  • Resources
    • Articles
    • Books
    • Templates
    • Education
    • Conferences
    • Video Hub
    • Quotes
    • Experts
    • Software
Powered by GitBook
On this page
  • Sprint Retrospective
  • Release Retrospective
  • Project Retrospective
  • Team Retrospective
  • Product Retrospective
  • Technical Retrospective
  • Further Reading
  1. Meetings

Retrospectives

Last updated 6 months ago

A retro or retrospective meeting is a time for a team to look back on a project or a period of work. They discuss what went well, what could have been better, and what lessons they can learn for future projects. It's a way to improve and learn from past experiences. There are different types of retrospective meetings, each with their own unique structure and focus. However, they are typically held after a project or a sprint in agile environments. Inessence, they are a post-sprint meeting to review what went well and what didn't in order to work more effectively going forward.

Sprint Retrospective

This is the most common type of retrospective, held at the end of each sprint in an Agile development process. The team reflects on the past sprint and three basic questions are asked.

  • What actions would you start?

  • What actions would you stop?

  • What actions would you continue?

Release Retrospective

Similar to a sprint retrospective, but focused on a larger release or project milestone. The team reflects on the entire release, identifying successes, failures, and lessons learned.

Project Retrospective

This is a retrospective held at the end of a large project or initiative. The team takes a broader look at the entire project, evaluating its overall success, identifying areas for improvement, and capturing lessons learned for future projects.

Team Retrospective

This retrospective focuses on the team's overall performance and dynamics. The team discusses its strengths, weaknesses, communication patterns, and collaboration habits. The goal is to identify areas for improvement in how the team works together.

Product Retrospective

This retrospective focuses on the product itself. The team discusses the product's features, user experience, and overall value proposition. The goal is to identify areas for improvement in the product and its development process.

Technical Retrospective

This retrospective focuses on the technical aspects of a project or product. The team discusses the code quality, architecture, testing practices, and other technical concerns. The goal is to identify areas for improvement in the team's technical practices.

Further Reading

LogoSprint Retrospective | TeamRetroTeamRetro
LogoEffective Team Check-Ins: What Every Leader Should KnowNova. Blog.