These Techniques Generate, Classify, and Prioritize Product Requirements
PMBOK v8 Definition
Requirements are captured at a high level and decomposed to the level of detail needed to design the final product. Product analysis techniques are used to translate high-level product or service descriptions into meaningful deliverables. These techniques include but are not limited to: product breakdown, requirements analysis, systems analysis, systems engineering, value analysis, and value engineering. This concept falls under Scope Management (Knowledge Area) and is applied primarily during the Planning Process Group.
Why It Matters for the Exam
The PMI exam frequently tests your ability to distinguish between techniques that generate, classify, and prioritize requirements versus those that document or validate them. Questions often present a scenario where you must select the correct technique for a specific requirement type (functional vs. nonfunctional) or identify which tool structures requirements for traceability. Expect these concepts in situational questions about scope definition and requirements collection.
Key Points to Remember (for the exam)
- Three Requirement Types: Functional (behaviors, actions, processes, data, interactions), Nonfunctional (performance, security, reliability, safety, supportability), and Transition/Readiness (data conversion, training, temporary capabilities)
- Product Analysis Techniques: Product breakdown, requirements analysis, systems analysis, systems engineering, value analysis, value engineering
- Requirements Traceability Matrix (RTM): Links business needs → project objectives → WBS deliverables → product design → development → test strategy → test scenarios
- RTM Attributes: Recorded for each requirement to define key information (business needs, opportunities, goals, objectives)
- Project Canvas: A visual tool used to outline and plan key project elements (structured framework)
- Prioritization Matrix: A scatter diagram that plots effort against value to classify items by priority
- Common Confusion: Functional requirements describe what the product does; nonfunctional requirements describe how well it performs
Typical PMI Exam Example
You are managing a software development project. The team needs to document that the system must process 1,000 transactions per second (performance) and must encrypt all user data (security). Which requirement type are you capturing? Answer: Nonfunctional requirements. The exam will test your ability to classify requirements correctly between functional, nonfunctional, and transition/readiness categories.
PMI Exam Traps
-
Trap: Confusing "product analysis" with "requirements documentation"
- Reality: Product analysis generates and classifies requirements; documentation records them
-
Trap: Thinking all requirements are functional
- Reality: Nonfunctional requirements (performance, security, reliability) are equally important and frequently tested
-
Trap: Assuming the Requirements Traceability Matrix is only for tracking changes
- Reality: RTM provides structure for managing scope changes AND links requirements from high-level to detailed levels through the entire project lifecycle
-
Trap: Confusing "transition requirements" with "functional requirements"
- Reality: Transition requirements describe temporary capabilities (data conversion, training) needed to move from current to future state, not permanent product features
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Scope Baseline | Output of | RTM feeds the scope baseline; requirements are decomposed into WBS deliverables |
| Collect Requirements | Preceding Process | Product analysis techniques are used during Collect Requirements to generate requirements |
| Validate Scope | Succeeding Process | Requirements from product analysis are verified against deliverables during Validate Scope |
| Quality Management | Complements | Nonfunctional requirements (performance, reliability) directly feed quality metrics and quality control |
| Product Life Cycle | Related Concept | Product management considerations (Section 2.3) integrate requirements throughout the product life cycle |
Quick Review Questions
-
A project needs to capture requirements about data encryption speed and system uptime. Which requirement type is being documented?
-
Your team is using a technique to break down a high-level product description into detailed deliverables. Which product analysis technique is being applied?
-
What is the primary difference between functional requirements and nonfunctional requirements?
-
Which tool plots effort against value to classify requirements by priority?
-
A data conversion requirement needed to migrate from the current system to the new system falls under which requirement category?
PMBOK v8 Reference
Section 4 – Inputs and Outputs (Requirements Traceability Matrix)
Section 5.2 – Collect Requirements (Product Analysis techniques)
Section 2.3 – Product Management Considerations (Product life cycle and product management integration)