The Retrospective

The Retrospective is designed to provide a formal point for inspection and adaption by the whole Scrum Team with actions from lessons learned incorporated directly into the next Sprint. It should be a safe environment in which the whole Scrum Team can share failures and learn from them.
There’s always talk of whether the Product Owner should be involved, but so long as any hierarchical relationship with the Development Team doesn’t adversely impact the need to be honest, open and transparent, and learn what change is required of the Team to improve their performance in the coming Sprint, it’s important for the whole Scrum Team to use this key event to inspect their way of working and adapt their way of planning for the next Sprint.

download Retrospective Checklist

About the author

Related Posts:

Better together: Agile + Lean UX

How do you make Design Thinking, Lean UX, and Agile work together. Sprint 0? Design Sprints? Upfront design and planning tends to delay the delivery of value, so there must be a better way to use Scrum but also engage in discovery work at the same time without devolving into parallel design work. Integrating design, user research, and experimentation into Sprints is the key.

READ MORE

How do I run a Sprint Review?

The Sprint Review is one of five events in Scrum. It’s purpose is to inspect the Increment of work, get feedback, and then adapt the Product Backlog. And while many people refer to the Sprint Review as the “demo” or “showcase”, this is only one aspect of the Sprint Review.

READ MORE

How do I run a Daily Scrum?

Many people use the Daily Scrum to provide a status report to the Product Owner or Scrum Master, and even to stakeholders, but this event plays a more critical part in ensuring that the team continues to stay focussed on their goal and adapt their work so they improve their chance of achieving it.

READ MORE

How do I run Sprint Planning?

Sprint Planning is one of Scrum’s five events. There’s more to it than just making a plan. Importantly, as an action of empiricism, the team should be inspecting the Product Backlog and adapting, and creating, a Sprint Backlog that makes their plan to achieve the Sprint Goal, and deliver a potentially releasable Increment, transparent.

READ MORE
search previous next tag category expand menu location phone mail time cart zoom edit close