<p> <enter sponsor dept/bureau name></p><p><Project Name></p><p>Requirements Management Plan <enter sponsor dept or bureau name></p><p>Document Instructions The template should include these instructions. After the document author has read these instructions, they can be deleted. This section is not included in the Table of Contents. </p><p><This document template contains directions for use or sample entries. These directions are enclosed in brackets (< >) and are italicized. They are included to help you fill out the form. As you complete the form, delete these instructions. </p><p>Please follow this document naming convention to facilitate document search and retrieval:</p><p><project code (if appropriate)> <project name (abbreviated)> <document name (abbreviated)> <version (if appropriate)></p><p>All documents should be posted to the appropriate project folder in SharePoint. ></p><p>Document History</p><p><The document history is a log of changes that are made to the document, who made the changes, and when. For example, the initial creation of the document may contain the following: Version 0.1, Date 1/1/2004, Author Charlie Brown, Status Initial creation. Subsequent updates to the document will be Version 0.2, 0.3, etc. The first published version of the document should be Version 1.0.></p><p>Versio Date Author Status Section Revision Description n 0.1 Initial Draft </p><p>1 First Published </p><p>2 <enter sponsor dept or bureau name></p><p>Table of Contents</p><p><enter project code & name> Requirements Management Plan v X.X Page 3 of 4 Printed: 5/9/2018 <enter sponsor dept or bureau name></p><p>1.0 Document Purpose</p><p>The purpose of document is to provide a high-level overview of how requirements will be defined and managed throughout the project lifecycle for the <enter project name> project.</p><p>2.0 Glossary and Acronyms </p><p>Table: Terms and Acronyms Used in This Document Term/Acronym Definition</p><p>3.0 Requirements Approach</p><p> Determine how requirements will be gathered  Determine how requirements will be documented  Determine from whom requirements will be gathered</p><p>4.0 Manage Requirement Scope Determine if the proposed requirement falls within the defined scope of the solution Document the process for defining the overall project scope (Charter) and requirement prioritization, including the sponsor’s signoff authority.</p><p>5.0 Manage Requirement Change Document the process for approving requirement changes and the communication of those updates to the appropriate project team members, including which stakeholder(s) has/have signoff authority.</p><p><enter project code & name> Requirements Management Plan v X.X Page 4 of 4 Printed: 5/9/2018</p>