Skip to Main Content
Program Management Curriculum Hero Image

Eliciting and Documenting Vendor Requirements Course

Available Modalities:

  • e-Training
  • Public Classroom
  • On Site
  • Virtual Classroom
Delivery Method PDU Total Technical PMP/PgMp Leadership Strategy PMI RMP PMI SP PMI ACP PfMP PMI PBA
Instructor-Led Training 15 15 0 0 0 0 0 0 0
Delivery Method Instructor-Led Training
PDU Total 15
Technical PMP/PgMp 15
Leadership 0
Strategy 0
PfMP 0
  • CEUs: 1.5
  • CPEs: 18
  • Field of Study: Management Adv Services
  • PDUs: 15

The quality of work performed by a vendor can only be as good as the requirements you provide them. Whether they are a contracting officer, project manager, or member of the integrated project team, an individual who works with a contractor should be adept at eliciting requirements from stakeholders. Taking those requirements and communicating them to vendors in a clear, measurable, and concise fashion will have a direct impact on project success.

In this course, participants will recognize the difference between a requirement and specification and better appreciate how different stakeholders require a different level of detail when it comes to communicating a requirement. Participants also learn how to define the problem, vision, and scope of a solution that will become the primary output of a project. This solution scope becomes the foundation for all future requirements that are documented and communicated to vendors. The solution scope will also become the baseline of against which participants will measure the project to detect and defend against scope creep.

As part of the requirements analysis process, participants also learn how to develop a requirements work plan, which will guide the requirements elicitation activities they will need to perform. Participants learn how to use models to analyze requirements and communicate the requirements to vendors and validate the requirements with stakeholders. Finally, participants learn how to package all of the requirements into a requirements document that can be delivered to vendors and maintained throughout the life cycle of the project.

  • Develop and validate solution scope and quality standards
  • Apply the appropriate modeling techniques
  • Properly plan requirements elicitation and analysis activities
  • Apply the most appropriate techniques for eliciting requirements
  • Document various kinds of requirements in a complete, coherent, and organized requirements document
  • Introduction to Requirements Elicitation
    • The Requirements Elicitation Process
    • What Is a Requirement?
    • Vendors vs. Contractors
    • Requirements Considerations for the Contracting Organization
    • Participants in Requirements Elicitation
    • Requirements Manager
    • From Needs to Requirements
    • Requirements Traceability
    • Requirements versus Specifications
    • Levels and Types of Requirements
    • Performance Requirements
    • Business Rules
    • Documentation and the Requirements Elicitation Process
    • The Documentation Strategy
    • Key Messages
  • Establishing Scope and Quality
    • Mission Statement versus Vision Statement
    • Solution Vision Statement
    • What Is Solution Scope?
    • Defining Solution Scope
    • Scope Creep
    • What Is Change?
    • Causes of Change
    • What Is Quality?
    • Quality and Requirements Elicitation
    • Quality Requirements
    • Quality versus Grade
    • Excellence versus Perfection
    • Cost of Quality
    • Validating Scope
    • Key Messages
  • Planning Requirements Activities
    • The Requirements Work Plan (RWP)
    • What Does the RWP Do?
    • How Is the RWP Used?
    • Elements of the RWP
    • Identifying Requirements Tasks for the Contracting Organization
    • Stakeholder Identification
    • Encouraging Stakeholder Involvement
    • Risk Management Planning
    • Key Messages
  • Requirements Elicitation
    • Requirements Elicitation and Validation
    • Elicitation Keys to Success
    • Levels of Source Accuracy
    • Dealing with Barriers to Elicitation
    • Elicitation and Validation Techniques
      • Market Research
      • Observation
      • Verbal Protocols
      • Interviews
      • Questionnaires
      • Focus Groups
      • Brainstorming
      • Product Evaluation Trials
    • Using Vendors for Requirements Elicitation
    • When Are You Done?
    • Key Messages

     Developing Requirements Documentation

    • Analyzing Requirements
    • Requirements Documentation Quality Attributes
    • Requirements Documents
      • Statements of Objectives (SOOs)
      • Statements of Work (SOWs)
      • Performance Work Statements (PWS)
      • Master Agreements (MAs)
      • Requests for Proposals (RFPs)
    • General Guidelines for Technical Writing
    • Why Use Models?
    • Modeling Requirements Best Practices
    • Characteristics of Effective Requirements
    • Addressing Concerns in the Requirements Documentation
    • Documenting Solution Options
    • Documenting the Correct Requirements
    • Key Messages
  • Validating Requirements
    • Checklist: Validating the Requirements
    • Validation Techniques
      • Desk Checking
      • Walkthroughs
      • Peer Reviews
      • Inspections
    • Consensus and Requirements
    • Managing Consensus
    • Tips for Effective Consensus Building