Development Team Leadership : First Steps Part 3

Raising the Alarm

I’m a big believer in the proverb:

A stitch in time saves nine

This holds true across so many scenarios in software development, perhaps most notably if your project is veering off course the worst thing you can do is sit on the problem and not tell those around you.

If you have a problem, talk about it, another quote:

A problem shared is a problem halved

If you’ve made a mistake, be honest and get on with it.  If you try to cover it up, chances are:

1.  you won’t be able to;
2. it will become infinitely worse.

Let those around you know so that something can be done about your problem. Software projects often get a bad rap for coming in late, or worse still, not at all (http://blog.codinghorror.com/the-long-dismal-history-of-software-project-failure/), you can bet at some point an alarm wasn’t raised when it should have been.

Be free with Advice

Giving advice where due will breed a culture of sharing knowledge and encourage those around you not to be afraid to ask questions.  The reality is that you don’t know everything, and at some point you will need help.  If you’ve given it, you’ll get it back with dividends.

Gaining Trust – Understanding the Business

Understanding the business you are working in/with will help to build trust between you and your clients.  If you can recommend on not only technical outcomes but, through understanding or prior experience recommend solutions to promote further efficiencies within existing practices then you will be appreciated greatly.

Building trust with clients is extremely important and understanding their needs will ease this.

If you have the confidence to question requirements and suggest a better solution to an issue that’s being tabled, and your client has the trust in you to listen; everyone’s a winner.