Managing Requirements › By Example: Plan Feature Requirements Over Releases

By Example: Plan Feature Requirements Over Releases

Mark Wilson is the product owner for an existing Forward, Inc. flagship product. Mark owns a mature software application that is healthy and currently produces a strong revenue stream. However, the product is in need of a revision to keep up with recent advances by competitors.

Mark has a list of requirements that have been entered into CA Product Vision by sales, support, and marketing. He manages the requirements over a number of releases in the next fiscal year. To manage the requirements using CA Product Vision, Mark does the following:

• Determines the product features to be implemented and creates the features in CA Product Vision.

  Mark examines the current requirements to determine which features to implement and in what order. Some requirements can be grouped into one feature. Mark determines that six product features are required (Features A, B, C, D, E and F). He also determines that all of the requirements for Feature A cannot be completed in one release, and must be spread across multiple releases.

• Determines the number of releases required and creates the releases in CA Product Vision.

  Mark determines that three releases are required to implement the features and requirements he has listed. The releases are Spring 2011, Summer 2011, and Winter 2011.

• Assigns requirements to the features.

  Mark assigns 72 requirements to the six features from the requirements list view.

• Assigns the requirements of Feature A across multiple releases.

  Mark assigns the following requirements from Feature A to the individual releases: five to the Spring 2011 release, seven to the Summer 2011 release, and three to the Winter 2011 release. From the requirements list page, he makes the assignments by highlighting the requirements and clicking Assign to Release.

More information:

About Requirements

Requirement Hierarchies