One option I am thinking about is to pay for a fas...

2010-03-06T23:27:59.709Z

One option I am thinking about is to pay for a fast dsl/fibre connection and host my own server vs paying someone a monthly charge for hosting.

Hi Milan: It’s nice to see you back. I am a real ...

2010-02-26T09:13:43.957Z

Hi Milan:

It’s nice to see you back. I am a real fan of your blogs.

Requirements should be based on the business / service benefits and hence they could be "barely sufficient" if the benefits can be met. I will quote an example but the issue needs to be addressed at a more fundamental level.

However, almost all the time they are not. The requirements are quite often a mash-up of business benefits and the "wish" of the originator. There has to be ways that can capture requirements in such a way that the business problems are "first" addressed and then address the wish list.

The "wish" factors are important from the customer experience perspective but for the techies, they are not as important as the cost, quality, time, performance, scalability and other goodness factors.

Just to cite an example from the automobile industry. The design, engineering and assembly are important for the design and tech team. Those should be decided by the design and engineering community after studying what the market wants (Not the customer). They are the best to do that job. Then comes the configuration bit - color, upholstery, music system etc. Those are similar to the "wish list". Those can be decided by the customer experience or sales teams along with the customer.

Often, in software development, it is very difficult to differentiate between the real requirements and the "wish" and hence teams land up with a lot in their plate.

MJ

Comments on knownbugs: barely sufficient

One option I am thinking about is to pay for a fas...

Hi Milan: It’s nice to see you back. I am a real ...