5.2 Collect Requirements
Process Definition
Collect requirements is the process of gathering stakeholder inputs to the projects objectives. It provides a means for managing the scope of work created by stakeholders needs and requirements.
Figure 9. Project Management Body of Knowledge Figure 5-4. Reprinted from "A Guide to the Project Management Body of Knowledge (PMBOK Guide), 5th Edition" by Project Management Institute, 2013, p. 111. Copyright 2013 by Project Management Institute, Inc. Reprinted without permission.
Process Assessment
The collection of requirements involves the gather and documentation of the customer/stakeholders needs. Quantified and recorded these requirements will help to form the scope baseline. Many of the follow-on processes such as the WBS, cost, schedule, quality planning and procurement are based on the results of this process.
(Inputs) Scope Management Plan
The scope management plan will provide the project team insight as to what type of requirements need to be collected. The example is an excerpt from a group project in PGMT 611 Anatomy of Project Organizations, that was written by Jeremy Curbey, Domingot Tuckler, and Reese Darlington.
(Tools & Techniques) Questionnaire, Requirements Traceability Matrix
A well thought-out questionnaire can provide the project team with some clarity as to what requirements need to be collected, its purpose, and importance to the stakeholder. The example is an excerpt from a group project in PGMT 611 Anatomy of Project Organizations, that was written by Jeremy Curbey, Domingot Tuckler, and Reese Darlington. A requirements traceability matrix is a good way to show the relationship between requirements as well as key attributes that help define the requirement. The example is an excerpt from a group project in PGMT 612 Leading Projects Across Cultural, Corporate, and International
Boundaries, that was written by Jeremy Curbey, Khoi ChuChe, Corey Cowley, Reese Darlington, and Domingo Tuckler.
(Outputs) Requirements Documentation
The requirements document breaks down each requirement needed for project completion. This example is from a group project in PMGT 501 Fundamentals of Project Management, written by Jeremy Curbey, Jay Kinser, and Charles Sutherland.