Part 1 (20 points)–Prepare a requirements management plan (RMP) that addresses the five components described in Section 5.1.3.2, PMBOK 6e.  The plan should be at least 3 but not exceed 4 pages and

Part 1 (20 points)–Prepare a requirements management plan (RMP) that addresses the five components described in Section 5.1.3.2, PMBOK 6e.  The plan should be at least 3 but not exceed 4 pages and does not need to conform to APA guidelines (except for citing and referencing sources).

Some things to think about – how is the role of the in-house rep dealt with in the RMP as it relates to activities for planning, tracking and reporting requirements?   Configuration management is not just about software and versioning.  What processes will be used for configuration management activities as they relate to changes in the product requirements?  How and who will authorize/approve changes?   The traceability structure should be tailored to the type of project and should ensure that each requirement adds business value.

Part 2 (15 points)– Prepare requirements documentation and a requirements traceability matrix (RTM).  The requirements documentation should be in MS Word and include:

•           Business requirements for the Peter’s Company (company-level perspective).

•           Business requirements for the Corwin Corporation (company-level perspective).

•           Stakeholder requirements for Delia, Royce, Frimel, Reddy, West, and Ray.

•           Solution requirements

•           Project requirements, and

•           Transition requirements (should successful R&D occur)

Two requirements per category above should be included in the RTM.  The RTM should be in MS Excel format.

Part 3 (15 points)– Create a Scope Statement.  Using the requirements documents from Part 2, prepare a Scope Statement that addresses the four components described in Section 5.3.3.1, Project Scope Statement, PMBOK 6e.  The statement should not exceed 3 pages and does not need to conform to APA guidelines except for citing and referencing sources

Part 4 (25 points) – Create a WBS and WBS Dictionary.  Now that your group (at Corwin) has a firm understanding of the product scope (i.e., “the features and functions that characterize” [the new rubber material] p. 154, PMBOK 5e), as well as the project scope (i.e., the work necessary to deliver the product), use the scope statement and other requirements documentation you group has prepared to create a WBS (no deeper than Level 4 on any tranche) and WBS Dictionary using the template provided.  The following elements of the WBS dictionary must be completed:  WBS ID, WBS Element Name, Description, Accountable Person, Acceptance Criteria, Assumptions, Constraints.  For project management-related work deliverables (e.g, plans, meetings and reviews, reports), also complete the Activity ID and Activity for each work package,

Additional considerations: The project will be completed in phases so preparing a WBS with phases at level 2 is a sensible way to design the WBS.  The project phases are: 1.1. Project Planning, 1.2. Rubber Material Research, 1.3 Rubber Material Development, and 1.4 Project Close.  The work required to complete the project associated with project management for execution, monitoring and controlling processes, can be sub-elements in the research and development phases.  The lucrative production contract (a hopeful outcome) is not part of this project, but could be part of the business decision by Corwin to expend their own funds to complete the development if additional funding is needed.

The scope statement, WBS and WBS Dictionary constitute the scope baseline.

Part 5 (15 points)– Create Scope Validation Process.  Using the cast of characters from the case study (and any additional people needed), prepare a process for validating the work packages and higher-level components of the WBS.   For each part of the process flow diagram, explain in a separate page who from the case study is involved and what is to be done.