I wrote recently about transparency being key in software development. I think that another way to move in this general direction is to concentrate on letting the business drive your process sometimes too.
Our customers don’t need to know much about software development in order to help us develop software that adds a ton of value. A close relationship with them allows us to ‘feel their pains’ and let their knowledge drive the delivery process. It also puts some of the owness back on them. Our customers need to ‘feel our pains’ as well. You would be surprised at how helpful they can be when they become more intimately involved with the actual software.
Of course our customers will not have all of the information they need to make great project decisions on their own. As consultants, it is our job to present the relevant information, and make recommendations. As well, we mustn’t be afraid to challenge decisions made by our customers. Always consider, “If that is the answer, what is the question”. Only when communication channels are opened up like this do we start to collectively make really good decisions that ADD VALUE. Our customers must be made aware of these benefits, and only then will they start to view us as trusted advisers, strengthening the cycle further.
In the end, this back and forth collaboration leads to a shared vision, and a more well-rounded team commitment that makes project success much more obtainable.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
0 Responses to “Let the Business Drive Sometimes Too”