Child pages
  • Requirement Cycle for a Project Manager in RMsis
Skip to end of metadata
Go to start of metadata



This presentation covers

  1. Objective
    1. How a Project Manager manages the lifecycle of a Requirement in a typical project.
  2. Assumptions
    1. Project Manager is the owner of Requirements in this project. The scenario may be different in Product Companies, where usually a Product Manager will own the Requirements set.
    2. Unplanned table is shared with customers.
  3. Requirement creation
    1. User enters data in the UnPlanned Table
  4. Requirement Analysis
    1. PM / Analyst analyzes the data
    2. Data is moved to Planned Table and is analyzed further.
    3. Requirement is reviewed and agreed upon.
  5. Commit
  6. Baseline
  7. Prepare for execution
    1. Create execution tasks.
    2. Create Test Cases.
    3. Look at Traceability view.
  8. Monitor execution in Reverse Traceability view for a specific release.
  9. Closure
    1. Task is closed.
    2. Test cases have passed.
    3. Release done.
    4. Requirement should be closed.


1 Comment

  1. The position of Planned / Unplanned Requirements and their table structure will slightly change with RMsis 1.8.0 release.