Agile Reflection
Use when asked to run a team reflection or retrospective in the spirit of the 12th Agile Manifesto principle — regular, honest process examination followed by actual behavior change — as distinct from a futurespective's forward-looking scenario exploration (see futurespective), which looks ahead rather than back.
The 12th principle behind the Agile Manifesto states it directly: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." See Agile Principles for this principle in the context of all twelve; this skill covers the reflection practice itself in depth.
What reflection actually involves
The whole team discusses recent experience: identifying bottlenecks, celebrating successes, and honestly acknowledging what needs improvement — examining communication methods, development practices, tool usage, or meeting structures for opportunities to do better. This isn't complaining about problems; it's actively seeking solutions and being willing to experiment with new approaches.
The part that's easy to skip: actually changing behavior
The principle's effectiveness lives entirely in the second half — "then tunes and adjusts its behavior accordingly." Identifying an issue during reflection isn't enough on its own; the team has to actually be willing to adjust, try a new technique, or abandon a practice that isn't serving it well. A reflection session that produces a list of observations but no actual behavior change has done the easy half of the principle and skipped the half that matters.
Why psychological safety is the precondition
Honest reflection requires team members to feel safe sharing genuine feedback without fear of blame or retribution — see Crucial Conversations for handling the harder conversations this can surface, and Ways of Working's emphasis on psychological safety as a team-success factor. Without it, a reflection session degrades into safe, surface-level comments that avoid the real issues.
What it builds over time
Regular reflection-and-adjustment creates a culture of learning and adaptation — teams become more resilient and responsive to changing requirements and technical challenges, and develop the ability to self-organize and self-improve rather than depending on external management to drive every change.
How it differs from a futurespective
Futurespective is forward-looking — imagining possible future scenarios to inform present decisions. Agile reflection is backward- looking — examining what actually happened recently to improve the team's process going forward. Both share the same underlying discipline of honest, structured examination, applied in opposite temporal directions.
Common pitfalls
- Reflection without follow-through — the single most common failure; see above — identifying issues isn't the same as fixing them.
- No psychological safety — without it, reflection produces only comfortable, low-value observations, missing the real friction points.
- Treating reflection as a one-time event — the principle specifies "regular intervals"; a single retrospective early in a project doesn't fulfill an ongoing improvement discipline.
- Reflecting on the same issues repeatedly with no actual change — if a retrospective keeps surfacing the same problem sprint after sprint, the team has diagnosed correctly but isn't closing the adjust-behavior loop.
Learn more
- Agile Principles for this principle in the context of all twelve.
- Futurespective for the forward-looking counterpart practice.
- Crucial Conversations, Ways of Working for the psychological-safety discipline honest reflection depends on.