This process gathers all the requirements guiding the development of project deliverables. The PMBOK states that this process determines, documents and manages stakeholders needs and requirements to meet project objectives (PMI,2013).
It is imperative to fully understand what the customer wants and needs. In collecting requirements, project managers need to collect all quantified documents that meets the needs and expecations of the sponsor, stakeholders and the customer. These requirements are the foundation to establish the WBS. The more inputs from different sources to include, business requirements, stakeholder requirements, project requirements and functional requirements, the higher chances of project success.
Collect Requirements: Inputs, Tools and Techniques, and Outputs, Reprinted from "A Guide to the Project Management Body of Knowledge (PMBOK Guide), 5th ed." by Project Management Institute, 2013, pg 111. Copyright 2013 by PMI.Inc. Reprinted without permission.
1. Project Charter (Input): This Project Charter was taken from PMGT 502 in an example to develop a charter and scope statement. This artifact adequately reflects an input for the Collection Requirement Process.
2. Group decision-making techniques (Tools and Techniques): this artifact was taken from PMGT 611. It was an essay on organizational structure and how teams come together to make better decisions.
3. Example Requirements for a Bicycle: Homework assignment from PMGT 614, WBS 1 module, to identify requirements that drive design of a bicycle. This reflects the output of this process.