A simple addition to every meeting

We have a lot of remote meetings as most of our team work a significant amount of time from home. Face to face meetings are much better for some types of meetings - especially workshops and retrospectives. As the level of expected collaboration increases the more it favours face to face interactions.

We have also been far from optimal in capturing information from meetings and discussions. We have tended to capture the actions fairly well but have failed to adequately capture the “why” - i.e. why were certain decisions made or approaches followed.

We had a recent meeting where we all collaborated on a shared Google doc as the meeting progressed. This worked really well for this particular meeting. We have decided that for nearly all meetings we will create a shared document with an expectation that all participants will update it as it progresses. I would expect there will be a need in each meeting for someone to “own” it so that things don’t fall through the gaps and I would also expect that role to be rotated. Any information captured is better than nothing.

Random Posts

REST API Guidelines

This is here for future reference - a very good set of guidelines for REST APIs.


Read More

Why? Not no

One of my favourite podcasts is Hanselminutes by Scott Hanselman. I have been listening to it probably longer than any other podcast. He recently interviewed Roberta Arcoverde from Stack Overflow. She talked about how the architecture of the Stack Overflow site is very different from most other large sites in that it is a self hosted monolithic application.


Read More

AI breaks the game of hide and seek

This is a really fun video where an AI is given a version of the game of hide and seek and each team has to learn ways to win - either by finding the other team or by not being found.


Read More