^ [[Appendix B - Project Management Plans and Logs]] # B.1  Requirements Management Plan The Requirements Management Plan defines and documents the requirements management approach, process steps and responsibilities, as well as tools, techniques and artefacts that will be used. Note that requirements themselves are documented and managed in separate artefact(s) (e.g. requirements matrix). Effective requirements management is a critical success factor for projects, as requirements are the starting point for all project work, and principally affect the project risk, duration and budget. Requirements are traditionally defined in detail early in the project lifecycle. However, depending on the type, scope and chosen project strategy, the requirements management process may need to accommodate a more agile definition and elaboration of requirements, thereby allowing for frequent and less formal requirements management cycles. The Requirements Management Plan can be tailored and customised to the project’s needs. In the absence of a more specialised role, the Project Manager (PM) is responsible for executing the process from project initiation until all requirements have been implemented and validated. ![[Table B.1 - Requirements Management Plan - Key Participants.png]] ## Inputs - Project Charter - Project Handbook - Project Stakeholder Matrix ## Steps 1. Check if a requirements management process already exists at the organisational level. 2. Tailor the Requirements Management Plan to the project’s needs. Create it as a standalone document or as a section within the Project Handbook. 3. Define what a requirement is, and what the possible states of its lifecycle are. 4. Ensure that the requirements management process is aligned with the change management process, and that requirement changes are traced to the project’s deliverables and activities. 5. Define the roles and responsibilities for each process step. Define clearly who is responsible for approving and validating the implementation of new requirements. 6. Define the tools and techniques that will be used to identify, evaluate, prioritise and manage requirements (e.g. brainstorming sessions, prototyping, MoSCoW, etc.). 7. Define the possible formats of representation of requirements for the project (e.g. text, use cases, diagrams, user stories, etc. 8. Define the artefacts and repositories used for the documentation and management of the requirements (e.g. specification document or requirements traceability matrix). 9. Define the requirements validation process and make sure it is aligned with the overall deliverables acceptance process. 10. Ensure that the requirements management process is communicated to the project stakeholders. ![[Tabla B.1 - Plan de Gestión de Requisitos - Artefactos relacionados.png]] ## Artefact - Requirements Management Plan (PM2 Template) ___ Spanish Guide: [[B.1 Plan de Gestión de Requisitos]] <-- [[Appendix B - Project Management Plans and Logs]] --> [[B.2 Project Change Management Plan]]