Project Requirements Management Plan 
Requirements Management Plan [Insert Project Name] Last Update: [Insert Date] Template-Requirements Management Plan v2 11-10-04 1 Overview [Provide an overview of the process you plan to employ to manage requirements, what roles will be involved, what the procedures will be and how you will measure the importance and relative weight of each requirement. Objectives [Describe what the objectives of the requirements identification effort will be. What is to be accomplished?] Requirements Scope [Describe what the areas of focus will be for the requirements gathering effort. What business areas are included or excluded?] Process [Describe the process you plan to employ to manage requirements. Will existing meetings/groups be leveraged in order to alleviate meetings? What will the escalation procedures be?] Roles and Responsibilities [Describe who will be involved in the requirements gathering process. What roles and teams are required? Are meetings required? If so, how often?] Rules/Procedures [Describe what rules or procedures the team must follow when logging, managing and assessing requirements. Should all requirements be submitted to the project manager? What mechanism must be used to log requirements?] Requirements Management Plan [Insert Project Name] Last Update: [Insert Date] Template-Requirements Management Plan v2 11-10-04 2 Weight and Ranking Approach [Some alternatives: Criticality (H/M/L); Stability (Volatile, Neutral, Unlikely to Change); Level of Effort (1-3, 4-7, 8-10 weeks or months); Impact (H/M/L); Target Release Deployment (1, 2, 3, 4); Dependency – Number requirements and identify relationships] [Describe the process that will be used to assess the importance and relative weight of each requirement. Who will be involved in this analysis?] Requirements Management Tools [Describe what tools will be used to log requirements. Will word or excel be used? Will a database be used? Where will the logging mechanism be stored? How will version control be handled?] Schedule [Describe what the high level plan will be to gather requirements. What will be discussed when (what will the sequencing be)?[ Approval and Authority to Proceed We approve the project component as described above, and authorize the team to proceed. Name [type or sign name] Title Date Prepared By: