Skip to Main Content
Being Agile: Eleven Breakthrough Techniques to Keep You from “Waterfalling Backward”
book

Being Agile: Eleven Breakthrough Techniques to Keep You from “Waterfalling Backward”

by Leslie Ekas, Scott Will
October 2013
Intermediate to advanced content levelIntermediate to advanced
224 pages
7h 58m
English
IBM Press
Content preview from Being Agile: Eleven Breakthrough Techniques to Keep You from “Waterfalling Backward”

Why User Stories?

Agile teams tend to be familiar with user stories. Mike Cohn1 introduced them as a way to concisely describe functionality that would be valuable to a user, and they are a key agile practice. User stories emphasize feature essentials from the stakeholder’s view, helping to ensure that only what is needed is developed—and no more.

1. Cohn, Mike, 2010. User Stories Applied: For Agile Software Development. Pearson Education, Inc.

A user story takes the following format:

As a <role> I can <goal> so that <business value>

• The role is a specific stakeholder role that the story is targeted for.

• The goal is what the story will accomplish (not the “how”).2

2. A necessary comment here—one of the biggest problems we see with teams when ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Communicate with Teams More Effectively

Communicate with Teams More Effectively

Charles Humble

Publisher Resources

ISBN: 9780133375640Purchase book