Copyright 1998 Honeywell Inc. And Ivy Hooks All rights reserved A CASE FOR PRIORITY Larry Fellows - Honeywell, Inc. and Ivy Hooks - Compliance Automation

Copyright 1998 Honeywell Inc. And Ivy HooksAll rights reserved

A CASE FOR PRIORITY

Larry Fellows - Honeywell, Inc.

and

Ivy Hooks - Compliance Automation Inc

2 Copyright 1998 Honeywell Inc. And Ivy HooksAll rights reserved

Prioritizing Requirements

Everybody does it - usually too late Need to do it early - when there are options

Resources

Requirements


Typical Project Progress

0 20 40 60 80 100

Req A

Req B

Req C

Req D

Req E

Percent Complete


Forced Priorities

0 20 40 60 80 100

Req A

Req B

Req C

Req D

Req E

Percent Complete

Real Priority

Req A - 1

Req B - 3

Req C - 1

Req D - 2

Req E - 3

Forced Priority

Req A - 3

Req B - 1

Req C - 1

Req D - 3

Req E - 1

Typical Project Progress


Requirement Reality

New absolutely necessary Requirement


Out of Sync Development

0% 50% 100%

Req A

Req B

Req C

Req D

Req F

Req G

Req

uir

emen

ts

% Complete

MOD 1

MOD 2


Options versus Time

0

20

40

60

80

100

% Options Available

Req Design Dev Start DevComp

Phase


Benefits of Prioritizing Early

Have real options Ensures that effort and resources are focused

on the essential requirements Useful when resolving requirement conflicts Useful when planning phased deliveries Required to determine which requirements

can be delayed or deleted


What is Prioritization?


Prioritization means Classifying

essential

useful

desirable

non-negotiable

negotiable

flexible

right now

a little later

someday

1

2

3


Prioritization Example 1

essential

useful

desirable

1

2

3

Operate in Windows 95 environment

Mouse and hot key for all functions

User can define hot keys



non-negotiable

negotiable

flexible

1

2

3

read data every 4 msec

provide data on screen within 1 second of command

allow sort data on any parameter



right now

a little later

someday

1

2

3

single platform

networked

multiple platforms


How to determine priorities


Prioritization Steps

Gather Prioritization Data

Assess Prioritization Data

Resolve Differences


Gather Prioritization Data

Sell prioritization benefits

Define the 1, 2, 3’s

Let stakeholders classify requirements

Do internal classification


Define 1, 2, 3’s

1

2

3

essential

useful

desirable


Problem

Need a new thermostat Honeywell has family of thermostats with

different features Thermostats labeled good, better, best Chose thermostat that meets our needs at a

price we are willing to pay


Thermostat Features Control heating to temperature degrees Control cooling to temperature degrees Programmable for weekday, Saturday, and Sunday Four temperature settings daily Hold at temperature (override program) Fan control run continuously or auto Automatic switch between heat and air conditioning Clock display Display settings Battery backup Low battery indicator


Assess Priority Data

1

2

3

A

B

C

D

A

B

C

D

A

B

C

D


Resolve Differences

D

D

D

B

B

B

D

D

D

B

B

B

Negotiate

Agree


Prioritization Considerations

Must involve all stakeholders All requirements cannot be essential Try to get agreement on prioritization

informally As analysis and design evolve, review

and adjust priorities


QFD

large and complex

many customers/users

very big differences in priorities from different viewpoints


Summary

Resources

Requirements

Limited

Time

Money

Skills

Too many Reqt

Changing Reqt

Unsynced Reqt

1 2 3

Time

Documents

Copyright 1998 Honeywell Inc. And Ivy Hooks All rights reserved A CASE FOR PRIORITY Larry Fellows - Honeywell, Inc. and Ivy Hooks - Compliance Automation