Development Requirements Identification

PMBOK v8 Definition

Development Requirements Identification is the process of determining, documenting, and analyzing stakeholder needs and expectations to establish the foundation for project scope. It is performed within the Needs Assessment area of the Value Management System Project, specifically under the Requirements Determination branch (Section 1.1.2). The process produces Requirements Documentation as its primary output, capturing detailed requirements that guide subsequent planning and execution activities.

Why It Matters for the Exam

This concept appears frequently in PMI exam questions testing your understanding of how requirements flow from stakeholder needs into project scope. Expect questions in the Initiating and Planning domains, particularly those asking you to identify the correct sequence of requirements activities or distinguish between requirements documentation and other project documents. PMI tests your ability to recognize which tools and techniques are used specifically for requirements identification versus scope definition.

Key Points to Remember (for the exam)

• Main Process Location: Part of Needs Assessment → Requirements Determination within the Value Management System Project structure

• Primary Output: Requirements Documentation – captures functional, non-functional, business, technical, and quality requirements

• Key Inputs: Requirements Management Plan, Scope Management Plan, Stakeholder Register, Assumption Log, Lessons Learned Register

• Essential Tools & Techniques:

  • Data Gathering: Benchmarking, Brainstorming, Focus Groups, Interviews, Questionnaires and Surveys
  • Data Analysis: Document Analysis
  • Interpersonal Skills: Facilitation, Nominal Group Technique
  • Design Thinking and Prioritization/Ranking

• Common Confusion: Requirements Identification (gathering needs) vs. Scope Definition (translating requirements into scope statements) – they are sequential, not identical processes

• Adaptive Environment Note: In adaptive environments, requirements are collected as user stories and prioritized in a backlog

• Critical Document Link: Requirements Documentation feeds directly into the Develop Scope Structure process (Figure 2-17)

Typical PMI Exam Example

A project manager is starting a new software development project. She conducts interviews with key stakeholders, facilitates brainstorming sessions, and reviews existing documentation to understand what the system must accomplish. She documents these as functional and non-functional requirements. Which process is she performing? → Elicit and Analyze Requirements (Development Requirements Identification)

PMI Exam Traps

• Trap: Confusing Requirements Documentation with Scope Baseline

  • Reality: Requirements Documentation is an output of Elicit and Analyze Requirements; Scope Baseline is developed later in Define Scope and Develop Scope Structure

• Trap: Thinking requirements identification happens only once at project start

  • Reality: Requirements are progressively elaborated and may be updated throughout the project, especially in adaptive environments

• Trap: Assuming all requirements gathering techniques are interchangeable

  • Reality: Benchmarking compares against industry standards; Brainstorming generates creative ideas; Interviews elicit detailed individual perspectives – each serves a different purpose

• Trap: Confusing Requirements Determination (1.1.2) with Alternatives Development (1.1.3)

  • Reality: Requirements Determination identifies what is needed; Alternatives Development explores different ways to satisfy those requirements

Important PMI Connections

Quick Review Questions

1. What are the primary data gathering techniques used in the Elicit and Analyze Requirements process?

2. How does requirements identification differ between predictive and adaptive project environments?

3. Which project documents serve as inputs to the Elicit and Analyze Requirements process?

4. What is the relationship between Requirements Documentation and the Scope Baseline?

5. Name three interpersonal and team skills used during requirements identification activities.

PMBOK v8 Reference

Section 1.1.2 – Requirements Determination (within Needs Assessment, Value Management System Project) Figure 2-15 – Elicit and Analyze Requirements Inputs, Tools and Techniques, and Outputs Figure 2-17 – Develop Scope Structure Process (showing Requirements Documentation as input)