Agile Requirements Management Training

Lesson 1 • Roles Involved in Requirements

Maps stakeholder roles—product owner, team, customer—to requirements responsibilities. Clarifies accountability gaps that cause requirement failures.

Lesson 2 • Common Requirements Failure Patterns

Catalogs recurring failure modes—ambiguity, gold-plating, scope creep—with root causes. Builds diagnostic awareness before introducing corrective techniques.

Lesson 3 • Agile Manifesto and Requirements

Connects the four Agile Manifesto values directly to requirements practices. Shows how each value reshapes how teams capture and validate needs.

Lesson 4 • Types of Agile Requirements Artifacts

Surveys epics, features, user stories, tasks, and acceptance criteria as a hierarchy. Prepares learners to select the right artifact for each context.

Lesson 1 • Story Smells and Anti-Patterns

Identifies technical stories, UI-driven stories, and conjunction stories as quality red flags. Provides rewrite strategies for each anti-pattern.

Lesson 2 • Story Splitting Techniques

Introduces nine splitting patterns—workflow steps, data variations, CRUD operations—to break large stories into deliverable slices. Prevents batch delivery anti-patterns.

Lesson 3 • The User Story Format

Teaches the As-a / I-want / So-that template and its rationale. Grounds story writing in user value rather than system behaviour.

Lesson 4 • INVEST Criteria for Stories

Applies the INVEST checklist—Independent, Negotiable, Valuable, Estimable, Small, Testable—to evaluate story quality. Each criterion is practised with real examples.

Lesson 1 • Backlog Structure and Hierarchy

Establishes the epic-feature-story-task hierarchy as the backlog's organising spine. Explains how hierarchy depth affects planning granularity.

Lesson 2 • Backlog Ordering Principles

Distinguishes ordering from prioritisation and introduces value, risk, and dependency as ordering drivers. Teaches techniques to sequence work for maximum learning.

Lesson 3 • Backlog Anti-Patterns and Debt

Identifies bloated, stale, and unordered backlogs as systemic risks. Provides pruning and archiving strategies to restore backlog integrity.

Lesson 4 • Backlog Refinement Process

Defines refinement as a continuous activity, not a single meeting. Establishes readiness criteria and cadence for keeping the backlog sprint-ready.

Lesson 1 • Elicitation Techniques Overview

Surveys interviews, workshops, observation, and surveys as elicitation methods. Matches each technique to context, stakeholder type, and information need.

Lesson 2 • Handling Conflicting Requirements

Provides frameworks for surfacing, categorising, and resolving stakeholder conflicts. Teaches negotiation moves that preserve relationships while reaching decisions.

Lesson 3 • Collaborative Story Mapping

Introduces user story mapping as a visual elicitation and organisation tool. Connects story maps to release planning and gap identification.

Lesson 4 • Validating Requirements with Stakeholders

Covers review walkthroughs, prototypes, and demos as validation mechanisms. Ensures requirements reflect actual stakeholder intent before development begins.

Lesson 1 • Release Planning Fundamentals

Defines release planning as scope-capacity-date negotiation across multiple sprints. Introduces rolling-wave planning to handle uncertainty at scale.

Lesson 2 • Sprint Planning Mechanics

Walks through sprint goal setting, story selection, and task breakdown in sprint planning. Connects planning outputs to daily execution and accountability.

Lesson 3 • Managing Scope Changes Mid-Sprint

Provides decision rules for accepting, deferring, or rejecting mid-sprint scope changes. Protects sprint integrity while remaining genuinely responsive to value.

Lesson 4 • Definition of Ready and Done

Establishes entry and exit criteria for stories entering and leaving a sprint. Prevents mid-sprint requirement churn and incomplete deliveries.

Lesson 1 • Embedding NFRs in Definition of Done

Adds NFR checks to the team's definition of done so quality is verified every sprint. Connects NFR compliance to continuous integration pipelines.

Lesson 2 • NFR Backlog Items and Enablers

Frames NFR work as enabler stories and architectural spikes in the backlog. Ensures NFR investment is visible, estimated, and prioritised alongside features.

Lesson 3 • Expressing NFRs as Constraints

Converts vague quality goals into measurable acceptance criteria and architectural constraints. Prevents NFRs from remaining aspirational and untestable.

Lesson 4 • Classifying Non-Functional Requirements

Categorises NFRs by quality attribute—reliability, scalability, security, usability. Establishes a shared taxonomy teams use to surface hidden constraints.

Lesson 1 • Documentation in Scaled Agile

Addresses documentation needs when multiple teams share requirements across programmes. Introduces shared glossaries and cross-team traceability conventions.

Lesson 2 • Traceability in Agile Contexts

Reframes traceability as impact analysis and change navigation rather than compliance paperwork. Identifies when traceability adds value vs. waste.

Lesson 3 • Lightweight Documentation Strategies

Applies just-enough documentation principles—decision logs, ADRs, story annotations. Prevents documentation debt without sacrificing institutional knowledge.

Lesson 4 • Linking Stories to Business Goals

Maps user stories upward to features, epics, and strategic objectives. Ensures every backlog item has a traceable line to measurable business value.

Lesson 1 • Requirements-Focused Retrospectives

Designs retrospective formats that surface requirements-specific pain points and experiments. Prevents generic retrospectives from missing requirements root causes.

Lesson 2 • Scaling Requirements Improvement

Extends improvement practices across multiple teams through communities of practice and shared standards. Prevents siloed improvement that fails to compound.

Lesson 3 • Measuring Requirements Quality

Introduces defect origin analysis, rework rates, and story rejection rates as quality signals. Connects measurement to targeted improvement actions.

Lesson 4 • Building a Requirements Capability Roadmap

Synthesises all course learning into a personal and team capability roadmap. Provides a structured path from current state to requirements mastery.