5th Edition PMBOK® Guide—Chapter 5: Process 5.2 Collect Requirements

According to the PMBOK® Guide, this process determines, documents and manages stakeholder needs and requirements in order to meet the project objectives.

The inputs are the management plans that give information about the requirements, and the stakeholders that will need to be consulted in order to carry out this process.

The tools & techniques contain a variety of different methods for developing the requirements.

The outputs are the requirements documentation and requirements traceability matrix.

1. Scope Management Plan How project teams will determine which type of requirements need to be collected for the project.
2. Requirements Management Plan Provides processes that will be used throughout to define and document the stakeholder needs.
3. Stakeholder Management Plan Used to understand stakeholder communication requirements and the level of stakeholder engagement in order to assess and adapt to the level of stakeholder participation in requirements activities.
4. Project Charter High-level description of the product, service, or result of the project so that detailed requirements can be developed.
5. Stakeholder register Identifies stakeholders who can information on the requirements, and captures major requirements and main expectations stakeholders have for the project.
1. Interviews Aids in identifying and defining the features and functions of the desired product deliverables.
2. Focus groups Used to learn about expectations and attitudes about a new product, service, or result.
3. Facilitated workshops Focused sessions that bring together key stakeholders to define product requirements.
4. Group creativity techniques Organized to identify product and project requirements.
5. Group decision-making techniques An assessment process having multiple alternatives with an expected outcome in the form of future actions. These techniques can be used to generate, classify, and prioritize product requirements.
6. Questionnaires and surveys Written sets of questions designed to quickly accumulate information from a large number of respondents.
7. Observations It is helpful for detailed processes when the people that use the product have difficulty or are reluctant to articulate their requirements.
8. Prototypes Obtains early feedback on requirements by providing a working model of the final product.
9. Benchmarking Compares actual practices, such as processes and operations, to those of comparable organizations in order to generate best practices.
10. Context diagrams A scope model which visually depicts the product scope by showing a business system and how people and other systems interact with it.
11. Document analysis Elicits requirements by analyzing existing documentation and identifying information relevant to the requirements.
1. Requirements documentation Consists of the following categories of requirements:

  • Business requirements
  • Stakeholder requirements
  • Solution requirements
  • Project requirements
  • Transition requirements
  • Requirements assumptions, dependencies, and constraints.
2. Requirements traceability matrix Traces requirements with respect to the following:

  • Business needs
  • Project objectives
  • Project scope/WBS deliverables
  • Product design
  • Product development
  • Test strategy and test scenarios
  • High-level requirements to more detailed requirements

The important thing is that the needs and requirements of the customer and other key stakeholders need to be translated from high-level requirements to more detailed requirements that eventually will turn into the deliverables that comprise the Work Breakdown Structure.

The next post will give an overview of the next process, 5.3 Define Scope.

3 Responses

  1. I see you don’t monetize your site, don’t waste your traffic, you
    can earn additional bucks every month because you’ve got hi quality content.
    If you want to know how to make extra $$$, search for: Ercannou’s essential tools best adsense

  2. You missed “Stakeholder Engagement Plan” part of the Project Management plan Unless you’ve used the V5 name “Stakeholder Management Plan”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: