10 steps to better requirements
Download
1 / 18

10 Steps to Better Requirements - PowerPoint PPT Presentation


  • 420 Views
  • Updated 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

Related searches for 10 Steps to Better Requirements

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 l.jpg
10 Steps to Better Requirements

Larry Fellows

Compliance Automation, Inc.


Standish group survey 1995 l.jpg
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 l.jpg
Standish Group Survey - 2002

34%On Time &On Budget

15%Cancelled(Cost $81B)

51%Challenged(Cost $59B)


A winning product l.jpg
A Winning Product

On Time On Budget Required Functions Right Quality



Step 2 identify the stakeholders l.jpg

Customer

Engineering

Designers

System

Engineering

Software

Marketing

Logistics

Service

Operations

Manufacturing

Testing

Reliability

Developers

Step 2 – Identify the Stakeholders


Stakeholder knowledge l.jpg

Common Knowledge

Unique Knowledge

Shared Knowledge

Stakeholder Knowledge


Create common vision l.jpg

Common Knowledge

Unique Knowledge

Shared Knowledge

Create Common Vision


Step 3 recognize the drivers l.jpg
Step 3 – Recognize the Drivers

Higher Level Requirements

Cost

Regulations

Specification

Standards

Existing systems & processes

User

expectations

Schedule



Step 5 define external interfaces l.jpg

test hardware

other software

command & data

status

command

other hardware

YourSystem

display

database

Power

Physical

keyboard

Step 5 – Define External Interfaces








No surprises l.jpg
No Surprises

People who write bad requirements

should not be surprised

when they get bad products

But they always are.

Ivy Hooks


ad