Question

Considering the reasons for systems projects, is it possible to have too much of a good thing? Can service ever be too good? Can performance be too strong? Can there ever be too much information? Can controls be too strong? Can costs be reduced too much? Why or why not? If so, where should a line be drawn?

Answer 1

Too much of anything will increase on too much of the costs, nothing comes for free of cost.

Anything that may be good for one may not be god enough for another, there is no limit on what is good and too good.

Thus, measurement of qualities or characteristics is based n some criteria that match or does not match.

Services asked for during project requirements phase are the basics to be fulfilled, once these are fulfilled successfully, the project may be considered good enough but there may be some additional features added upon the project,which may be qualified as too good, or even the customer may not be happy with that, humans never have an end to their desire.

Too much of information may lead to too much of handling issues, and too much of problems in organizing and understanding which information to be used and which to be discarded.

Cost can not be reduced too much as long as the project is being build up by a professional team, working and providing their effort for their salary.

Performance of a project may be increased to a near too much amount, but it may depend largely on the hardware system, which may result to a failure at any time.

Controls are dependent on performance and hardware as well.

Thus each specific feature is dependent on some other characteristic of the project, making something good of too much may not be really too much for someone else.

And increasing the features increases the costs as well.

Thus every thing is interrelated on one another withing a project development procedure and so it is not really feasible to improve good things up to an extent to call it as 'too much'.

Thank you

Please comment for any issues