10 steps to better requirements
Download
Skip this Video
Download Presentation
10 Steps to Better Requirements

Loading in 2 Seconds...

play fullscreen
1 / 18

10 Steps to Better Requirements - PowerPoint PPT Presentation


  • 420 Views
  • Uploaded on

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

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about '10 Steps to Better Requirements' - Gabriel


An Image/Link below is provided (as is) to download presentation

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.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
10 steps to better requirements
10 Steps to Better Requirements

Larry Fellows

Compliance Automation, Inc.

standish group survey 1995
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

Only 61% of originally specified features delivered.

standish group survey 2002
Standish Group Survey - 2002

34%On Time &On Budget

15%Cancelled(Cost $81B)

51%Challenged(Cost $59B)

a winning product
A Winning Product

On Time On Budget Required Functions Right Quality

step 2 identify the stakeholders
Customer

Engineering

Designers

System

Engineering

Software

Marketing

Logistics

Service

Operations

Manufacturing

Testing

Reliability

Developers

Step 2 – Identify the Stakeholders
stakeholder knowledge
Common Knowledge

Unique Knowledge

Shared Knowledge

Stakeholder Knowledge
create common vision
Common Knowledge

Unique Knowledge

Shared Knowledge

Create Common Vision
step 3 recognize the drivers
Step 3 – Recognize the Drivers

Higher Level Requirements

Cost

Regulations

Specification

Standards

Existing systems & processes

User

expectations

Schedule

step 5 define external interfaces
test hardware

other software

command & data

status

command

other hardware

YourSystem

display

database

Power

Physical

keyboard

Step 5 – Define External Interfaces
no surprises
No Surprises

People who write bad requirements

should not be surprised

when they get bad products

But they always are.

Ivy Hooks

ad