Loading content
A retrospective is a structured team practice for regular reflection on ways of working, collaboration, and outcomes. In a timeboxed session the team identifies successes, problems, and concrete improvement actions. The method fosters continuous learning through agreed experiments and a facilitator who ensures focus and tracks commitments.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
A retrospective is a facilitated learning and improvement format in which a team examines its collaboration or a work period and agrees concrete next steps.
Retrospectives became established in agile software development as a recurring review; they have no single inventor. The practice continues earlier after-action reviews and spread through Scrum and Agile teams.
Guide the team through a learning arc: collect facts and observations, explore patterns and causes, choose a few improvements, and make their implementation visible. A safe frame separates observation from blame; the next session checks what actually changed.
Concrete events and experiences provide the shared starting point.
Patterns and causes explain how collaboration or outcomes unfolded.
A few owned experiments turn insights into changed behaviour.
Retrospectives help teams derive adaptations from their own experience and improve collaboration continuously. They need time, psychological safety, and followed-through actions; a complaint round produces little learning.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.