Wasting effort for sake of contract
Nobody wants their work go waste. But most of us would have worked hard to develop something which is definitely not going to be used. It is like building a igloo in Sahara desert. It will just melt away as soon as it is done. Many times there are situations where we have to develop some features in the application which we know are not useful. Customer also knows it cannot be used. But it will be part of the agreed requirements to be developed. To meet the contract you just develop those small things and spend time testing those are working fine.
It sounds funny. But it is very cruel and waste of money. And it happens in most of the projects. No developer likes his work go for waste. They would have got paid for doing it. But to develop a good software it requires more than coding. Only when the team puts their mind and heart together good software gets developed.
If you need good software then do not waste the effort. Wasteful effort is usually result of contracts. Otherwise no person in sane mind will let effort go waste. Contracts mandate all the items in the requirement to be developed. It is not in the interest of the vendor to inform the customer that some features cannot be used as intended. Also customer does not want to pay more for changing the features which are obviously cannot be used as intended. I really do not know how to strike a balance here. But the way it happens does not look good. To maximize the profits vendor designs for everything in the beginning and then develops the code in a very fast pace. This does not allow vendor much scope to do changes. Customer does not want to spend more money on the features which require small changes which were not obvious in the beginning.
Agile SCRUM can solve some of these issues. But it does not work for fixed price contract where requirements, time and money are fixed. It customer and vendor are trusting each other then probably contract can be altered to include scope changes. In this case SCRUM can be used. Trust is not easy come when money is involved.
It sounds funny. But it is very cruel and waste of money. And it happens in most of the projects. No developer likes his work go for waste. They would have got paid for doing it. But to develop a good software it requires more than coding. Only when the team puts their mind and heart together good software gets developed.
If you need good software then do not waste the effort. Wasteful effort is usually result of contracts. Otherwise no person in sane mind will let effort go waste. Contracts mandate all the items in the requirement to be developed. It is not in the interest of the vendor to inform the customer that some features cannot be used as intended. Also customer does not want to pay more for changing the features which are obviously cannot be used as intended. I really do not know how to strike a balance here. But the way it happens does not look good. To maximize the profits vendor designs for everything in the beginning and then develops the code in a very fast pace. This does not allow vendor much scope to do changes. Customer does not want to spend more money on the features which require small changes which were not obvious in the beginning.
Agile SCRUM can solve some of these issues. But it does not work for fixed price contract where requirements, time and money are fixed. It customer and vendor are trusting each other then probably contract can be altered to include scope changes. In this case SCRUM can be used. Trust is not easy come when money is involved.
Comments
Post a Comment