What is an anchors & engines retrospective?
A breakdown of the anchors & engines retrospective
There will always be a balance of both elements and this is certainly important. Having the right ratios is what is key to a successful delivery. If your project requires speeding up, then you may need to create more engines in the project or further boost (support) existing engines. At the same time, removing, cutting off or reducing the size of anchors that are creating a drag on the project will also have positive effects.
How to run an anchors & engines retrospective in TeamRetro
Start your anchors & engines retrospective with a click
Log into TeamRetro and choose the Anchors & Engines Retrospective template.
Ideas and tips for your Anchors & Engine retrospectives
- Set the stage. Let people know that the objective of the retrospective is to address the current velocity of the project and how the team can improve this. It’s a great time to remind people that the goal is not to blame individuals but identify behaviours, policies or actions that might be improved.
- Making this brainstorm anonymous will help provide a sense of safety especially if there are anchors that might otherwise be sensitive in nature.
- While one of the questions focuses on current engines, you can also ask them to brainstorm potential future engines. These are things that are not currently in place (such as an online retrospective tool) that could speed things up.
- Remember that there are some anchors that are necessary. Just like a real boat, an anchor is a useful device! Too many engines might push the ship in the wrong direction or off course.
- One way to quickly reflect on the effectiveness of the actions taken is to redo the anchors and engine retrospective and to see if there have been any changes in the comments or votes.
- A thank you goes a long way. Give a shout out to the team at the end of the meeting.