Pierson’s customers have found that they are able to capture 93 – 95% of the business requirements functionality by using a collaborative requirements method and by creating and validating paper prototypes with the business community.
Pierson has conducted studies with Hallmark, Amica Insurance, CarMax, Staples and the U.S. Department of Energy. The following time and cost savings were found:
- 25 – 50% of time saved for requirements gathering
- Use of a collaborative requirements approach saved 25% to 33% of time over the entire project or 3 – 4 months out of a year long project.
Pierson’s customers have all found that it is not just a cost savings but also getting it right the first time which decreases redesign. Redesign is very costly for companies. Pierson’s philosophy is also to strive for consensus based requirements in order to provide a key measure of success for better customer satisfaction.
You may find this informative also. http://www.it-financeconnection.com/enterprise-systems/roi-success-through-business-anaysis/
This is very interesting.
I have found that faulty or incomplete requirements are the reason for most project failures. It is the first thing I address when taking over a troubled project.
This is true for our organization.
Website is interesting and informative.