Agile Requirements In Depth

Earl BeedeConstrux Senior Fellow

This course dives into techniques for developing requirements on Agile projects, including the Agile Work Breakdown Structure (WBS), story mapping to define project scope, writing user stories, sizing stories (agile estimation), and developing acceptance criteria for user stories.

5 Hours of Content
10 Lectures
Purchase Options

Course Details

  • Overview

    Agile development shifts traditional requirements work to a “just in time” approach. How does this affect good requirements practices? This class explains Agile approaches to traditional requirements sources including MRDs, PRDs, feature lists, and user scenarios. It dives into techniques for developing requirements on Agile projects, including the Agile Work Breakdown Structure (WBS), using story mapping to define the scope of the project, writing user stories, sizing stories (agile estimation), and developing acceptance criteria for user stories.

    Certification Information

    5 PDU’s
    PMI PDU Reporting Instructions

    Who Should Attend

    This seminar is for Scrum Masters, Product Owners, business analysts, requirements analysts, technical product managers, technical program managers, test leads, and anyone else who provides input to software developers.

  • Course Details

    What Are We Trying to Build?

    • It all starts with the Product Vision
    • Characteristics of good Product Visions

    Software Requirements: What and Why

    • What is a requirement?
    • The Product Vision as the top-level requirement
    • Three purposes of requirements
    • Using requirements to manage risk
    • Product versus project requirements
    • Potentiallly useful requirements artifacts
    • Working software as the ultimate requirements specification

    Initial requirements gathering

    • Envisioning the high level requirements
    • What can I do with it: high-level user stories and story mapping
    • How it works: business rules and the domain model
    • How it looks: low-fidelity UI models and workflows

    Just-in-time Requirements Elaboration

    • No requirement before its time: the concept of the last responsible moment
    • Requirements elaboration during iteration planning

    Requirements Change Management

    Requirements Validation

    • Acceptance criteria
    • The Definition of Done and why it matters


  • Earl Beede

    Construx Senior Fellow

    Earl Beede, CSDP is a Senior Fellow at Construx Software, where he designs and leads seminars and provides consulting services on early project-lifecycle practices, estimation, requirements, quality assurance, contract management, and software methodologies.

    With more than 20 years experience as a quality assurance representative, systems analyst, process architect, and manager, Earl has designed and written software development processes for companies across a wide variety of industries. Prior to joining Construx, he held quality assurance and systems analyst positions at organizations that include the Department of Defense, Boeing Computer Services and Verizon Wireless.

    Earl has a Bachelor’s degree from the University of Washington. He is a member of the IEEE Computer Society and a past coordinator of the Seattle Area SPIN (Software Process Improvement Network).

Purchase Options

Single License

$399

Start Training Today

Get unlimited access to this online course for an entire year.

BUY NOW

Single All Access Pass

$599

Save 60%

Access this course along with ALL other Construx OnDemand Content.

BUY NOW

Team License

$249

Discounts Start At 10%

Need 10 or more seats? Contact us to learn how much you can save!

CONTACT US

Team All Access Pass

$599

Best Savings

The more seats you need, the more you save! Contact us for info.

CONTACT US

Start Your Free Trial

Try a free preview of the entire Construx OnDemand Catalog.

TRY NOW