Program Management Curriculum Hero Image
Developing Agile 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
Instructor-Led Training 15 13 1 1 0 0 13 0 12
Virtual Instructor-Led Training 15 13 1 1 0 0 13 0 12
Delivery Method Instructor-Led Training Virtual Instructor-Led Training
PDU Total 15 15
Technical PMP/PgMp 13 13
Leadership 1 1
Strategy 1 1
PMI SP 0 0
PMI ACP 13 13
PfMP 0 0
PMI PBA 12 12
  • CEUs: 1.5
  • CPEs: 18
  • Field of Study: Business Management and Organizations

Among the leading causes of project failure are unclear or undefined requirements. It is crucial that everyone associated with a project understands how to gather and manage requirements to ensure a successful project outcome.

This course focuses on the processes of requirements gathering, communication and prioritization in an Agile environment. It is geared towards providing critical information to those who serve in the role of product owners and to those who support the work of fulfilling requirements as development team members. You will cover visual modeling and tips on how to engage stakeholders. You will understand how to differentiate the levels of requirements and how to gather the right level at the right time. This course is designed to be interactive. Participants will learn how to read into the full extent of what stakeholders are saying, so no requirements are overlooked.

Requirements of excessive size or quantity can also hinder a project’s realization. You will learn how to break down hefty requirements and prioritize so no essential requirements are missed.

No project can succeed without properly defined and prioritized requirements. Be sure you know how to gather and manage these vital components of the project process.

  • Address requirements challenges from the perspective of the product owner
  • Apply principles of the Kanban and Lean methodologies to Agile project work
  • Analyze stakeholders and their role in project requirements
  • Define the Product vision and the customer’s “Conditions of Satisfaction”
  • How to maintain and continually prioritize requirements as the Product Owner
  • Use facilitation and elicitation techniques for Requirements Gathering
  • Identify non-functional/technical requirements
  • Describe when a requirement is “done”
  • Explain the User Acceptance tests and effective process modeling
  • Use business value points and dependency for prioritization
  • Brainstorm and consolidate features of requirements as well as break down large requirements

This course uses digital materials.

  • Introduction
    • Speaker
    • Course Scope
    • Course Objectives
    • Participant Introductions
  • Overview of Agile and Agile Requirements
    • Agile Value Proposition
    • When to Use Agile
    • Agile & Waterfall
    • Traditional and Agile Project Constraints
    • Challenges with the Waterfall Approach
    • The Agile Manifesto
    • Agile Principles
    • The Agile Project Lifecycle
    • Engaging Through the Lifecycle
    • Traditional Roles and Responsibilities vs. Agile Ones
    • Major Methodologies
    • Scrum
    • Lean
    • What is Waste?
    • Kanban
    • Agile Approach to Requirements
    • Six Levels of Agile Planning
    • Work Items in Agile
    • Product Backlog
  • Product Vision
    • What Do Customers Really Want?
    • How Value Flows and is Broken Down
    • What Is the Vision?
    • Delivering the Vision
    • Cut Scope Creep by Modeling Early!
    • Conditions of Satisfaction and Definition of Done
    • Knowing When to Stop
    • Sample Conditions of Satisfaction
    • User Roles and Personas
    • Steps for Identifying User  Roles
    • Personas
    • Creating a Backlog
    • Backlog Prioritization
    • Building a Product Roadmap
    • Slices of Functionality
    • Using Business Value Buckets
    • MoSCoW
    • Kano
    • Dependency Prioritization
  • High-Level Requirements
    • Agile Requirements Principles
    • Understanding the Problem Domain
    • Traditional vs. Agile Requirements
    • The Levels of Requirements
    • Creating a Roadmap: Generating Themes and Epics
    • Requirements Visioning
    • Identifying Requirements
    • High-Level Use Case Diagrams
    • User Interface Flow
    • Stakeholder Management: Identifying the Right Stakeholders
    • Agile Requirements Elicitation Techniques
    • Dealing with Technical Debt
    • Causes of Technical Debt
  • Requirements Breakdown
    • What Is a User Story?
    • What Makes a Correct User Story?
    • User Story Structure
    • Value Stream
    • User Story's Definition of Done
    • Definition of Done and Kanban Boards
    • Why Does DoD Matter so Much?
    • Generating User Stories
    • How Do Stories Appear?
    • Brainstorming Techniques
    • Story Mapping
    • Slicing Large User Stories
    • Breaking Down the Epics
    • Sample Compound Stories
    • Sample Complex Stories
    • Techniques for Slicing Stories
    • Process-based Breakdown
    • CRUD – Function-based Breakdown
    • Business Rule Breakdown
    • User- or Platform-based Breakdown
    • Technical User Stories and Spike Stories
    • Nonfunctional Requirements
    • What is a Technical User Story?
    • Where is the User?
    • Technical Stories and Technical Debt
    • Spikes
    • Tracking Progress
    • Track User Stories
    • Track Tasks
    • Burn Downs and Burn Ups
  • Deep Dive (Testing and Acceptance Criteria)
    • Knowing When to Stop
    • Requirements Deep-Dive
    • Where Are the Story Details?
    • Who Does What?
    • “Team Members” Over “Functional Roles
    • A New Approach to Quality Management
    • Agile Quality Management
    • Testing Management
    • Principles for Successful Testing
    • Agile Testing Quadrants
    • Identifying Acceptance Tests
    • Types of Testing
    • Example: User Story Testing
    • Example: Regression Testing
    • Example: Integration Testing
    • Examples of Other Tests
    • Sample Acceptance Test Cases
    • Business Rules
    • The “Traceability” Question
    • Test-Driven Development (TDD)
    • Behavior-Driven Development (BDD)