ScatterSpoke

I know the best way to work with people is face to face and in the same building. Indeed, the best way will be that all team members will be located in the same floor. However, we have to accept that working in big companies that ideal scenario is imposible to see there.

Retrospectives

The best moment to check how well was our performance is in the Retrospectives. The Scrum Master or any facilitator (for instance in Kanban) organise this great ceremony. It means, he got a meeting room with a board (or a big paper to post the sticky notes), sticky notes and sharpies  and with all team members go ahead to review the last Sprint (in case you are doing Scrum).

As I mentioned before many times you (as Scrum Master or member in a Scrum team) you have to deal with distributed team members because of that you need to use tool to conduct the Retrospective.

ScatterSpoke logo

 

 

 

 

 

 

Thanks to a colleague: Colleen Johnson – Practice Director, Lean/Agile Transformation at ImagineX Consulting I found ScatterSpoke

The following material was extracted by ScatterSpoke

How it works

Rethink how you retro

Do you remember what you had for lunch last Tuesday? Exactly. Most of us spend our retrospectives focusing only on what happened in the last few days or as far back as our memory allows. We forgot key events and lose track valuable learning opportunities. ScatterSpoke’s got your back. Add cards when they happen, view past retrospectives, and connect commonly occurring themes. ScatterSpoke can provide your with team the data and trends to reflect, review and grow beyond the whiteboard and stickies. Stop spending time trying to remembering what you did yesterday. ScatterSpoke takes the remembering out of your retrospective so you and your team can truly focus on continuously improving.

Balanced input for max output

We typically spend a lot of time trying to vary the format of our retrospectives to keep things fresh and exciting. While changing up the questions or way we gather data can certainly keep the team more engaged, we don’t spend enough energy focusing on the content and types of cards we are posting. We break these down into four easy types: facts, events, kudos and observations. It’s important to get a balance of each of these four so you establish clear picture of your team’s work and create a safe environment to be open.

Facts

A team focus on expressing statements with facts will go a long way to improving the outcome of a team’s retrospectives. Facts remove bias and emotion while giving us something measurable to change or improve upon. This can include things like velocity, throughput, and cycle time. It can be a great idea to keep track of the same facts and stats at each retrospective to build a story of your improvements over time.

Events

Making notes of events that occurred during the focus of the retrospective on what happened to create shared understandings. Recalling key events can also help set the context for observations and facts. This might include things like a teammate out on vacation, a build that failed, or a production outage. Discussing events can also help others remember things that may not have been at the top of their mind.

Kudos

Including praise in your retrospective opens up communication and keeps the team positive. This is especially important when the conversation may be heated or contentious. Kudos can be simple things like appreciation for on-call coverage, a thank you for doing a code review, or gratitude for patience while pairing. Showing recognition of each other’s effort goes a long way in creating a safe space for the team to express themselves.

Observations

Something that you noticed, felt, or experienced would be considered an observation. These are editorial in nature and often include statements of opinion and perspective. Examples might include having a different point of view on backlog priorities or sentiments of not having an equal voice in story pointing. It is important for the team to have an opportunity to express their feelings and be heard. ”

To conclude, you need to give a chance to ScatterSpoke for your distributed agile team retrospectives and let me know what was the result of your experience!!!

 

Share:
Mario Lucero

Mario Lucero

I am all about helping companies to adopt agile as methodology in Chile. Why? I believe many organizations think that agile is not for Chilean companies because of Chilean culture is totally different from i.e. USA culture but I worked with Chilean professionals who after using agile realized it is feasible to implement it. Agile works in small and large projects and there are many evidences which demonstrate this.

Leave a Reply

CommentLuv badge