About | Donate | Books
Planning your next agile retrospective? Start with a random plan, change it to fit the team's situation, print it and share the URL. Or browse around for new ideas!

Is this your first retrospective? Start here!
Run great agile retrospectives: Get all activities and more for your ebook reader!

Check out the Retromat ebook!
Current Plan ID:
Replaced by JS

Landscape Diagram (#100)

Assess action items based on how clear they are and take your pick
Source: Diana Larsen adapted it from Human Systems Dynamics Institute
This activity is helpful when a team is facing an ambiguous, volatile, uncertain or complex set of problems and has many suggested action items to choose from.

Draw a Landscape Diagram, i.e. an x-axis labeled 'Certainty about approach' and a y-axis labeled 'Agreement on issue'. Both go from low certainty / agreement in their mutual origin to high towards the top / right. For each action item ask 'How much agreement do we have that solving this problem would have a great beneficial impact? How certain are we about the first steps toward a solution?' Place the note on the diagram accordingly.
When all actions are placed, shortly discuss the 'map' you created. Which actions will give the greatest benefit in the next iteration? Which are more long term?

Choose 2 actions from the simple / ordered area of the map or 1 action from the complex area.

(#)


Source:
Retromat contains 127 activities, allowing for 8349005 combinations (25x30x22x22x23+5) and we are constantly adding more.

Created by Corinna Baldauf

Corinna wished for something like Retromat during her Scrummaster years. Eventually she just built it herself in the hope that it would be useful to others, too. Any questions, suggestions or encouragement? You can email her or follow her on Twitter. If you like Retromat you might also like Corinna's blog and her summaries on Wall-Skills.com.

Co-developed by Timon Fiddike

As developer, product owner, scrum master and agile coach, Timon has been a Retromat user and fan for more than three years. He had quite a few feature ideas. In 2016 he started to build some of those features himself. You can email him or follow him on Twitter.