By Example: Connect Traditional Requirements to Agile Development

As release planning is wrapping up, Karen Smith, a Forward, Inc. product owner, discovers that the new software service she is planning will be built by an agile development team. The development team has requested the requirements in the form of user stories.

In Product Vision Karen selects the next release of her product and views the requirements included for the release. She selects each requirement individually and creates user stories that express the requirement. In a few cases, there is only one user story for a requirement, but most requirements spawn several user stories.

Because the development team is using CA Agile Vision, each user story that Karen creates shows up in the backlog for the product, tagged to the correct release in CA Agile Vision.

When Karen completes the user story creation exercise, she returns to the Product Vision requirements list view. In the View field, she selects Traceability Matrix and filters the view to show the product and release she is planning. She can then see the traceability from the selected features for the release to the user stories. She can study the traceability to help ensure that all requirements for her release have an associated user story for the development team.