Example mapping is a great way to have a discussion about your user stories and can be used to make refinement sessions more interactive.
Read all about it here: https://cucumber.io/blog/example-mapping-introduction/
Just a site where I archive interesting reads I've encountered online
Example mapping is a great way to have a discussion about your user stories and can be used to make refinement sessions more interactive.
Read all about it here: https://cucumber.io/blog/example-mapping-introduction/
This article describes an interesting card game that will help you improve your refinement process: https://hackernoon.com/35-cards-which-will-improve-your-backlog-refinement-process-and-engage-every-team-member-54f929fdd282
The original blogpost that contains a lot of retrospective idea’s that were bundled later in a nice book can be found here: https://agilestrides.com/blog/40-ideas-to-spice-up-your-retrospective/
If you need some inspiration for a fun retrospective, take a look at this board game:
Inspired by Carmen Guerra Jurado her holiday in Greece, it has:
The teams enjoyed it and results were fruitful! (Pun intended.) The game itself still needs some tweaking. But Monopoly better watch its back! 😆
Natuurlijk is er geen standaard lijstje van de beste vragen en is ieder team en ieder vraagstuk in een team uniek. Vanuit Loes van Luijk haar teamcoachervaring en opleidingen heeft ze wel krachtige vragen ontdekt die zij als teamcoach vaker inzet.
Lees het volledige artikel hier: https://www.linkedin.com/pulse/de-10-beste-vragen-aan-je-team-loes-van-luijk/
A nice write-up of what a Scrum Master can do all day by Joshua Partogi, read the complete article here: https://www.scrum.org/resources/blog/what-does-scrum-master-do-all-day
Interesting article from Ram Srinivasan with some great tips on working with distributed teams, including research why having co-located teams is better can be found: https://www.scrum.org/resources/blog/remote-teams-and-virtual-facilitation
Here are my major takeaways.
Last Thursday I facilitated an internal Liberating Structures meetup together with Lars Coppens at ABN Amro. This meeting had a specific goal: How can you use Liberating Structures within Scrum events and especially with a distributed team. The time box and our challenge? Within 1.5 hours introduce several Liberating Structures and explain how to use these structures, so that the can be used with a distributed Scrum team. In this post I will describe how we designed this session.
I started by creating a list of structures I’ve used myself within Scrum events and added structures I could find others have used. You can find the list here.
The best way to learn Liberating Structures is not only to learn how to use them but also to experience them yourself. But because of the limited time, we thought people might be disappointed when we only covered a single or maybe two structures. We therefore tried to think about another way to give the participants as much information as possible without making it just a boring one-way presentation.
Our first thought was using a Shift & Share. We could set up a station for every Scrum event and just make a presentation out of it. But that would be boring! Instead, we thought of asking the attendees to identify structures that we could use for each event. That automatically made us think of doing Caravan. Wouldn’t it be nice to let the people themselves add additional Structures to the initial list and create a long list of possible structures for each event?
But then we thought of a possible flaw in this plan. A lot of people still don’t know Liberating Structures and are attending this meetup to learn about them. So without briefly explaining the structures, it would probably be very hard for them to select structures for an event.
We eventually came up with the idea to use Open Space Technology to let the participants pick the structures they want to learn about. This way we had an opportunity to share as much information as possible in a way that people could decide for themselves what they wanted to learn. And maybe we could close the session by asking the participants which structures they would like to experience themselves. With this output, we could structure our future meetups.
We already had an extensive list of structures that could be used to facilitate Scrum events. So we picked a number of them that could be used for multiple events and wanted the participants to choose from these.
With the possibility of over 40 participants, how would we find ourselves other facilitators and quickly decide on a schedule? We could just ask them, but what is the fun in that 😉 so what if we would use a Gallery Walk as input for the Open Space?
The eventual string we came up with looked like this:
To introduce the participants to each other, we used Folding Spectrogram as a way to form the first pairs for Impromptu Networking.
We used the following invitation for Folding Spectrogram:
After everyone was paired up, we used the following invitations to start Impromptu Networking:
We created posters for the selected Liberating Structures which we spread across the room together with the card from the card deck and an icon of the structure and invited the participants to walk around in silence first to see which structures there were.
Next, we invited them to move to the structure they had the most experience with. We made a mistake to include 1-2-4-All which of course attracted the most people 😉 but luckily there were also people at other structures. For us, this was an indication we might find possible facilitators for the Option Space.
In order to select the topics for the Option Space. We asked the attendees to move to the structure they wanted to know more about.
After this, we asked who would want to facilitate one of the structures where people gathered around and quickly found a couple of volunteers. The rest of the slots would be facilitated by Lars and me and therefore, we invited the attendees to create their own schedule using the remaining structures.
We proposed to facilitate each slot using the following steps:
When the time box was over, we quickly debriefed what we had discovered and introduced an online tool called mentimeter.
To wrap up the meeting and gather input for our next meetups. We used the tool mentimeter to ask the participants two questions.
Mentimeter is an online tool that I use a lot with distributed teams to collect feedback from individuals. I’m still planning on writing a separate article on this, so keep an eye out for it in the future 😉
We could have used a 25/10 to determine which Liberating Structures our public wants to experience during the next meetup. But using the ranking question in mentimeter we could get a similar outcome in less time. And at the same time let everyone experience how easy menti.com can be used.
As a wrap-up question, we asked the participants for feedback on this session and if they enjoyed it. Luckily most of them did! For me the best feedback we received is that almost a third of them wants to experience more structures in-depth and thinks 1.5 hours might be too short to do so. So, challenge accepted! I’m looking forward to facilitate future meetups!
What do you think of the string we came up with? Do you have any tips on what we could’ve done better? Let me know!
as also published on: https://www.linkedin.com/pulse/designing-meetup-liberating-structures-jeroen-de-jong/
The items on the left bring us the best value and help us perform an efficient Daily Stand-up Meeting.
Team Connection OVER Status Update
Simple but Specific OVER Generic Information
Outcomes Mapped to a Goal OVER Creation of Output
Highlight Relevant Topics OVER Problem Solving and Storytelling
Read the complete article here: https://www.linkedin.com/pulse/daily-stand-up-manifesto-raluca-mitan/