Transcription of First Things First: Prioritizing Requirements 1
{{id}} {{{paragraph}}}
Copyright 1999 by Karl E. WiegersFirst Things First : Prioritizing Requirements1 Karl E. WiegersProcess are never thrilled to find out they can t get all the features they want in of a new software product (at least, not if they want the features to work). However, if thedevelopment team cannot deliver every requirement by the scheduled initial delivery date, theproject stakeholders must agree on which subset to implement First . Any project with resourcelimitations has to establish the relative priorities of the requested features, use cases, or functionalrequirements. Prioritization helps the project manager resolve conflicts, plan for staged deliveries,and make the necessary trade-off Prioritize Requirements ?
Copyright © 1999 by Karl E. Wiegers First Things First: Prioritizing Requirements 1 Karl E. Wiegers Process Impact www.processimpact.com Customers are never thrilled to find out they can’t get all the features they want in release
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}
Karl Wiegers Describes 10 Requirements Traps, Requirements, Writing a Requirements Document, BY ORDER OF THE SECRETARY AIR FORCE, By order of the secretary, Business Value of Agile Development, AIR FORCE, Handbook of Occupational Groups, 1 HANDBOOK OF OCCUPATIONAL GROUPS, IMMUNIZATION SUPPLY CHAIN, Immunization Supply Chain and Logistics