Requirements Management Plan (RMP)

Mona78

RequirementsManagementPlanRMP.docx

Home >Business & Finance homework help >Management homework help >Requirements Management Plan (RMP)

Week 2 Assignment

Requirements Management Plan (RMP)

Overview and Rationale

For this assignment you will create a Requirements Management Plan (RMP.)

The Requirements Management Plan is a key document in managing the scope of your project. The RMP components describes how you will elicit, analyze, document and manage the requirements of the project. Specifically, the RMP will outline the up-front gathering of high-level project and product requirements, as well as the more detailed product requirements that you will collect during the project lifecycle.

Adhering to an effective requirements management process helps the project focus on the requirements that have been developed and maintains the integrity of the requirements throughout the lifecycle of the project.

Program and Course Outcomes

This assignment is directly linked to the following key learning outcomes for the course:

· Know the general requirements collection process steps and become familiar with best practice requirements collection techniques

· Practice techniques for eliciting stakeholder’s input to develop effective and feasible requirements success criteria

· Distinguish between different types of requirements (functional, Non-functional, technical, project, regulatory, etc.)

· Analyze techniques used to differentiate the needs /vs/ wants of stakeholders for a project: MoSCoW technique

· Understand the purpose of an effective Requirements Management Plan (RMP): Create an RMP

In addition to these key learning outcomes, you will also have the opportunity to demonstrate the following skills through completing this assignment:

· Critical thinking and analysis

· Problem solving

Your written assignment this week is to complete a Requirements Management Plan for your chosen case study (the SAME case study you used for your Scope Management Plan last week.)

Please refer to the assignment instructions and outline below in order to successfully complete the assignment.

Requirements Management Plan (RMP) Outline and Instructions

Use the following list to create the sections (components) that should be included within your RMP:

1. Executive Summary – In 1 paragraph, write this Executive Summary on the key components of your RMP.

2. Project Overview. In 2-3 paragraphs, briefly describe the purpose of the project for the readers that have not seen your Project Charter nor understands the project’s key business objectives.

3. The Requirements Gathering Process. In this section, describe the process that you will use to elicit, analyze and document the project requirements. Identify and describe at least 4 requirements collection tool(s) and techniques you intend to use to collect project requirements from key stakeholders. Moreover, please comment on the collection method’s efficiency to collect necessary project requirements. (Note : efficiency should focus on timeliness to collect requirements vs. cost to collect requirements)

4. Key Roles and Responsibilities. In this section, please list the roles & responsibilities of at least 5 key project stakeholders who will be involved with gathering, creating and managing the project requirements throughout the project ‘s lifecycle.

(For example: Roles could include the project manager, project sponsor, business analyst, customer(s) or project SMEs, or other key stakeholders. Responsibilities could include requirements elicitation, change management, requirements creation, testing and approving requirements. etc.)

5. Requirements Collection Timetable - Using at least 3 requirements collection methods, briefly identify a requirements collection schedule for your project. Please justify your timeline based upon key resources availability, their assumed skills and the collection method used.

6. Requirements Traceability. Please describe how you will track and manage requirements from requirements elicitation to identifying project deliverable, WBS / project schedule development and scope change management. [Hint: Review 100% rule].

7. RMP Approval. Identify who will review and approve the RMP. Please comment on how you will communicate the RMP to project and key stakeholders.

Assignment Format

Below are some key guidelines you will want to ensure you follow in creating this assignment. Think of this short list as a quality control checklist, along with the attached grading rubric.

· Requirements Management Plan template must be complete, please submit in MS Word (.doc, .docx) or .pdf format

· You should format the document professionally:

· Double line spacing between paragraphs but 1.5 spacing within the paragraph

· 12-point Times Roman

· 1-inch margins

· Use footnotes or endnotes and citations

· 2-14-point font, bold headings and subheadings

· Adhere to APA 6th edition conventions

· Please carefully review the list of RMP document components provided on the previous page and use it as a basis for creating your RMP. The list contains specific guidelines on what is required in each RMP section.

· Please ensure you remove all instructions (italicized) and any examples provided within the RMP outline

Please be sure to review the attached rubric. Along with these assignment instructions, the rubric will ensure you have a solid understanding of the assignment requirements and how the assignment will be graded. The rubric is provided on the next page.

Requirements Management Plan Rubric

