Skip to content

Blogs de Développeurs: Aggrégateur de Blogs d'Informatique sur .NET, Java, PHP, Ruby, Agile, Gestion de Projet

Forum Logiciel

Forum Logiciel : diffusion de connaissance et d’informations sur toutes les activités liées au développement d’applications informatiques en entreprise.

Un Chti café - Jérémy Sevellec
Syndiquer le contenu
Un peu de JEE... un peu d'IT... un peu d'agilité... par Jérémy SEVELLEC
Mis à jour : il y a 12 heures 8 min

A remote retrospective Story

lun, 09/22/2014 - 10:09
a bit of context...I'm working as a remote ScrumMaster since approximatively 2 years with the same team. This team is a full remote team even if most of the times we are doing our sprint planning together IRL. I went with my product owner to setup a new team in Vietnam six months ago. This new team is a bit different because, compared to "mine", all team members of the new team are working together on the same office.
It was quiet challenging because it was planned to make both teams working on the same project and same code base.
Now, 6 months and a product release together later, we decided to make a retrospective with the two teams. The goal was to find out what was working and what was not regarding the collaboration with the two teams.
So I was responsible to setup this retrospective.

the setupI wanted to port my usual local retrospective format based on sticky note with a whiteboard using good/bad/questions/suggestions areas.
My needs : - a good communication tool.- a good virtual white board.

We were used to use Google Hangout so we sticked with it as our communication channel. The only problem is the 10 slots limitation that i will have to deal with.
After some googling, i found that google drawing could be my virtual white board. I got some inspiration from here : http://www.iliokb.com/2013/02/facilitating-retrospectives-with-remote.html

So we did end up with this kind of setup and a drawing is better than a long speech :


Due to the quality of the internet connection of the green team and to the google hangout limitation, we decided to use the green team scrumMaster as a proxy of the other teams member and to use only one google hangout slot for the green team.

The plan
Here is what I did :- the week before : 
  • fix the date, not so easy to find a slot which everybody.

- few days before : 
  • had setup of the google drawing white board, made some try.
  • talked to the product owner to explain how it will work.
  • talked to the other scrumMaster to explain how it will work.

- the day before :
  • sent an email to all participants to remind the goal and scope of the retrospective and to ask them to start to think about that.
  • talked again with the other ScrumMaster. As he acted as team's proxy, we discussed together to try to prepare that as better as we can.
- the D day :
  • verified that everybody was able to join the shared google drawing.
  • just dot it!

Here is the result :


It was fun to hear when everybody was filling the white board "hey, who has stoled my sticky?" ;-)

the retro of the retroBad :
  • Hangout Limitation (max 10 slots)
  • The scrumMaster of the green team was the proxy of the whole teams. It was ok because he was already used to do that for others meeting we already had. Anyway It would have been better to have the whole green team at the same "level"

good :
  • It worked well! Using Google drawing as a virtual shared white board was really successful : simple and efficient.
  • It's now decided to do that one time per release.

Notes : 
  • the virtual retrospective was no longer than the local retrospective i was used to do locally.
  • There was more preparation from me compared to a local retrospective.
  • I had to allocate more time than initially planned to allow everybody to fill the google drawing.



Catégories: Blog Individuel

Partagez la connaissance

Partagez BlogsdeDeveloppeurs.com sur les réseaux sociaux