first place, and to forecast that point at which benefits would begin to outweigh the costs of the effort.
Want to Learn More?
- David Gelperin, Maybe We Shouldn't Write Requirements , StickyMinds Original Article, October 2002. A brief discussion—and lots of reader comments—on how best to record and manage requirements: paper documents vs. spreadsheets vs. database, etc.
- Jeffery E. Payne, Quality Meets the CEO: How to Get Management Buy-in , STQE magazine, May/June 1999.
- David F. Rico, How to Estimate ROI for Inspections, PSPsm, TSPsm, SW-CMM®, ISO 9000, and CMMIsm , StickyMinds, Sept 2002.
- Ed Weller, Calculating the Economics of Inspections , StickyMinds, Jan 2002.
- Dean Leffingwell, Calculating Your Return on Investment from More Effective Requirements Management .
Tags:
About the author
Richard Denney is the author of Succeeding with Use Cases: Working Smart to Deliver Quality, part of Addison-Wesley's Object-Technology Series. Richard has 25 plus years experience in software development and process management. He's also has experience as a principal in process improvements for some of the oil industry's largest software solutions suppliers: the Texas State Office of the Attorney General, and several Fortune 500 companies as a consulting affiliate of TeraQuest Metrics (software process component of Borland) and SAIC.
User Comments
Your ROI assumptions include the cases in which requirements are not written down and are not circulated between the stakeholders. <br/><br/><br/><br/>What do you think an RMS ROI will be in a company that is using using ms-word/excel, e-mail, and document management system to specify, distribute, store, and track requirements?<br/><br/><br/><br/>Moshe Suberri