Remote Agile (Part 2): Virtual Liberating Structures
Virtual Liberating Structures — answering the question of how we can use the powerful toolbox of inclusive and collaborative practices.
Join the DZone community and get the full member experience.Join For Free
Last week, we addressed basic practices and tools of remote agile with distributed teams. Based on that article, I also ran a live virtual class, the recording of which will be made available soon on the Age-of-Product’s Youtube channel. This follow-up post now delves into virtual Liberating Structures, answering the question of how we can make use of the powerful toolbox of inclusive and collaborative practices in a remote setting.
Created by Keith McCandless and Henri Lipmanowicz, Liberating Structures cover a set of easy to learn, yet powerful ways to collaborate as a team — even as a (very) large team by Scrum standards, overcoming traditional communications approaches like presentations, managed discussions, or another disorganized brainstorming at which the loudest participants tend to prevail.
Generally, Liberating Structures are well suited to improve the level of engagement among participants of Scrum events, thus stimulating the kind of outcomes that are necessary to create learning organizations. Liberating Structures also provide an excellent toolbox to handle Product Backlog refinements or improving the Definition of Done of an engineering organization.
Moreover, Liberating Structures are a great tool when peers come together to jointly figure out how to improve as an individual as well as a professional.
LS for Scrum
More than a year ago, my Berlin Hands-on Agile meetup started exploring the possibilities to use Liberating Structures specifically in the context of Scrum. As a result, we have explored 15-plus Liberating Structures so far and started tailoring Liberating Structures strings to specific situations, such as Scrum events, or the Megabrain.io scenario, our struggling startup.
In this article, I revisit most of those microstructures and provide initial thoughts on how to use them as virtual Liberating Structures.
Design Elements of Virtual Liberating Structures
Virtual Liberating Structures share a set of common design principles:
- Breakout rooms are used to divide the whole group of participants into smaller workgroups, starting with pairing up two participants. I am using Zoom for that purpose.
- Muting/unmuting is used — beyond the purpose of reducing noise — to mark different states of participants. For example, in the Conversation Café exercise during rounds 1, 2, and 4, everyone is muted except the individual that is sharing his or her thoughts.
- Video on/off is used to distinguish between roles, for example, between the inner circle and the outer circle of the User Experience fishbowl. Here, the outer circle members turn their video off as well as mute themselves.
- A shared workspace is needed to aggregate findings, for example, as the result of a 1-2-4-All session. This can be a simple Google slide or a FunRetro.io board.
- Workbooks are useful to provide participants with instructions when working in breakout rooms; for example, a detailed description of how an individual Liberating Structures works.
- A chat channel is used to facilitate communication within the whole group.
How to Practice Individual Virtual Liberating Structures
Let‘s explore the microstructures for their potential to become virtual Liberating Structures. The ordering is based on the LS Menu of the Liberating Structures website:
- 1-2-4-All: To cover 1-2-4-All, we need breakout rooms and a place to aggregate the findings. We start with everyone in the whole group for a minute in silence; then, we split the whole group into pairs using Zoom’s breakroom feature for 2 minutes. After that round, we merge two pairs into a group of four for five minutes — this has to be done manually by the host — and the group aggregates its findings, for example, on a Google sheet prepared for each group in advance. We can introduce each group’s findings to the whole group by screen sharing in a Shift and Share.
- Impromptu Networking: This is a simple application of breakout rooms; just make sure that after each round, the pairs are created a new. Provide the invitation and the three questions in the workbook in advance.
- Appreciative Interviews (AI): AI is another application of breakout rooms, workbooks, and a shared workspace. Introduce the steps in the whole group, break into pairs for the individual interviews, merge two pairs into one breakout room, then gather insights within the group workspace to share later with the whole group. AI works well with 1-2-4-All and Shift and Share. Make sure that you provide a description of AI in the workbook, and also consider time-keeping via the breakout room broadcasting function for the admin. (Participants tend to get lost otherwise.)
- TRIZ: Again, TRIZ is a combination of basic elements of virtual Liberating Structures: breakout rooms, embedded 1-2-4-All, joined workspaces, Shift and Share when several groups are working on the problem. Consider time-keeping via the breakout room broadcasting function, as participants are likely to be highly engaged and may lose track of time.
- 15% Solutions: We use a similar procedure as with TRIZ. Consider aggregating all suggestions in the whole group’s shared workspace for clustering and ranking by voting. (I like to use a FunRetro.io board for that purpose: it is simple and does not need much explaining.)
- Troika Consulting: We start by creating breakout rooms for groups of three. Consultants and the consultee have the initial conversation; then, the consultee turns around on his or her chair for the consulting phase. Alternatively, both consultants stop broadcasting their video, so the consultee is just listening to what they have to say. Again, as the facilitator consider time-keeping on behalf of the groups.
- What, So What, Now What?: Also, W3 is a sequence of individual work and group work based on breakout rooms, aggregating findings in shared workspaces to be shared with the whole group in the end.
- Shift and Share: That is a simple one: each workgroup presents its findings to the whole group by screen sharing. Alternatively, if the shared workspace has been created in advance, for example, Google Slides with a slide per workgroup, the moderator can share his or her screen while someone from the team is explaining the findings to the whole group. This reduces the stress of switching screen sharing on and off among several groups.
- 25/10 Crowd Sourcing: This one LS that I haven’t yet tried in the virtual realm. I am still thinking about how to make this happen. I would probably miss the dancing while swapping the suggestions…
- Min Specs: Like What, So What, Now What?, Min Specs is a sequence of individual work and group work based on breakout rooms, aggregating findings in shared workspaces to be shared with the whole group in the end.
- Conversation Café: Create groups with the breakout room function, and identify a host for time-keeping. During rounds 1, 2, and 4, where one participant is talking while the others are listening, use mute for the listeners. Once the timebox has expired, the previously talking participant “hands over” the microphone by calling out the next one in line and then muting him- or herself. As the facilitator, also consider providing a matrix — rounds by speakers with checkboxes — to the hosts to ensure that everyone has a fair share of airtime.)
- User Experience Fishbowl: Working in the whole group, use mute and video off to distinguish between the inner circle and the outer circle of the User Experience fishbowl. Here, the outer circle members turn their video off as well as mute themselves. Gather additional questions through the chat channel from the out circle members. A facilitator should pass on these new questions in due time. (While discussing the topic at hand, the inner circle members should try not to read these new chat messages at the same time.) Use W3 to debrief in the whole group.
- Heard, Seen, Respected (HSR): A classic application of Zoom’s breakout room function. Again, as a facilitator, consider becoming the external time-keeper.)
- Lean Coffee: Lean Coffee is an excellent example of a workaround for virtual Liberating Structures. Gather all the input in the usual way, for example, engaging in 1-2-4-All, and gather those on a FunRetro.io board while voting is turned off. (Use several columns if the whole group is large to speed up the gathering process.) Then ask the whole group to cluster similar topics, then turn on the voting and order the remaining entries by votes. For here, you continue with a whole group discussion, or you engage smaller groups with breakout rooms.
- Ecocycle Planning: Principally, we apply the techniques as before, from breakout rooms to shared workspaces. Speaking of which, given the large number of “stickies” that you usually create during Ecocycle planning, you may want to consider a specialized online board application such as Miro or Mural. (Please note that both tools are not self-explanatory and require a prep session with participants to avoid frustrating them.)
Conclusion — Virtual Liberating Structures
While there will always be a bit of the magic missing that in-person Liberating Structures sessions have, I do believe that there is plenty of opportunities to create a sound experience with virtual liberating Structures.
Of course, they are different — which can be attributed mostly both to the lack of nearness among the participants as well as the limited technical support of virtual Liberating Structures. However, given the alternatives, virtual Liberating Structures again prove to be far superior to other competing virtual practices.
Liberating Structures are developed by Henri Lipmanowicz and Keith McCandless and are licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.
What experience have you made with applying virtual Liberating Structures? Please share it with us in the comments.
Published at DZone with permission of Stefan Wolpers, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.