Assessment Element	Above Standards	Meets Standards	Approaching Standards	Below Standards	Not Evident
Overview and Requirements Process (40%)	Overview of project and assessment of the project requirements process is in depth, logical and effective in managing project requirements. At least 4 requirements elicitation processes were effectively identified. Demonstrated a high degree of understanding of the requirements elicitation process and collection tools and techniques.	Overview of project and assessment of the project requirements process was mostly in depth, logical and effective in managing project requirements. At least 4 requirements elicitation processes were identified. Demonstrated an adequate level of understanding the requirements elicitation process and collection tools and techniques.	Overview of project and assessment of the project requirements process was not in depth, and somewhat effective in managing project requirements. At least 4 requirements elicitation processes were identified. Demonstrated a minimally acceptable level of understanding the requirements elicitation process & collection tools and techniques.	Overview of project and assessment of the project requirements process was not adequate Less than 4 requirements elicitation processes were identified. Demonstrated an unacceptable level of understanding the requirements elicitation process & collection tools and techniques.	Demonstrated an unacceptable level of understanding the requirements elicitation process & collection tools and techniques.
Key Roles and Responsibilities (20%)	At least 5 key stakeholders’ roles and responsibilities were clearly identified. Demonstrated a superior level of understanding the key roles and responsibilities in the requirements management processes.	At least 5 key stakeholders’ roles and responsibilities were mostly adequately identified. Demonstrated an effective level of understanding the key roles and responsibilities in the requirements management processes.	At least 5 key stakeholders’ roles and responsibilities were mostly adequately identified. Demonstrated a minimally acceptable level of understanding the key roles and responsibilities in the requirements management processes.	Less than 5 key stakeholders’ roles and responsibilities were identified. Demonstrated a less than adequate level of understanding the key roles and responsibilities in the requirements management processes.	Less than 5 key stakeholders’ roles and responsibilities were identified. Demonstrated an unacceptable level of understanding the key roles and responsibilities in the requirements management processes.
Timetable and Traceability Process (20%)	Provided at least 3 timeline assessment for requirements elicitation. Requirements collection timeline was well developed and logical. Discussion on requirements traceability process was in depth and logical. Demonstrated a superior level of understanding requirements collection timelines and effectiveness’ of the traceability management process.	Provided at least 3 timeline assessment for requirements elicitation. Requirements collection timeline was mostly well developed and logical. Discussion on requirements traceability process was mostly in depth and logical. Demonstrated an acceptable level of understanding requirements collection timelines and effectiveness’ of the traceability management process.	Provided at least 3 timeline assessment for requirements elicitation. Requirements collection timeline was adequate - some were vague. Discussion on requirements traceability process was mostly not in depth and logical. Demonstrated a mostly acceptable level of understanding requirements collection timelines and effectiveness’ of the traceability management process. Improvement is needed to meet standards.	Did not provide at least 3 timeline assessment for requirements elicitation. Requirements collection timeline was not adequate. Discussion on requirements traceability process was not in depth nor logical. Demonstrated an unacceptable level of understanding requirements collection timelines and effectiveness’ of the traceability management process. Improvement is needed to meet standards.	Demonstrated an unacceptable level of understanding requirements collection timelines and effectiveness’ of the traceability management process. Improvement is needed to meet standards.
Critical Thinking (10%)	Professional insights into depth and breadth of assignment - goes WELL beyond assignment requirements to create an effective RMP.	Showcases a comprehensive understanding of the requirements management process, and the effectiveness of an RMP.	Showcases a base understanding of the requirements management process, and the effectiveness of an RMP.	Does not evidence a base understanding of the requirements management process, nor understands the effectiveness of an RMP.	Evidences a very poor understanding of the requirements management process, does not understands the effectiveness of an RMP.
Grammar & Clarity (10%)	All work grammatically correct with no misspellings or grammatical mistakes. Expresses ideas and opinions clearly and concisely in a manner appropriate to the assignment.	All work grammatically correct with rare misspellings.	Minimal errors in spelling, grammar, sentence structure and/or other writing conventions but the reader is able to understand what the writer meant.	Frequent errors in spelling, grammar, sentence structure, and/or other writing conventions that distract the reader.	Writing contains numerous errors in spelling, grammar, sentence structure, etc. that interfere with comprehension. The reader is unable to understand some of the intended meaning.