10 Steps to Better Requirements Larry Fellows Compliance Automation, Inc. Standish Group Survey - 1995 17% On Time & On Budget 33% Cancelled (Cost $81B) 50% Challenged (Cost $59B) Average Challenged Project: 189% Over Budget 222% Behind Schedule
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Compliance Automation, Inc.
17%On Time &On Budget
Average Challenged Project:
189% Over Budget
222% Behind Schedule
Only 61% of originally specified features delivered.
34%On Time &On Budget
On Time On Budget Required Functions Right Quality
DevelopersStep 2 – Identify the Stakeholders
Shared KnowledgeStakeholder Knowledge
Shared KnowledgeCreate Common Vision
Higher Level Requirements
Existing systems & processes
command & data
keyboardStep 5 – Define External Interfaces
People who write bad requirements
should not be surprised
when they get bad products
But they always are.