Contact Us

Use the form on the right to contact us.

You can edit the text in this area, and change where the contact form on the right submits to, by entering edit mode using the modes on the bottom right. 

Informaticalaan 5
Delft, ZH, 2628 ZD
Netherlands

+31.15.301.0202

Agile Training

Agile Requirements Gathering & Modelling · R20

R20s.png
R20s.png

Agile Requirements Gathering & Modelling · R20

from 519.00

Duration: 2 days / 4 evenings / 14 hours 
Audience: BA, PO, ProdDes, UX, ScrumMstr, Dev, TestFunc

Learning Cases and Simulations:
Create an agile vision, derive epics and set release themes
Elicit data from end users and specify personas and scenarios
Create user stories with acceptance criteria
Drive backlog grooming in an agile team
Elaborate stories using various modelling techniques (e.g. use cases)
Size product backlog items with story points and perform ranking
✓ Obtain stakeholder feedback
Perform efficient change management

Event Date:
Register for Public Event

ELABORATION AND SPECIFICATION

5 · Writing User Stories and Backlog Management

  • What forms exactly 1 story?
  • Formats and key characteristics of high quality stories
  • Story acceptance criteria
  • Dealing with large and/or complex stories
  • Driving efficient backlog grooming sessions

6 · Backlog Grooming, Specification and Solution Design

  • Elaboration approaches suitable for agile projects
  • Scenario-based modeling
  • Non-functional specifications
  • Quantifying crisp business rules with stories

REQUIREMENTS MANAGEMENT

7 · From Requirements to Implementation

  • Upfront versus just-in-time modeling
  • Scrum Sprint Planning Meeting
  • Organization of spec items
  • Committing features to releases

8 · Change Management

  • Dealing with new ideas
  • Sources of requirements changes
  • Controlling and enabling change
  • Mechanisms to support triaging

SUPPORT

9 · Tools Support

  • Available tools for agile content management and story tracking
  • Tools evaluation criteria
  • Cases: Microsoft TFS and Atlassian Jira/Confluence

FOUNDATIONAL CONCEPTS AND PROCESS FRAMEWORK

1 · Requirements Engineering Essentials

  • Needs, features and software requirements
  • Traditional requirement types and artifacts
  • Dealing with needs changes
  • The relationship with user experience (UX)
  • Software requirements

2 · Agile Projects

  • Agile values, principles and techniques
  • Backlogs, prioritization and visibility
  • Requirements engineering elements in agile projects
  • Dealing with unknown needs and changes
  • Specific challenges for large systems and teams

ENVISIONING AND ELICITATION

3 · Project Scope and Business Requirements

  • Defining an agile vision
  • Epics: breaking the scope into logical sets of capabilities
  • Story mapping: a multi-dimensional product backlog with stories in context
  • Establishing business areas, goals and requirements
  • Framing requirements to support business strategy and customer justification

4 · Requirements Elicitation and Discovery

  • Stakeholder collaboration formats
  • User goals, scenarios and tasks
  • User stories
  • Personas: goals, characteristics and painpoints
  • Other story types