work

It is very easy for your work week to become a random collection of meetings - all with different attendees and different agendas. For developers in particular this can cause a huge hit on productivity as their day becomes disjointed and they are unable to stay focussed for the longer periods they need for their work.

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.

On most projects there is a tendency for someone involved to become the "expert" in one or more areas. As they become comfortable and more knowledgeable in an area they will naturally gravitate to picking up tasks related to it. The need to deliver as quickly as possible can also drive this as the person who knows most is likely to be the person who can do the work quickest.

When someone leaves a company there are two sides to it.

We have just completed a two week exercise with the whole development team to identify, design and estimate the next phase of work. It started as an organic process as we found the best way to do this and then developed into a repeatable process for the latter functionality.