The lawyers who say NO!

Hi guys,

Recently I’ve became so busy that I totally forgot about my blog. Even when I try to do everything perfectly, something comes up and ruins my plans.
Well, that’s the nature of our jobs anyway. Nothing is predictable.

A while ago I was reading an article at Dr.Dobb’s Journal from Scott Ambler (see his profile at IBM) here. I suggest you guys to read it as well if you haven’t yet.

It actually points out a hidden impediment which is an obstacle to many of software development teams that try to exercise IID (Iterative and Incremental Development); the lawyers who say NO!
Before I continue I must remind you that what you read here is my personal opinion and you might find it incorrect or disagree with me. Well, that’s what the comments are for. I believe as a reader, it’s your obligation to share your opinion with the writer and other fellow readers.

“Lawyers who say NO!” is a metaphor for those people who approve the project’s funding which can be the customer itself, those who audit project’s compliance with what is planed business-wise, and those real lawyers who make the contract with customers. The message this article is trying to send is no matter how much you as a software specialist try to fix your process and development method to mitigate the risks and achieve the goals, there will be non-technical obstacles that can make your efforts worthless. Unless everybody involved in the project have same understanding of what has to be done and how (of course with their own point of view and different levels of details).

Customers and project investors need to understand the fact that that making a friendly and close cooperation with the development team is the key role they can play in the success of the project and eventually get a better ROI (return of investment) from the result product.
In addition having a right governance process that can be aligned with the development methodology and resolve the potential clashes between technical and business views is crucial. For those who don’t know what Governance means, because business success rests on software success, business executives need to understand how their investments in information technology and software development are paying off. They demand visibility and accountability. That's where the governance shows up.

So as you can see delivering a successful project that eventually can make profit for the customer needs a right collaboration process in place. Note that this is in addition to having a suitable Development Methodology and Governance Process.

I guess that's it. That was the message I was trying to send (ok, simplifying what Scott Ambler was trying to say mixed with my own opinion). That was what I understood. Let me know what do you think.