When the time comes to determine which requirements are to be implemented in the next release, you can create rules to help you decide which requirements to implement and which to postpone for a future release. For example, you may decide that in the first release, you will implement only those requirements evaluated as being high risk and high difficulty. If you have assigned risk and difficulty attribute values to each requirement, you can then easily sort all requirements by these attribute values.

One way to organize requirements is by priority. You might decide to assign high priority to certain requirements that are important to the customer. You can then sort through your requirements and address those with high priority early in your project.

Consider these factors when you set priorities for requirements:

You should also examine your schedule. Do you have time to complete all of your high priorities? Setting realistic expectations at this stage will help your team stay on schedule and close to budget.

Page 6 of 8    Main Menu Previous Page Next Page