Robert MacLean
11 June 2015
With an agile team you should meet daily for a quick meeting. Normally that takes the form of each person answering a three question status update (What did I achieve, what will I achieve, what is blocking me). For a team working together it means these steps:
- Team arrives at the shared team board
- Team goes round and gives status update
- Team goes back to work
Just because your team is distributed doesn’t mean this shouldn’t happen – it just means that you’ll find a few extra steps:
- Team members who work together go to booked meeting room (you need a meeting room so those remote can hear over the normal work environment noise)
- Be surprised to find some one in the room
- Explain that you booked the room
- Wait for them to leave the room
- Connect the projector
- Realise you left your microphone in your laptop bag, return to desk get it, return to meeting room
- Plug it in
- Open the digital scrum board
- Start meeting software and join meeting
- See one remote team member is already there – apologise for being late
- wait for response
- wait for response
- realise they can’t hear you.
- Both the remote team member and yourself try to figure out what is not working
- Figure out that there is a mute hardware button that today (and today only) is turned itself on
- Try again – success, they can hear you
- Wait for the product owner to join.
- Give up waiting and kick off meeting (everyone is seated now cause no ones legs last that long)
- Go around the team and give status update
- Product owner joins during second last team members status update
- Product owner starts sharing a bunch of bugs and task updates that someone else is now capturing live
- Finish status updates
- Team decides to use this time that we are all here to discuss technical info around the new stuff from the product owner
- Product owner is late for meeting and has to disconnect
- Someone walks into the meeting room and asks if this is the meeting for organising the year end party
- silence
- No one answers
- silence
- Scrum master answers
- Team discusses technical issues. Half are marked as needing more info and will be discussed with product owner in tomorrows meeting
- Call ends
- Team goes to get coffee (they need it) and says how glad they are using agile cause they save so much time with less meetings
- two hours later
- other team member joins call alone because the time zone he is in changed to daylight savings today
Repeat daily