Something we've been trying to cut down on at work is the amount of context switching that the development team have to do. Rather than working on multiple projects at once, we've been trying to get them onto one project that they can concentrate on all day.
The reason we do this is we think there's a cognitive cost of changing what you're doing. It's obvious, and it's not a new observation:
A man commonly saunters a little in turning his hand from one sort of employment to another. When he first begins the new work, he is seldom very keen and hearty; his mind, as they say, does not go to it, and for some time he rather trifles than applies to good purpose. The habit of sauntering, and of indolent careless application, which is naturally, or rather necessarily, acquired by every country workman who is obliged to change his work and his tools every half hour, and to apply his hand in twenty different ways almost every day of his life, renders him almost always slothful and lazy, and incapable of any vigorous application, even on the most pressing occasions. Independent, therefore, of his deficiency in point of dexterity, this cause alone must always reduce considerably the quantity of work which he is capable of performing.
Adam Smith - The Wealth of Nations (1776)
It amazes me when people say "Can't you just work on both things at once?" but it's very common in some workplaces. I guess some things take a few centuries to sink in.
1.
Imagine doing the washing up then half way through someone asks you to do the hoovering.
You dry your hands, get the hoover out, plug it it in.
Then half way through hoovering someone asks you to do the ironing.
You unplug the hoover and put it away, get the iron out wait for it to heat up.
By this time the water in the washing up has gone cold and you need to run the water again.
In any other context people can understand the need for finishing a task and only doing the most urgent thing at any one time.
Perhaps because non-technical people don't understand the amount of mental effort it takes to switch between projects they are unable to appreciate that the same applies to web development.
A solid development process and a good project / product manager should shield the dev team from most of these interruptions.
Russell
9th July 2010, 13:11