Collect Requirements

This article contains most of the important information you need to know about Collect Requirements process in order to answer questions related to this topic in the PMP Exam, I recommend you review this type of articles 1 week before your exam date, all information mentioned are based on PMBOK Guide 6th edition and PMP Exam Prep 9th edition for Rita Maclhy’s, ITTO refers to Inputs, Tools & Techniques and outputs.

This process is a part of Planning Process group and Scope Management Knowledge Area with the following ITTO’s

Inputs:

  1. Project charter
  2. Project Management Plan ( Scope & Requirements management plan , Stakeholder engagement plan )
  3. Project Documents ( Assumption log , lessons learned register , stakeholder register )
  4. Business documents ( Business case )
  5. Agreements
  6. Enterprise environmental factors
  7. Organizational process assets

 

 

Tools & Techniques:

  1. Expert Judgement
  2. Data Gathering ( Interviews , Focus Groups , Facilitated Workshops Brainstorming , Surveys and benchmarking )
  3. Data Analysis ( Document Analysis )
  4. Decision making ( Voting , Multicriteria decision analysis )
  5. Group Creativity Techniques
  6. Group Decision Making Techniques
  7. Observations
  8. Surveys
  9. Prototypes
  10. Benchmarking
  11. Context Diagram
  12. Document Analysis

Outputs:

  1. Requirements Documentation
  2. Requirements Tractability matrix

 

  • Requirements are what stakeholders needs from a project , here are the main types of requirements
  1. Business Requirement: Support Business objectives of the company
  2. Stakeholder requirements.
  3. Solution Requirements: Functional ( Product behavior ) and non-functional ( reliability, security … )
  4. Transitional Requirements: temporary requirements including trainings, tracking.
  5. Quality Requirements: Quality criteria defined by stakeholders.
  • All requirements should be evaluated against :
  1. Project Business Case.
  2. Project Charter.
  3. Project Scope of statement.
  4. Project Constraints.
  • Collect Requirements Process Tools and Techniques :
  1. Review historical Records: Looking on previous similar projects.
  2. Interviews: Expert interviews, meeting key stakeholders to collect requirements.
  3. Focus Groups: Meeting a specific set of stakeholders to collect requirements for an aspect of the project.
  4. Facilitated Workshops: group of stakeholders from different perspectives which results in user stories like “As a – Role- , I want a –Goal- , So that “business case” .
  5. Brainstorming, main reason is not only to collect ideas but to encourage participants to build on each other idea.
  6. Nominal Group techniques which includes ranking of useful ideas.
  7. Multi criteria decision analysis , quantify requirements through decision matrix based on factors like risk ,schedule ,cost…
  8. Mind Maps , Diagram ideas to help generate , classify or record information , several trees radiating from central core.
  9. Affinity Diagram , Requirements divided upon similarities , each is given a title.
  10. Surveys , used for large groups and projects.
  11. Prototype , Model of proposed product.
  12. Bench marking , looking at what competitors doing, It consumes time and cost , it limits group creativity.
  13. Observation , includes job shadowing , watching potential used of the product at work.
  14. Context Diagram , diagrams that shows input , source and output to show how people interact with the system.
  15. Analytic Hierarchy process , for complex decisions give different weights to factors to build hierarchy then voting is accomplished.
  16. Group Decision making ,
  17. Dictatorship
  18. Majority technique , above 505 agreement
  19. Plurality technique , Biggest percentage agree
  20. Consensus technique , generates agrrement
  21. Delphi technique , From remote locations experts gives their opinion , it is executed several times until agreement is obtained.
  • Voice of customer ( VOC ) , translates customer needs into requirements
  • Collect requirements process have 2 major outputs :
  1. Requirements Tractability Matrix, tracks requirements from origin to deliverables , it links each requirement to the objective , requirement attributes should be documented and to include source, status , identification … all necessary details .
  2. Requirements Documentation , Document all stakeholders requirements along with acceptance criteria of each .

Leave a Reply

Logged in as shadi alsha3er. Log out?