240 likes | 328 Views
A CASE FOR PRIORITY. Larry Fellows - Honeywell, Inc. and Ivy Hooks - Compliance Automation Inc. Resources. Requirements. Prioritizing Requirements. Everybody does it - usually too late Need to do it early - when there are options. Typical Project Progress. Percent Complete.
E N D
A CASE FOR PRIORITY Larry Fellows - Honeywell, Inc. and Ivy Hooks - Compliance Automation Inc
Resources Requirements Prioritizing Requirements • Everybody does it - usually too late • Need to do it early - when there are options
Typical Project Progress Percent Complete
Forced Priorities Forced Priority Req A - 3 Req B - 1 Req C - 1 Req D - 3 Req E - 1 Real Priority Req A - 1 Req B - 3 Req C - 1 Req D - 2 Req E - 3 Typical Project Progress Percent Complete
Requirement Reality New absolutely necessary Requirement
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
essential useful desirable Prioritization means Classifying right now a little later someday 1 2 3 non-negotiable negotiable flexible
essential useful desirable Prioritization Example 1 Operate in Windows 95 environment Mouse and hot key for all functions User can define hot keys 1 2 3
non-negotiable negotiable flexible Prioritization Example 2 read data every 4 msec provide data on screen within 1 second of command allow sort data on any parameter 1 2 3
right now a little later someday Prioritization Example 3 single platform networked multiple platforms 1 2 3
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
A B C D Assess Priority Data A A B B C C D D 1 3 2
D B B D B D Resolve Differences Negotiate D B B D Agree B D
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
Resources Requirements Summary Too many Reqt Changing Reqt Unsynced Reqt Limited Time Money Skills 2 3 1 Time