Readers/Web/Team/Retrospectives/2014-03-17

The mobile team ran a "One word retrospective". Moiz originally expressed doubt and there were suggestions that Jon was being a bit of a hippy but Jon persevered with carrying out the one word iteration retrospective. Every participant picked a word that captured the iteration for them. We discussed these words and then used these as the basis for a conversation to identify things the team should start doing, continue doing, stop doing, we also took time to have shout outs for people that had helped out in the last iteration.

This seems to have been a fun way of leading the conversation and we got some good action points out of this:

• [Moiz] Explore user testing strategy
• [Team] The team from now on will for the next iteration "Squirrel Monkey", will test out a more disciplined approach to code review. No code should be submitted if there are more than 5 patches in MobileFrontend with positive or zero votes. The team should drop working on new patches until this code review is done.
• [Kenan] Explore ways to improve cross team dependencies e.g. with VE

(Informally Agreed) to hold hands at the end of each retrospective and go ummmmmmm (this happened)

Etherpad notes

On Etherpad

The iteration in one word

In a single word describe this iteration.

The words:
pleading
communication
docieranie (wearing in)
movement
cooperation
stutttt-t-t-t-tter
VE

From these words, we started to identify things that we should start/stop/continue doing and thanked people that had made the iteration a positive one.

The discussion

'''Things we should start doing'''
Find a way to get dependencies for mobile from the VE - get more efficient when there are cross team dependencies
Find ways to user test our designs better (not usertesting.com)
Work on other things than VE to keep things interesting / diverse
Include Max in VisualEditor work by adding performance tasks related to VisualEditor
Start including Max's Minifier work and other work on Mingle
Explore ways of working in a similar consistent way so that people get stuff code reviewed when they need it

'''Things we should stop doing'''
Unnecessary VE meetings

'''Things we should continue doing'''
Talk to the VE team as often as possible
Having Roan in meetings
Meeting with James and VE team on regular basis - helps structure work better on technical viewpoint

'''Shoutouts'''
Aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Kowabunga!
Kaldari shouted out to pretty much all the team

Actions

[Moiz] Explore user testing strategy
[Team] if ( there are more than 5 patches in MobileFrontend with positive or zero votes then we should code review)
[Kenan] Explore a way to get better expectations of when things were done
(Informally Agreed) hold hands at the end of each iteration