User Stories - Driving Requirements with Agility

Who Should Attend/Prerequisites

• Product managers, developers, testers, people managers, customer proxies
• Teams new to agile or considering agile product development
• Teams seeking a better way to elicit and clarify requirements

Class Size Limit: 40 (Minimum 10)

Course Overview

Eliciting and managing project requirements is often challenging for product owners and development teams. The course covers in detail a proven Agile Method of managing requirements – the User Story. Attendees completing this course will be ready to introduce or refine their use of User Stories as an excellent means of managing requirements with agility.

User stories are inexpensive, low fidelity, simple, and brief descriptions of functionality from the user’s point of view. The promise of User Stories is that development teams can begin writing and demonstrating working code very early in the project lifecycle.

The course ends with an introspective discussion of the audience’s current challenges and how User Stories can help improve your ability to impact the bottom line. The course is participatory and uses many exercises to instill a deep understanding of how to find, create, manage, track, estimate, and derive velocity of User Stories.

The following topics are covered:

·         Origins

·         Position in software lifecycle

·         Customer proxy role

·         Product owner role

·         How to write a user story

·         Role of acceptance test cases

·         Good and bad user stories

·         Granularity

·         Tracking user stories

·         Managing requirement changes with user stories

·         User story workshops

·         Estimating user stories

·         Planning poker

·         Establishing team velocity

·         Iteration planning using user stories

·         Release planning using user stories

·         Predicting release content

·         Business impact and ROI

·         Introspection & challenge

Agenda

Origins of user stories

Position in software lifecycle

Roles: customers, stakeholders, product owner, developers, testers

How to elicit requirements

How to write a user story

                Exercise

Card – Conversation – Confirmation

Acceptance test cases

Good user stories – the INVEST acronym

Bad user stories

                Exercise

User story workshops

                Exercise

Collaborative trolling for additional requirements

Tracking user stories

Product backlog

                Exercise

User story board

                Exercise

Managing requirement changes with user stories

                Exercise

Granularity

Estimating user stories

Planning poker

                Exercise

Calculating team velocity

                Exercise

Iteration planning using user stories

Release planning using user stories

                Exercise

Predicting release content

Business impact and ROI

Introspection, Challenge, & Commitment

Cost:

$695 per attendee.