Welcome to Quality Essay Writers

Management homework help

Management homework help. PJM 6005-Team Assignment: Requirements Management Plan (RMP)
 
Overview and Rationale
For this assignment, each team will create a Requirements Management Plan (RMP).
The RMP is a key document in managing the scope of your project. The RMP describes how you will elicit, analyze, document and manage the project’s requirements process.
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 evidence the following skills through completing this assignment:

  • Critical thinking and analysis
  • Problem solving

Essential Components & Instructions
Requirements Management Plan (RMP) Overview
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.
 
Most importantly, adhering to an effective requirements management process helps the project team focus on the requirements that have been developed and maintains the integrity of the requirements throughout the lifecycle of the project.
Requirements Management Plan (RMP) Template / Instructions
The following template outlines common RMP sections:

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

 

  1. 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.

 

  1. 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) & techniques you intend to use to collect project requirements from key stakeholders.   Moreover, please comment on collection method’s efficiently to collect necessary project requirements. (Note:  project efficiency should focus on timeliness to collect requirements vs. cost to collect requirements)

 

  1. 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 team SMEs, or other key stakeholders. Responsibilities could include requirements elicitation, change management, requirements creation, testing and approving requirements. etc.)
 

  1. Assess Requirements: From your project case overview and individual research, write at least 6 requirements. Please ensure requirements follow the SMART guideline for effective project requirements.  Moreover, each requirement must be categorized based upon the project’s defined strategic objectives & goals.  Please categorized each requirement into Must Have, should have and Could have/Would like to have (pls refer to the MoSCoW Method).  You can use a table for this section.

 

  1. 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.

 

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

 

  1. RMP Approval. Identify who will review and approve the RMP.  Please comment on how you will communicate the RMP to project team 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, pls submit in MS Word (.doc, .docx) or .pdf formats
  • You should format the document professionally
  • Please ensure that you remove all instructions (italicized) and any examples provided within the template

Please be sure to review the attached rubric. It along with these assignment instructions will ensure you have a solid understanding of the assignment requirements.

  • Please carefully review the RMP template.  The template has specific guidelines on what is required in each RMP component.

Please be sure to review the attached rubric. It along with these assignment instructions will ensure you have a solid understanding of the assignment requirements.
 
 
 
 
 
 
Rubric(s)
 

Assessment Element Above Standards Meets Standards Approaching Standards Below Standards Not Evident
Overview and
Requirements Process
(25%)

 
Overview of project and assessment of the project requirements process was in depth, logical and effective in managing project requirements.
 
Moreover, At least 4 requirements elicitation processes were effectively identified.
 
Team demonstrated a high degree of the requirements elicitation process & 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.
 
Moreover, At least 4 requirements elicitation processes were   identified.
 
Team demonstrated an adequate level of understanding the requirements elicitation process & 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.
 
Team 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.
 
Team demonstrated an unacceptable level of understanding the requirements elicitation process & collection tools and techniques.
 
Team demonstrated an unacceptable level of understanding the requirements elicitation process & collection tools and techniques.
 
Key Roles &
Responsibilities
(20%)
At least 5 key stakeholders’ roles and responsibilities were clearly identified.
 
Team 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.
 
Team 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.
 
Team 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.
 
Team 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.
 
Team demonstrated an unacceptable level of understanding the key roles and responsibilities in the requirements management processes.
Requirements Assessment
(20%)
Team provided at least 6 well written and SMART requirements.
 
Each requirement was effectively categorized based upon the project’s defined strategic objectives & goals
 
Team demonstrated a superior level of understanding of a well written and categorized project requirement.
Team provided at least 6 mostly well written and SMART requirements.
 
Each requirement was mostly effectively categorized based upon the project’s defined strategic objectives & goals
 
Team demonstrated an acceptable level of understanding of a well written and categorized project requirement.
Team provided at least 6 requirements.  Not all were adequately written – following the SMART requirements guidelines.
 
Not all requirements were effectively categorized based upon the project’s defined strategic objectives & goals
 
Team demonstrated a mostly acceptable level of understanding of a well written and categorized project requirement.
Team did not provided at least 6 requirements.
 
Moreover, not all were adequately written – following the SMART requirements guidelines.
 
Not all requirements were effectively categorized based upon the project’s defined strategic objectives & goals
 
Team demonstrated a less than adequate level of understanding of a well written and categorized project requirement.
Team demonstrated an unacceptable level of understanding of a well written and categorized project requirement.
Timetable and
Traceability Process
(15%)
Team 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.
 
Team demonstrated a superior level of understanding requirements collection timelines and effectiveness’ of the traceability management process.
Team 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.
 
Team demonstrated an acceptable level of understanding requirements collection timelines and effectiveness’ of the traceability management process.
Team 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.
 
Team demonstrated a mostly acceptable level of understanding requirements collection timelines and effectiveness’ of the traceability management process. Improvement is needed to meet standards.
Team 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.
 
Team demonstrated an unacceptable level of understanding requirements collection timelines and effectiveness’ of the traceability management process. Improvement is needed to meet standards.
Team demonstrated an unacceptable level of understanding requirements collection timelines and effectiveness’ of the traceability management process. Improvement is needed to meet standards.
Critical Thinking
(15%)
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.

 

Management homework help

Solution:

15% off for this assignment.

Our Prices Start at $11.99. As Our First Client, Use Coupon Code GET15 to claim 15% Discount This Month!!

Why US?

100% Confidentiality

Information about customers is confidential and never disclosed to third parties.

Timely Delivery

No missed deadlines – 97% of assignments are completed in time.

Original Writing

We complete all papers from scratch. You can get a plagiarism report.

Money Back

If you are convinced that our writer has not followed your requirements, feel free to ask for a refund.