Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Death by User Story

User Stories are a universally adopted technique for agile teams
by

Brindusa Axon

on 30 September 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Death by User Story

Brindusa Axon
@gbrindusa

Death by User Story
How to break free?
Agile Product Management
Naive conversion of requirements documents to stories
Deadly anti-patterns
- business value thinking vs schedule driven thinking
User Story
the workhorse of agile development
tool for building product backlog
the basic unit of work for a team
container that carries the value stream to the user
lightweight and effective approach to managing requirements for a system
help bridge the developer-customer communication gap
a metaphor for our entire incremental value delivery approach
User Story
Re-work and bugs
Unmet expectations
Disappointed stakeholders, customer, clients, users
Failure
Delayed projects
Rejected demoes
Unsatisfied teams
What is a user story?
A brief statement of intent that describes something that the system needs to do for an user.
As a <role>, I want <goal/desire> in order to <benefit>.
Business domain
(requirement)
Technical domain
(solution design)
the story unites the requirement with the agreed solution
Idea
Need
Problem
Requirement
"In order to ..."
Conversation
Solutions
Options
Design sketch
"I want ..."
Envisioning seminars
Requirements workshop
Grooming sessions
Bug backlog
Acceptance Criteria
Acceptance tests
Examples
In order to <receive benefits> as a <role> I want <goal/desire>.
As <who> <when><where><what> because <why>.
Mike Cohn / Connextra
Chris Matts
Five Ws
Story Elements
Story Attributes
C
ard
C
C
onversation
onfirmation
I
N
V
E
S
T
ndependent
egotiable
aluable
estimatable
mall
estable
Where does it all go wrong?
Story Map
Story Mind Map
Product Backlog list
Incremental package building vs value delivery
Statements without confirmation
&
Solutions without conversation
Misuse of priorities and value
Visual design isn't the whole story
Cultivate:
- shared understanding of user stories - purpose and benefits
Measure
Don't start with User Stories!!!
- holistic approach vs linear approach
Refactor
Whole team approach
Experiment
Full transcript