Mark Wilson is the product owner for an existing Forward, Inc. flagship product. Mark's product is 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 Product Vision by sales, support, and marketing. It is Mark's job to manage the requirements over a number of releases in the next fiscal year. To manage the requirements using Product Vision, Mark does the following:
Mark does this by examining the current requirements and determining what is to be done and the 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 one feature (Feature A) cannot be done in one release but will have to be spread across multiple releases.
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.
Mark assigns 72 requirements to the six features from the requirements list view.
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. This can be done from the requirements list page by highlighting the requirements and clicking Assign to Release.
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |