managing lifecycle of a requirement with rmsis 1.2.x

17
RMsis 1.2.x Lifecycle of a Requirement in Product Development Scenario

Upload: optimizory-technologies-pvt-ltd

Post on 06-May-2015

4.607 views

Category:

Technology


0 download

DESCRIPTION

In this presentation, we describe the lifecycle of a requirement, from idea to release !

TRANSCRIPT

Page 1: Managing lifecycle of a requirement with RMsis 1.2.x

RMsis 1.2.x

Lifecycle of a Requirement in Product Development Scenario

Page 2: Managing lifecycle of a requirement with RMsis 1.2.x

Problem Statement To walk through the lifecycle of a specific

Requirement in a product development scenario.

A need is contributed by customer, eventually leading to inclusion as feature.

1. Need is specified in unplanned table.2. Requirement is included in the planned set, analyzed

and assigned to a release.3. Requirement is evolved and baselined.4. Requirement goes through a change request.5. It is implemented and tested.6. Forward traceability is established.7. Issues are associated and tracked to closure.

Page 3: Managing lifecycle of a requirement with RMsis 1.2.x

“Customer Need B” is contributed by a customer / team member in “Unplanned Table”.

Page 4: Managing lifecycle of a requirement with RMsis 1.2.x

The need is elaborated by the contributor / Business Analyst / Product Manager.

Page 5: Managing lifecycle of a requirement with RMsis 1.2.x

Product Manager identifies this as a valuable input and decides to move it to the Planned Requirements list.

Page 6: Managing lifecycle of a requirement with RMsis 1.2.x

Product Management Team◦defines a “Feature B” and creates dependency on need.◦can also define a requirements hierarchy, like

User Need >> Product Function >> Feature

Page 7: Managing lifecycle of a requirement with RMsis 1.2.x

This Feature is analyzed by the Product Management Team, who does an estimation and assigns values to various attributes.

Page 8: Managing lifecycle of a requirement with RMsis 1.2.x

The Feature is opened up to a multidimensional team (sales, developers, architects) for comments.

The team’s feedback is incorporated.

Page 9: Managing lifecycle of a requirement with RMsis 1.2.x

When the evolution of “feature B” stops, it’s current version is committed.

Page 10: Managing lifecycle of a requirement with RMsis 1.2.x

The feature can be Baselined / Marked for Baseline.

Page 11: Managing lifecycle of a requirement with RMsis 1.2.x

The feature is assigned to product “Release 7”.

Page 12: Managing lifecycle of a requirement with RMsis 1.2.x

Development Team starts developing Feature B. Test Team starts preparing for testing of Feature B. They discover an issue and log a change request.

Page 13: Managing lifecycle of a requirement with RMsis 1.2.x

Change request is closed. Feature is updated and a new version (2) created. This version is assigned to Release 7.

Page 14: Managing lifecycle of a requirement with RMsis 1.2.x

Test Cases are mapped to the requirement.

Page 15: Managing lifecycle of a requirement with RMsis 1.2.x

Issues found during testing are mapped to the requirement.

These issues are tracked to closure.

Page 16: Managing lifecycle of a requirement with RMsis 1.2.x

The “Product Feature B” is released as part of

Release 7

Page 17: Managing lifecycle of a requirement with RMsis 1.2.x

Thanks!

For details, please visithttp://products.optimizory.com/rmsis

For further questions or issues, [email protected]