There is a natural reaction for people when faced with a problem to offer solutions. This can be especially true for managers.

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

This excellent article looks at the different types of deadlines and the impact they have. The key point for me, and not something I had seen previously defined, is the distinction between real and artificial deadlines:

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.

This one is just for future reference for me that I may find useful one day - a website full of resources that may be useful for naming things.

We had a meeting recently with 16 people on the video conference call. Due to poor planning and technical issues it took nearly half an hour to decide to postpone the meeting. That is eight man hours wasted - a whole day of work!

We had a discussion at work about "throw away" code. One of our developers was very against developing any code that would be thrown away afterwards. He referred to this as a waste. In my view sometimes the biggest gain can be in developing code that is meant to be thrown away. It can be used to try things and, more importantly, learn things that can shape the code that is kept. This article sums it up much more eloquently than I can.

I have used the "5 whys" approach multiple times to get to the root of some question. This article advocates adding a time dimension to the decision. Not only should we consider why we are doing something, we should also consider why we are doing something at a specific point in time. It also twists this around and suggests we should consider "What is the danger of not doing this right now?" - what would we lose or miss?