« Leadership is a State of Mind | Main | The Gordon Pask Award »

03 August 2010


Feed You can follow this conversation by subscribing to the comment feed for this post.

Pawel Brodzinski

I'd say that the factor which is most often underrated is intimacy. We tend to keep it professional and professional only and we lose a chance to build trust relationship within a team. This is a pity since basing on trust you can skip a lot of formal procedures making work efficient, yet still fairly pleasurable for the people.

On the other hand, while I agree that work shouldn't be always done by experts, in some cases I find it hard to have done any job by any member of the team. Sure, we employ collective code ownership to share knowledge about whole code base among developers, but I don't expect they would take product management from me or would become expert system administrators. And that's what cross-functional teams are about too.

We try to help each other whenever we see bottlenecks but on a typical situation I prefer our developers not to start functional testing as that's not very effective way of using their time. Besides, odds are they won't become star testers no matter how hard they try.

But then we come back to trust again. We trust that a tester would do his job perfectly. We trust a developer would fix bugs using he mind and not knees to proposed best solution, etc. If the trust is the problem we start shooting at each other using bug tracker as a gun and wasting time writing lengthy comments just to show we right and the other side is not. Then, it's time to come back to "I" factor.

The comments to this entry are closed.