liveBook · Manning

Retrospective

A retrospective is a structured reflection on past work or events in which participants identify lessons and improvements for future work.

How 7 Manning books explain it

Think Like a Software Engineering Manager

A retrospective is a structured team reflection used to inspect recent work and identify improvements to collaboration or process.

How it is used
Uses reflection to improve cross-functional collaboration, project delivery, management transitions, and time allocation.
How deep it goes
Provides reflection prompts and session goals, but does not specify a detailed team-facilitation procedure.
Examples
Illustrates reflection with management-transition questions and two ways to record time spent across priority quadrants.
What you can do after
Practice/perform it to identify improvements and actionable steps after shared work or a personal transition.

Read how Think Like a Software Engineering Manager explains retrospective →

Collaborative Software Design: How to facilitate domain modeling decisions

A retrospective is a recurring team meeting for examining recent work and agreeing on improvements to future collaboration or delivery.

How it is used
Uses post-session reflection to improve collaborative modeling, preserve feedback, and turn decisions into follow-up actions.
How deep it goes
Explains timing, participants, reflection questions, bias control, follow-up, and consequences of omission.
Examples
Uses session observations, participant feedback, photographs of physical visuals, a canvas, follow-up concerns, and premortem outcomes.
What you can do after
Diagnose collaboration problems, validate follow-up responsibilities, and adjust future sessions or organizational behavior.

Read how Collaborative Software Design: How to facilitate domain modeling decisions explains retrospective →

Build High Value Software Systems

A team meeting for reflecting on recent work and identifying improvements.

How it is used
Uses retrospectives to turn reflection on recent work into measurable improvements in end-to-end delivery flow.
How deep it goes
Details a repeatable loop for checking the previous change, choosing one friction point, assigning ownership, and measuring the result.
Examples
Uses a review-time Kaizen card, a sprint-by-sprint improvement log, and a table contrasting ceremony complaints with flow problems.
What you can do after
Practice/perform a retrospective that selects one delivery bottleneck, tests a specific change, and checks its measured result.

Read how Build High Value Software Systems explains retrospective →

Lead Developer Career Guide

A team reflection meeting used to examine recent work and identify improvements for future work.

How it is used
Uses team reflection to capture pain points, review velocity, and improve development processes.
How deep it goes
Explains the meeting’s improvement purpose and practical discussion targets but does not prescribe a fixed agenda or facilitation method.
Examples
Uses recurring bugs, failed regression tests, slow tasks, agile transformation, and annual leadership reflection as examples.
What you can do after
Practice/perform a retrospective by identifying problems, discussing specific improvements, incorporating feedback, and following up on changes.

Read how Lead Developer Career Guide explains retrospective →

Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A retrospective is a facilitated group reflection on completed work that identifies what is working and opportunities for improvement.

How it is used
Uses recurring group reflection to improve team delivery, modernization collaboration, and workshop behavior.
How deep it goes
Explains purpose, participants, cadence, and facilitation examples without prescribing a complete retrospective procedure.
Examples
Uses monthly team reviews, project retrospectives, and a workshop exercise asking what participants learned and would change.
What you can do after
Practice/perform recurring retrospectives that identify improvements and strengthen collaboration across participating teams.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains retrospective →

The Creative Programmer

A Scrum event in which a team reflects on completed work and identifies improvements to people, relationships, processes, and tools.

How it is used
Uses regular team reflection to improve people, relationships, processes, and tools after completed work.
How deep it goes
Defines the event, outlines five facilitation stages, and names techniques without detailing a complete meeting script.
Examples
Uses Check-In, Mad Sad Glad, Five Whys, Circle of Questions, Temperature Reading, Pomodoro, time tracking, and interruption patterns.
What you can do after
Practice/perform a Sprint Retrospective by gathering observations, generating insights, choosing improvements, and closing the reflection.

Read how The Creative Programmer explains retrospective →

The Coder Cafe

A retrospective is a structured team review of completed work intended to identify successes, problems, and improvements.

How it is used
Uses regular team reviews to support controlled growth and continuous improvement after major development milestones.
How deep it goes
Defines timing and purpose but stops short of prescribing a retrospective agenda, facilitation method, or follow-up checklist.
Examples
Uses a team review after a major development milestone as its concrete scenario.
What you can do after
Practice/perform a milestone review that identifies successful practices and improvements for subsequent development.

Read how The Coder Cafe explains retrospective →

Also covered in

What to know first

Related concepts

Questions about retrospective

What is retrospective?

A retrospective is a structured reflection on past work or events in which participants identify lessons and improvements for future work.

Which Manning books explain retrospective?

Think Like a Software Engineering Manager, Collaborative Software Design: How to facilitate domain modeling decisions, Build High Value Software Systems, Lead Developer Career Guide, Architecture Modernization: Socio-technical alignment of software, strategy, and structure, The Creative Programmer and The Coder Cafe.

What should I know before learning retrospective?

Manning books that teach retrospective usually introduce stakeholder, agile software development, feedback and communication first.

What is the difference between retrospective and continuous improvement?

A retrospective is a structured reflection on past work or events in which participants identify lessons and improvements for future work. Continuous improvement is a recurring process in which outcomes or feedback guide successive changes intended to improve a system, process, or result.

What is retrospective part of?

Retrospective is part of Scrum. Scrum is an Agile framework for developing and sustaining products through iterative, incremental work, defined accountabilities and events, and regular inspection and adaptation.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.