Just a site where I archive interesting reads I've encountered online
This article is published in Agile NXT. This article describes some of the concepts Evelien Roos learned and how you can apply “brain science” to make your Scrum events more effective.
https://articles.xebia.com/using-brain-science-to-boost-your-scrum-events
Scrum’s sprint reviews are intended to surface issues that customers, users and stakeholders may have with the team’s work of the current sprint.
But sometimes, too many issues are identified. Not only can these be brutal for the team, Scrum Master, and product owner to sit through, having a lot of issues identified during the sprint review is a strong indicator that the team’s process could be improved.
Here are a few things to consider if you are finding too many problems during your sprint reviews.
In addition to trying one or more of these fixes, use the retrospective to discuss why so many issues were found during the review.
Finding problems isn’t necessarily a problem itself, but finding them as late as the sprint review is.
Addressing that and finding issues earlier will help your team succeed with agile,
Mike Cohn
By using this format for the Sprint Review you’ll achieve its purpose: inspect the increment that was created during the Sprint as well as to adapt the Product Backlog based on new insights, ideas, and changes that result from this inspection. The Liberating Structures ensure it’s done in such a way that everyone is continuously involved & engaged. Shaping the next steps becomes a joint effort as well.
Read the complete article here: https://medium.com/the-liberators/improving-the-sprint-review-with-liberating-structures-variant-2-35eb011abc60
For an upcoming meetup I’m preparing a session on how to use LS for Scrum Events and especially events where the participants are distributed and joining the event remotely.
Here’s a brief overview of some LS that can be used for the different Scrum events. I’ve marked all structures with an * that I’ve used myself in a distributed setting.
On the liberating Structures website you can find a design checklist for virtual meetings. Since the link is currently no longer working, you can find the document here:
In this short video Christiaan Verwijs gives some simple examples of the many ways in which Liberating Structures can be used as part of the Scrum Framework.
The structures that are mentioned are:
In this post, The Liberators explain the Liberating Structure What, So What Now What and how they use this structure within the context of Scrum.
Read the complete article here: https://medium.com/the-liberators/create-shared-understanding-with-what-so-what-now-what-6dda51d5bcf9
The Speed Boat game explores user’s pains and jobs. The heart of the game is a metaphor of a Speed Boat (product). It has anchors: current problems and pains in using the Product that prevents it from moving forward. The stronger the anchor, the higher amount of customer pain, the more anchor slows the boat down.
Read all about it here: https://www.scrum.org/resources/blog/enhancing-sprint-review-speed-boat-game
Some insights of this video include:
If your Sprint Review looks like this, you are doing it wrong:
Signs you are doing it right: