Project Scope Management (by Process Groups) — PMBOK® Guide, 6th Edition Update
Click here for a detailed analysis of each project management process group and knowledge area.
Collect Requirements 101
What Does Collect Requirements Involve and When Do You Perform It in a Project Life Cycle?
- WHAT Collect Requirements Is. Collect Requirements implies turning project stakeholders’ needs into requirements, characteristics of project deliverables.
- WHY Collect Requirements Is Important. The Collect Requirements process generates two outputs – requirements documentation and requirements traceability matrix – that document how the final product or service of the project will look like to meet the stakeholders’ expectations.
- WHEN Collect Requirements Is Executed. The requirements gathering process is used prior to completing the scope statement.
- HOW Collect Requirements Operates.
Inputs | Tools and techniques | Outputs |
---|---|---|
|
|
|
Source: PMBOK® Guide, 6th ed., Chapter 5, section 5.2, p. 138.
Collect Requirements Key Terms
What Are the Key Terms to Fully Understand the Process of Collecting Requirements?
- Context Diagrams. A method of diagramming the product scope by representing how people, processes, or systems interact with the product.
- Facilitated Workshops. A workshop directed by an independent party that brings together stakeholders to solicit information on a particular issue – i.e., joint application development (JAD) for improving software development process and quality function deployment (QFD) for determining critical characteristics of new product development.
- Multi-Criteria Decision Analysis. A decision matrix used to score and rank ideas in decision making based on conflicting criteria such as expected risk levels, time estimate, and cost and benefit estimates.
- Prototypes. A technique of producing a working replica of the finished product, service, or result to help define user requirements.
Collect Requirements Tips
What Are the Best Tips to Answer Correctly the PMP Cerification Exam Questions on Collect Requirements Process?
- Functional Requirements Vs. Nonfunctional Requirements. Functional requirements describe the intended behavior we want from the product – i.e., new features, bug fixes, and new or different behavior. Nonfunctional requirements refer to elements that are related to the product but do not describe the product directly – e.g., performance, reliability, ease of use, and so forth.
- Joint Application Design (JAD) Sessions. A JAD is a facilitated workshop that brings together end users and development team to define requirements for application design/development.
Click here for a detailed analysis of each project management process group and knowledge area.
SOURCES: Project Management Institute (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide). 6th ed. Newtown Square: Project Management Institute.
pmbok 6th edition, pmi pmp certification, pmp classes, pmp certification classes, pmp classes online, pmp program, pmp boot camp, pmp bootcamp, pmp certification, pmp certification prerequisites, pmp certification requirements, pmp certification process, pmp certification atlanta, pmp certification boot camp, pmp certification program.