Program Management Curriculum Hero Image
How to Gather and Document User Requirements

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
e-Training 28 28 0 0 0 0 0 0 28
Instructor-led training 28 28 0 0 0 0 0 0 28
Virtual instructor-led training 28 28 0 0 0 0 0 0 28
Delivery Method e-Training Instructor-led training Virtual instructor-led training
PDU Total 28 28 28
Technical PMP/PgMp 28 28 28
Leadership 0 0 0
Strategy 0 0 0
PMI RMP 0 0 0
PMI SP 0 0 0
PMI ACP 0 0 0
PfMP 0 0 0
PMI PBA 28 28 28
  • CDUs: 28
  • CEUs: 2.8
  • CPEs: 34
  • Field of Study: Business Management & Organization
  • Prerequisites: Prior to taking this course, participants should take Foundations to Business Analysis or have practical professional experience in all of the topics covered in the course, including system development life cycle, project management methodologies, user requirements analysis and requirements management.

Incomplete requirements are often cited as the number-one reason projects or systems fail. Accurately identifying requirements and staying on course from the beginning is key to success in today’s business world.

This “how-to” course introduces the roles of the business analyst as they relate to the elicitation, analysis and documentation of requirements. It familiarizes participants with the core knowledge and skills required to identify and document user requirements. It also addresses how these requirements are managed throughout the life cycle.

Recommendation: The material presented in this course provides the detail needed to begin eliciting and documenting requirements. If you plan to take additional courses in the Business Analysis Professional Development Program, you will need this foundation.

This course is aligned with version 2.0 of A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide)™.

  • Explain the critical role of the business analyst with respect to requirements elicitation and project management 
  • Develop and validate a solution vision and scope 
  • Use appropriate modeling techniques 
  • Planning the requirements elicitation and analysis to maximize efficiency and estimate the required effort 
  • Determine the most appropriate technique for eliciting requirements at different points in the analysis cycle 
  • Analyze various kinds of requirements into a complete, coherent and organized requirements document 
  • Build consensus to validate and finalize the requirements in the business requirements document
  • Creating a Requirements Work Plan
    • The value of planning
    • Elements of a requirements work plan
    • Planning the analysis Identifying business analysis tasks
    • Stakeholder identification and prioritization
    • User identification and profiling
    • Managing risk
  • Documenting Requirements
    • The purpose of documenting requirements
    • Elements of a Business Requirements Document
    • Technical writing guidelines
    • Requirements analysis
    • The role of modeling in requirements documentation
    • Use case and activity diagrams
    • Presenting requirements
  • Elicitation Techniques
    • Dealing with barrier to elicitation
    • Elicitation strategy
    • Elicitation techniques
    • Advantages and challenges of elicitation techniques
  • Introduction to Modeling
    • Documenting and tracking business rules
    • Why use models?
    • Modeling techniques
  • Managing Consensus
    • Communicating effectively
    • Effective consensus building
    • Validating Requirements
    • Validation techniques
    • Decision making and approvals
    • Managing change and risk post-validation
    • What happens next?
  • Roles, Definitions and Key Principles
    • Critical role of business analyst
    • Creating and adopting a formal documentation strategy
    • Key requirements documents
    • Roles and mutual expectations among team members
  • Types of Requirements
    • Attributed and types of effective requirements
    • What is an effective requirement?
  • Vision Scope and Quality

    Defining problem, vision, and scope

    Importance of a solution’s scope statement

    Documenting project vision and scope Including quality measures

    Managing change