I have realized that Liberating Structures are helping me with being a more successful ScrumMaster. I have written about my experienced benefits of Liberating Structures as concept, as well as links to useful resources in the first post of this series. This post is about my experiences and reflection on a specific Liberating Structure. The primary reason for writing about it is for the sake of my own reflection. If you can use it as well, that’s awesome. Also, if you disagree, have questions, or if you spot room for improvement, don’t hesitate to comment.
Context and reason for choosing
The team had previously identified the need of having a Definition of Ready. Previous attempts in making a Definition of Ready has resulted in a poor list, which the team stopped referring to quickly after the meeting. And when a team member mentioned the need of a Definition of Ready, heated and unfruitful discussions emerged about should we have it or not?; What should it contain, and what not?
As a Scrum Master I needed to find a way to facilitate a discussion that gave everybody equal possibility of contributing; a feeling of being heard; ownership for decisions made, as well as doing it effectively, to avoid wasting time of worthless discussions.
The “Min Spec” is designed to Specify only the absolute “must do’s” and “must not do’s” for achieving a specific purpose so I chose this for the Team’s Definition of Ready workshop.
The group consisted of 4 people in the room, and 2 via skype, and me (facilitator)
Steps and reflections
I highly recommend to read the original Min Spec description from the inventors, which I used as basis for this Definition of Ready workshop. Below I have listed the steps I went through, along with my reflections.
Continue reading “Liberating Structures – Min Specs for Definition of Ready”
Agile Reflections 