PJM6005 Final Paper

Requirements Management Plan (RMP)

Sebastian Guevara

Mustafa Bokhary

Xiangling Yang

Jialin Zheng (Catherine)

Surbhi Ithape

Junze Li

Northeastern University

PJM 6005

Michael Madden

Table of contents

Executive Summary

Project Overview → Mustafa

Requirement Gathering Process → XL

Key Roles and Responsibilities → Mustafa

Assess Requirements → XL

Requirements collection Time Table --- Catherine

Requirements Traceability → Sebastian

RMP Approval → Sebastian

1.Executive Summary – In 1-page, 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.

Elicit:

In this process, it mainly uses 1-to-1 interviews and brainstorming to inspire and collect requirements of different types of stakeholders. Stakeholders are divided into a small number of key stakeholders and a large number of general stakeholders. Interview a small number of key stakeholders to ensure that the requirements of the stakeholders are understood correctly. In addition, you can also ask the key ftostakeholders to ask for basic requirements. Concentrating brainstorming meetings on a large number of general stakeholders, the collision and divergence of thoughts can generate a lot of ideas to integrate and improve requirements.

（1） 1 to 1 interview: This is a form of person-to-person face-to-face interview. The interviewer can determine the required standards and intentions by observing the interviewee's facial expressions and asking questions.

（2） Brainstorming meeting: Team members come together for a lot of creative divergence on a topic and expand based on what others think. This tool can collect lots of thoughts in shot time.

Analyze:

In this process, it mainly uses SMART, expert and MoSCow analysis tools. The SMART analysis is first used to determine whether the requirements meet the criteria and thus to determine the validity of the requirements. Next, use expert analysis to identify requirements that have significant impact and must. Finally, MoSCoW is used to rank the remaining requirements.

（1）SMART analysis：This is an analytical method for assessing the effectiveness of requirements in accordance with SMART rules.

（2）Expert analysis：This method requires the professional experts or experienced personnel to make judgments and give their opinions based on their professional knowledge.

（3）MoSCow analysis：This technique is often applied in agile project management. Use this rule to grade requirements to determine the needs that need to be prioritized.

Document:

In this process, requirements need to be classified and graded into the document. In addition, a requirements tracking matrix should be established to facilitate tracking the completion of requirements in the project.

（1）Rquirements tracking matrix: This matrix records relevant information about requirements in detail, and is mainly used to track the completion of requirements in the project.

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

5.Assess Requirements:

	Must have	Should have	Could have
Functional Requirements	Identify, procure, and then successfully implement a project management software tool(s) solution for TSG.	Assess impact of new PM tool to TSG’s organization.	Add a project management knowledge base to provide tool downloads and templates.
	Create and conduct training sessions for all TSG’s critical stakeholders.	Add training usage videos to automated project management tools.
			Providing survey opportunities to users to help the future development of our website. Creating a more customizable experience to fulfill different needs from our users.
Constraint requirements	Project plan integration must be completed by summer 2020 for a Board decision.	The cost of completing the project does not exceed $ 650,000.	Try to ensure a sense of stakeholder participation in each project process.
	Entire project needs to be completed by 12/31/2021.

6.Requirements Collection Timetable ：

Timeline	Requirement Collection process	Requirement collection method	Key Resource
03/01/2020 - 03/08/2020	Eliciting	Interviews, Brainstorming, Surveys and questionnaires	Project Manager, SMEs, TSG PM
03/09/2020 - 03/17/2020	Analyzing	SMART Analysis, Expert Analysis, MoSCow	Project Manager, Project Team
03/17/2020 - 03/22/2020	Validating	Requirement tracking Matrix, Facilitated Workshops, Focus Groups	Project Manager, Stakeholders, TSG PM

7.Requirements traceability：

The team will look to maintain the WBS fully updated at all times during the project. It is important to have all of the requirements expressed by the key stakeholders in the WBS. This will allow the PM to look at the state of the project and maintain a clear picture of any of the three problems with task:

· Incomplete tasks running late

· Tasks that should have started, but have not

· Have not completed as much work as planned.

By managing the WBS closely the PM will also have the opportunity to trace the problem of success to each requirement and be able to address it properly. With this in mind this team will implement a requirements traceability matrix.

8.RMP Approval：

It is important to have the project sponsor review this document. They are not only a key stakeholder but they are the ones giving economical life to the project. This document illustrates the management structure of the project. It is a simple guide to what is going on and who is responsible for that requirement. The idea being that there should be no surprises. The RMP will serve as a document that will maintain the project on track. Because it maintains an accurate state of each requirement. The RMP should also be reviewed by all key stakeholders previously identified.

Week 2 Assignment No. 2

Group Assignment

Group High Five Participants:

Mustafa Bokhary (Section 2 and 4)

Northeastern University, Boston

PJM-6005 - Project Scope

Dated: March 01, 2020

Table of Contents

Section	Topic	Page
1.	Executive Summary
2.	Project Overview
3.	Requirements Gathering Process
4.	Key Roles & Responsibilities
5.	Assess Requirements
6.	Requirements Collection Timetable
7.	Requirements traceability
8.	RMP Approval

RMP Version History

Version #	Date	Author	Key Differences
1	03-01-2020

Enterprise Project Management Tool Selection & Implementation Project

