ProPM / Collect Requirements
ProPM Logo About ProPM Initiate and Close Integration Management Quality Management PMBOK ITTO Dictionary      
Process Benefits Plan management Scope Management HR Management Input / Output Menu      
Process Inputs Plan execution Time Management Communications Management Input Menu      
Tools and Techniques Execute Cost Management Procurement Management Tool and Technique Menu      
Process Outputs Monitor and Control Risk Management Stakeholder Management Output Menu      
ProPM Logo Collect Requirements    
ProPM Logo                

The Collect Requirements process consists of;

  • Determining
  • Documenting
  • Managing

Stakeholder needs & requirements to meet project objectives.

The key benefit of the Collect Requirements process is that it provides the basis for;

  • Defining & managing the project scope.
  • Including the product scope.

Requirements are: Conditions or capabilities that the project / product must meet to;

  • Satisfy an agreement.
  • Satisfy some other formally imposed specification.

Requirements include the quantified & documented needs & expectations of;

  • The Sponsor
  • The Customer
  • Other Stakeholders

Requirements must be elicited, analyzed & recorded in enough detail;

  • To be included in the scope baseline.
  • To be measured once project execution begins.

Requirements become the foundation of the WBS.

  • Cost, schedule, quality planning & sometimes procurement: all based on these requirements.

Requirements are often categorized into different types;

  • Business Solutions: Referring to stakeholder needs.
  • Technical Solutions: How stakeholder needs will be implemented.

Further refinement of categorization can result in;

  • Business Requirements: Higher level organizational needs as a whole.
  • Stakeholder Requirements: Needs of stakeholders or stakeholder groups.
  • Solution Requirements: Features, functions, characteristics to meet requirements.
    • Functional Requirements: Behaviors of the product.
    • Non-Functional Requirements: Qualities required for product to be effective.
  • Transition Requirements: Temporary capabilities such as training.
  • Project Requirements: Actions, processes or other conditions the project needs to meet.
  • Quality Requirements: Condition or criteria required to validate successful completion;
    • Of Project
    • Of deliverable
    • Of other project requirements

Project success is directly influenced by active stakeholder involvement in;

  • Discovery & decomposition of needs into requirements
  • General care taken with determining, documenting & managing requirements

Development of requirements begins with an analysis of info contained in;

  • Project Charter
  • Stakeholder register
  • Stakeholder management plan
ProPM Logo    
ProPM Logo    
ProPM Logo    
Scope Management          
Plan execution          
Collect Requirements          
Process Inputs          
scope mgmt. plan          
requirements mgmt. plan          
stakeholder mgmt. plan          
Project Charter          
stakeholder register          
Tools and Techniques          
Focus groups          
Facilitated workshops          
Group creativity tech.          
Group dec. making tech.          
Questionnaries & surveys          
Context diagrams          
Document analysis          
Process Outputs          
Require. documentation          
Require. tracability matrix          
Process Benefits          
Requirements collected from stakeholders provide the core input, foundation and corner stones for;

*  Eventually defining & managing the project scope.
*  Including the product scope.
ProPM Logo    
ProPM Logo    
ProPM Logo    
ProPM Logo    

© 2014-2020