home

The Seinfeld Approach to Requirements

by Barbara Davis

Software industry stats clearly show there is an urgent need for dramatic and immediate improvement to the way we develop our products.

Only 16.1% of software and technical projects are successful, and that of the successful 16.1%, only 20% of the implemented features are used all the time and 40% are never used at all! That means that only
1.24% of all proposed features are actually implemented and used! Further, 2.48% of all proposed features are implemented and never used!

The single-most common reason for these alarming statistics is requirements. A lack of practice formalization and holistic view of the causes and effects of failure, have led to the shotgun approach to
requirements. Periodic successes with this approach have, in turn led Business Analysts to believe that the fault lies elsewhere in the process.

AttachmentSize
The Seinfeld Approach to Requirements.pdf141.35 KB

Article Sponsored By

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
sources by bdavis@e2consul...
Moving Target by bdavis@e2consul...
Standish Report -CHAOS by smojumder

    Sponsored Announcements & Special Offers

© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group