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

Agile Stories

No description
by

Jason Waack

on 12 October 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Stories

Title = Role + Action
As a WHO
I want WHAT
So that WHY
Acceptance Criteria:
Statement - test / business rule / note
Senario - Given When Then
Table
Allows for relevance and understanding of stories to evolve
with passage of time and based upon the experience gained by prior deliverables.
production quality
details fleshed out
negotiated
conversation
optimized
Agile Stories
"represent customer requirements
rather than document them."
- Rachel Davies
Created
Prioritized
Groomed
Implemented
w/ expectation of change
start out at a high level and coarse grained
in language of the business
in context of users and benefit it provides
focus on WHAT need is over how it is solved
WHO
WHY
continually reproritized
by business value
opportunity to learn
minimum valuable product
differentiating features
risk
with consideration of cost
iteratively
at most responsible moment
higest value stories first
clarrify understanding by
conversation
consideration of user feedback
captured as acceptance criteria
split in smaller stories
expose value
better estimate
surface inner detail
size implementable in a few days
iteratively
Annotated wireframe or comp
sized (estimate)
Code-Breaker Submits Guess
The code-breaker submits a guess of four numbers. The game marks the guesswith + and - signs.

For each number in the guess that matches the number and position of a numberin the secret code, the mark includes one + sign. For each number in the guessthat matches the number but not the position of a number in the secret code,the mark includes one - sign.
Scenario Outline: submit guess
Given the secret code is "<code>"
When I guess "<guess>"
Then the mark should be "<mark>"
Scenarios: no matches
| code | guess | mark |
| 1234 | 5555 | |

Scenarios: 1 number correct
| code | guess | mark |
| 1234 | 1555 | + |
| 1234 | 2555 | - |

Scenarios: 2 numbers correct
| code | guess | mark |
| 1234 | 5254 | ++ |
| 1234 | 5154 | +- |
| 1234 | 2545 | -- |

Scenarios: 3 numbers correct
| code | guess | mark |
| 1234 | 5234 | +++ |
| 1234 | 5134 | ++- || 1234 | 5124 | +-- || 1234 | 5123 | --- |Scenarios: all numbers correct| code | guess | mark || 1234 | 1234 | ++++ || 1234 | 1243 | ++-- || 1234 | 1423 | +--- || 1234 | 4321 | ---- |
From The RSpec Book by David Chelimsky p51.
Story Template
Acceptance Criteria
Automated Testing
Sprint
0
Create Initial
Product Backlog
Backlog Grooming
Planning
as a brief statement about a need
for later ellaboration
Intent
Conversation
Acceptance Criteria
acting as a a placeholder for fututure conversations
evocative, resulting in recall of prior coversations on details
where conversation is a more valuable medium than documentation
Additional Detail
name it
Story
Full transcript