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

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.

Assume the Peter's Company provided some initial statement of work documentation, by email or other means, that was sufficient for Dan West (the project manager) to move forward with the project for the Corwin Corporation. A sample project charter is provided for you. The project charter (provided) is a high-level document;

Be sure to list as many stakeholders and issues as you can by using your group's collective project management experience. The list of stakeholders is more than a relisting of the cast of characters in the case. A stakeholder register is essential for collecting requirements and for managing communication needs.

Question: "Prepare a requirements management plan (RMP) that addresses the five components described in Section 5.1.3.2, PMBOK 6e.

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

The (RMP) in PMBOK - 5.1.3.2 (5 components):

i) How requirements activities will be planned, tracked, and reported

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

iii) Requirements prioritization process

iv) Metrics that will be used and the rationale for using them

v) Traceability structure that reflects the requirement captured on the traceability matrix

Please refer to the above case study and could you help me with the question above with respect to the Traceability structure of the RMP?

Corwin Corporation By June 2003, Corwin Corporation had grown into a $950 million per year corpora- tion with an international reputation for manufacturing low-cost, high-quality rubber components. Corwin maintained more than a dozen different product lines, all of which were sold as off-the-shelf items in department stores, hardware stores, and automotive parts distributors. The name Corwin was now synonymous with "quality." This provided management with the luxury of having products that maintained extremely long life cycles. Organizationally, Corwin had maintained the same structure for more than fifteen years (see Exhibit D). The top management of Corwin Corporation was