Use: Best for small teams who want to focus more of their time brainstorming solutions to posted issues.
Length of time: 60-90
Short Description: The Do-Si-Do allows team to focus on potential solutions to team members’ biggest issues my moving from station to station like an old fashioned dance!
Materials: Flip Charts, Markers, Timer, & Smaller, Bright Post It Notes
Process: 1. Facilitator presents an obvious theme or objective affecting the team. (i.e. Meeting our potential) Team agrees it’s an important topic. (Optional: Facilitator can present a few hot themes and team votes on one that resonates most.)
2. Facilitator rips out big sticky sheet of paper from flip chart. Sticks it to wall. Adds a sheet to the wall for every team member, so every team member will start in front of a blank sheet. Every team member gets a marker.
3. Every team member is asked to write something they didn’t have or something they wished they had to get them closer to the theme or objective.
4. They should also write a possible activity or solution that would have helped if they have one in mind. Each team member has 2 mins to do this. A timer is used.
5. Time runs out. Each team member shifts to a station to their right. They look at what their teammate wrote and add another possible solution. Or if a solution has been posted they agree with, they should +1 the existing solution.
6. If team members cannot think of what to contribute at the next station, there is a station in the middle, maybe at a table or desk. We call this the Liked! station where team members add things they liked in the last iteration that did help them get closer to the objective.)
7. After rotating through all the stations, they end up back in front of their original station.
8. Facilitator gives team 10 mins. to walk around and review the outputs and vote with small post-its on the actions most interesting to them. Each team member gets three votes.
9. Team reviews and discusses the highest voted items.
10. Team commits to implementing those activities or solutions in the next iteration.
Source: No previous source found. Contributed by D. Vaz, Boston-area ScrumMaster.