2. Project Overview: The TestSmart Group (TSG) is a non-profit organization that provides educational testing services to the Department of Education (DoE) of the State of Massachusetts, and a valued Customer of our company, Tim Inc. For the past many years we have worked extensively with TSG towards implementing Project Management methodology frameworks and processes, tools & templates, conducting training for project managers and their project teams on effective project management, coaching teams in the development of their project plans, and the implementation of processes and templates for program and project portfolio management to add strategic-level project governance, with the overall objective of helping TSG achieve maturity in project management which, their management believes, has significantly changed the TSG organization.

The Enterprise Project Management Tool Selection & Implementation (EPMTSI) Project is the next step in our PM maturity journey with TSG. The purpose of this project is to increase productivity and improve the quality of project planning and execution at TSG, by using more current and productive PM collaborative tools than the ones that are currently being used, such as MS SharePoint, MS Project, Excel Gantt Charts and Jira. The project involves defining the process for assessing and selecting the “Best Value” automation tool; identifying, procuring and implementing a project management software tool(s) solution; integrating TSG’s current PM processes into the chosen solution; create and conduct training sessions for all TSG’s critical stakeholders; identifying and training advanced users (i.e. train-the-trainer) to serve as operational support; supporting project, program and portfolio managers in managing their functions; the solution should provide the functionality for TSG’s senior managers to make informed decisions, and providing effective, accurate and timely project progress information and metric dashboards for TSG managers and TSG’s Board of Directors. The aforementioned requirements are not exhaustive and additional requirements still need to be collected, prioritized and validated for possible inclusion in this initiative.

The approved budget for the project is $650,000 with a contingency reserve of another $100,000, the control of which is with the Project Sponsors. The project has been budgeted in the calendar year 2020 and 2021 and the TSG management has made it clear that the project should be fully implemented, approved and operational for enterprise wide use, latest by 1/01/2022. It is important, therefore, that the project scope statement and detailed planning is complete by the first quarter of 2020, so that the project plan integration can be approved by the Board by summer 2020. The acceptance criteria, quality requirements and change management process governing this project have been clearly defined and made part of this report. This project provides Tim Inc. with the opportunity to not only consolidate our long and outstanding relationship with TSG, but also take it to the next level.

Key Roles & Responsibilities: For the purpose of this RMP, the table below identifies the key stakeholders who will be involved with gathering, creating and managing the project requirements throughout the project‘s lifecycle.

Table X: Roles & Responsibilities

Roles	Responsibilities
1. Project Sponsor (TSG Management)	· Approves Project Scope, Project Management Plan and Project Plan Integration · Approves the Requirements Management Plan and updates · Reviews and provides comments and clarification for requirements · Validates requirement details · Defines and approves the required dashboard for monitoring projects · Reviews and approves test results and the defined project acceptance criteria · Approves, releases budget · Controls contingency (budget) reserve · Reviews and approves change requests by PM
2. Project Manager	· Manages Requirements Management processes · Develops project scope & project management plan · Identifies current solution functionality & more detailed requirements to assess, select and implement an effective enterprise wide PM solution · Performs requirements quality assurance · Manages requirements traceability · Gathers, records stakeholders’ requirements, and implements / updates requirements in the project scope · Evaluates TSG’s current PM processes and additional requirements that need to be integrated · Define requirements to identify, procure and implement a project management software tool(s) · Designs the required training regimen for all TSG’s critical stakeholders and identifies requirements for conducting the training (specialists, infrastructure, etc.) · Manages change request process · Relates requirements to project managements processes of TSG · Assesses the impact of new PM tool to TSG’s organization. Then, creates a proposed effective organizational change management strategy initiative
3. SME’s (Functional Heads of TSG Organization as subject matter experts plus Vendor)	· Represent each functional departments of TSG and provide individual requirements for the project management software tool(s) solution · Participate actively in the requirements development process · Participate in interviews and workshops and provide inputs during the project elicitation process · Build requirement metrics for system acceptance and quality assurance · Provide resources for assistance in project implementation, if necessary · Provide access and necessary infrastructure to implement the project · Act as the TSG’s Test Team for project acceptance · Testing System Replacement requirements · SME from the vendor’s side to provide infrastructures requirements for the deployment of system that provides the desired functionality
4. Core Project Team	· Assists the project manager in his role and responsibilities · Performs different roles as assigned by the PM · Follows the Requirements Development and Management processes · Aids the PM in gathering requirements and traceability information · Refines requirements · Performs solution analysis · Proposes Change Requests · Confirms that the impacted requirement(s) are covered in the Change Requests
5. Business Owner (Management of Tim Inc.)	· Assigns resources to the core project management team · Oversees function of the project management team · Provides high level facilitation and coordination, as and when required · Intervenes and mediates in case of issue escalation · Hires external subject matter expert(s) for guidance & support in the project, if required

6. Requirements Collection Timetable

Timeline	Requirement Collection process	Requirement collection method	Key Resource
03/01/2020 - 03/08/2020	Eliciting	Interviews, Brainstorming, Surveys and questionnaires	Project Manager, SMEs, TSG PM
03/09/2020 - 03/17/2020	Analyzing	SMART Analysis, Expert Analysis, MoSCow	Project Manager, Project Team
03/17/2020 - 03/22/2020	Validating	Requirement tracking Matrix, Facilitated Workshops, Focus Groups	Project Manager, Stakeholders, TSG PM