Lifecycle of a Product Requirement in RMsis

8,849 views

Published on

This presentation traces the life-cycle of a Requirement in RMsis; in the context of Product Development.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
8,849
On SlideShare
0
From Embeds
0
Number of Embeds
6,696
Actions
Shares
0
Downloads
60
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This presentation provides a short overview of RM sis.
  • Thanks for your time and interest !

    Finally, we want to ensure that we build products, which really solve your problems.

    So, if you have any open issues, please feel free to contact our support team.
  • Lifecycle of a Product Requirement in RMsis

    1. 1. Lifecycle of a Requirement in Product Development Scenario Simplify Requirement Management for JIRA
    2. 2. 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.
    3. 3.  “Customer Need B” is contributed by a customer / team member in “Unplanned Table”.
    4. 4.  The need is elaborated by the contributor / Business Analyst / Product Manager.
    5. 5.  Product Manager identifies this as a valuable input and decides to move it to the Planned Requirements list.
    6. 6.  Product Management Team ◦ defines a “Feature B” and creates dependency on need. ◦ can also define a requirements hierarchy, like  User Need >> Product Function >> Feature
    7. 7.  This Feature is analyzed by the Product Management Team, who does an estimation and assigns values to various attributes.
    8. 8.  The Feature is opened up to a multidimensional team (sales, developers, architects) for comments.  The team’s feedback is incorporated.
    9. 9.  When the evolution of “feature B” stops, it’s current version is committed.
    10. 10.  The feature can be Baselined / Marked for Baseline.
    11. 11.  The feature is assigned to product release “v1.0.0”.
    12. 12.  Development Team starts developing Feature B.  Test Team starts preparing for testing of Feature B.  They discover an issue and log a change request.
    13. 13.  Change request is closed.  Feature is updated and a new version (2) created.  This version is assigned to Release v1.3.0.
    14. 14.  Test Cases are mapped to the requirement.
    15. 15.  Create Test Run(s) and execute
    16. 16.  Issues found during testing are mapped to the requirement.  These issues are tracked to closure.
    17. 17. The “Product Feature B” is released as part of Release 7
    18. 18.  RMsis Home  http://products.optimizory.com/rmsis  RMsis Documents  Latest Release : http://docs.optimizory.com/display/rmsis/RMsis+Documentation+- +Latest+Release  Preview of latest features : http://docs.optimizory.com/display/preview/Home  Functions included in Releases : http://docs.optimizory.com/display/rmsis/Summary+of+RMsis+Releases  RMsis at Atlassian  https://plugins.atlassian.com/plugin/details/30899  RMsis Demo link  http://jira-rmsis.optimizory.com/  Project manager login details  Login: pm1  Password: project123  Team member login details  Login: usr1  Password: user123 See Also ..
    19. 19. Thanks! For further questions or issues, contact support@optimizory.com

    ×