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. Concepts are illustrated through extensive use of hands-on labs. 

2-day seminar

Highlights 

  • Software Requirements: What and Why
  • Initial Requirements Gathering
  • Just-in-Time Requirements Elaboration
  • Requirements Change Management
  • Requirements Validation

 

Reviews

"Excellent material and presentation. The formal presentation of the principles and techniques provides me with quite a number of takeaways to go back to the office. We have much to learn as we look to improve our execution both with the Software Division and the rest of the company."  -- Christopher Scharver, Mechdyne Corporation

"Instructor was very knowledgeable and interested in making the course useful for our organization."  -- Margarita Medina, Seattle Public Schools

"Instructor was excellent. Course is geared toward product owners, so some of it was outside my universe, but it was both informative and fun."  -- Fred Hagan, Starbucks

"Time will spent."  -- Adam Perry, ON24

 

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.

Certification Information

14 PDU

PMI PDU Reporting Instructions

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

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, ...

John Clifford

John Clifford is a Senior Fellow and Agile Practices Lead at Construx Software. John got his first software development job at a startup, while still in college, ...

Melvin Perez-Cedano

Melvin Pérez-Cedano is a Senior Fellow at Construx Software where he provides training and consulting services that help organizations and individuals to successfully ...