Reference no: EM132224582

Principles of Project Management [Unit 7- Scope Planning] Book- contemporary Project Management 4th Edition

CASE: Peter's Company R&D Project

Case Study on Research and Development (R&D) Projects

The case study below offers an excellent perspective on how projects are often initiated under less than ideal circumstances—which often lays the ground work for project failure.

Companies that provide a service for another company usually respond to a bid document from a company that needs help. This case study is a good example of this situation. The bid document can be as simple as an email from the buyer to the seller or as complicated as a request for proposal (RFP) outlining the objectives of the project and asking a seller to develop a proposal that provides a solution.

Each company (seller and buyer) will have a business case for doing the project. The Peter’s Company is outsourcing for a reason. The Corwin Corporation is taking on the project for a different set of reasons. One of the reasons the Corwin Corporation is taking on the work is the looming, potentially very lucrative production contract if they are successful. There are no guarantees in research and development project that there will be success.

Question-

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.

Components:

-How requirements activities will be planned, tracked, and reported

-Configuration management activities such as: how changes will be initiated, how impacts will be analyzed, how they will be tracked, traced, and reported, as well as the authorization levels required to approve these changes.

-Requirements prioritization process

-Metrics that will be used and the rationale for using them

-Tracebeability structure that reflects the requirement attributes captured on the traceability matrix.

Update: What do you mean by Project Management Question? I have posted full case study question above.