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:

Big Upfront Planning is Out. Pivoting to Respond to Change is In

With uncertainty at an all time high, the response of many organisations in those early days was to batten down the hatches and the impact may be felt for many months to come. To survive through this, big up front planning will be out and pivoting to respond to change will be the new normal.  

READ MORE

Strategies for successfully leading remote agile teams

Leading remote agile teams was always going to be tricky. Implementing these 6 strategies can help leaders reduce team stress, address concerns about work progress, increase productivity for the  teams, and restore and maintain healthy communication channels.

READ MORE

Principles of Effective Governance

What governance best supports product development efforts using agile frameworks? Don’t be tempted to over complicated things with a hybrid committee structure. Scrum has all the roles and responsibilities you need to deliver value.

READ MORE

Copyright © Zen Ex Machina® and ™ (2020). All rights reserved. ABN 93 153 194 220

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