If you can drive out explicitly what the business really needs and wants from its systems, then you have an excellent chance of success. This means capturing the requirements for a system in the right way to ensure that they will provide a sound basis for systems development.
It may sound easy and should be common best practice but most organisations find it hard to make this scenario a reality.
There is often a discrepancy between what is “wanted” by the users; what is “understood” by the systems designers and what is then “developed” by developers. This can result in a gap between what the users want and what goes on to be delivered to them.
To read more, please click here.