The document discusses user stories and how they can be used to develop acceptance criteria and test scenarios for a team scoring feature in a game. It provides an example user story of wanting to introduce competitive elements by allowing teams to earn points for correct answers. Accompanying acceptance criteria and test scenarios are presented to validate the difficulty-based scoring system. Examples are also used to illustrate the acceptance criteria and help explore the different scoring outcomes.

1. Let me tell you a story
Seb Rose
Claysnow Limited
@sebrose
Tuesday, 22 April 14

2. Tuesday, 22 April 14

3. Tuesday, 22 April 14

4. VISA subscriptions
In order to increase subscriptions
visitors should be able to
subscribe online with a VISA card
Tuesday, 22 April 14

5. “User stories are slippery,
Tuesday, 22 April 14

6. “User stories are slippery,
so we call them Product Backlog Items”
Tuesday, 22 April 14

7. We never
finish them in an
iteration
How do I trace
them to features
Hard to estimate
Not enough detail
to start coding
Nothing I can test
Difficult to
prioritise
Tuesday, 22 April 14

8. As a <role>
I want to <do something>
So that <I get some value>
Tuesday, 22 April 14

9. In order to <get some value>
<role> should be able to
<do something>
Tuesday, 22 April 14

10. Tuesday, 22 April 14

11. “A
boundary
object
is
a
concept
in
sociology
to
describe
informa7on
used
in
different
ways
by
different
communi7es.
They
are
plas7c,
interpreted
differently
across
communi7es
but
with
enough
immutable
content
to
maintain
integrity”
-­‐-­‐Wikipedia
User Stories are Boundary Objects
Tuesday, 22 April 14

12. -- Leigh & Griesemer
Tuesday, 22 April 14

13. “They are weakly structured in common
use, and become strongly structured in
individual-site use. They may be abstract or
concrete.
-- Leigh & Griesemer
Tuesday, 22 April 14

14. “They are weakly structured in common
use, and become strongly structured in
individual-site use. They may be abstract or
concrete.
They have different meanings in different
social worlds but their structure is common
enough to more than one world to make
them recognizable means of translation.
-- Leigh & Griesemer
Tuesday, 22 April 14

15. “They are weakly structured in common
use, and become strongly structured in
individual-site use. They may be abstract or
concrete.
They have different meanings in different
social worlds but their structure is common
enough to more than one world to make
them recognizable means of translation.
The creation and management of boundary
objects is key in developing and maintaining
coherence across intersecting social worlds.”
-- Leigh & Griesemer
Tuesday, 22 April 14

16. Tuesday, 22 April 14

17. http://www.agileproductdesign.com/blog/dont_know_what_i_want.html
Depth first (incremental)
Tuesday, 22 April 14

18. http://www.agileproductdesign.com/blog/dont_know_what_i_want.html
Breadth first (iterative)
Tuesday, 22 April 14

19. Iterative and Incremental
http://itsadeliverything.com/revisiting-the-iterative-incremental-mona-lisa
Tuesday, 22 April 14

20. Parallel development
Tuesday, 22 April 14

21. The one where...
User stories &
acceptance
criteria
Examples
Tuesday, 22 April 14

22. The one where...
User stories &
acceptance
criteria
Examples
Tuesday, 22 April 14

23. The one where...
User stories &
acceptance
criteria
Examples
Open
questions
Tuesday, 22 April 14

24. The one where...
User stories &
acceptance
criteria
Examples
Open
questions
Domain
learning
Tuesday, 22 April 14

25. Tuesday, 22 April 14

26. •Must support VISA
•Does not need to support MasterCard, Switch
•...
•Customers should be prevented from entering
invalid credit card number
• ...
Credit Card Processing
Acceptance criteria:
Tuesday, 22 April 14

27. The one where ....
... we validate content of the card number
User Enters Outcome
@£$%@£$%@£$%@£$% Error message
4575 9879 6752 1245 Error message
4.57599E+15 OK
Tuesday, 22 April 14

28. Acceptance
Criteria
(Rules)
Examples
User Story
Tuesday, 22 April 14

29. Acceptance
Criteria
(Rules)
ExamplesExamples help us toexplore and test theacceptance criteria
together
User Story
Tuesday, 22 April 14

30. Tuesday, 22 April 14

31. In order to introduce a
competitive element
participants should be able to
get points for a successful
answer
SCORING THE GAME
Tuesday, 22 April 14

32. Get points for a correct answer
Acceptance criteria:
Tuesday, 22 April 14

33. Is it only the first
team that gets the
answer right that
scores?
Do teams start
with a score of 0?
Are all answers
worth the same?
Can the score be
negative?
What happens if the
answer is wrong?
Tuesday, 22 April 14

34. Teams start with a score of 0
Acceptance criteria:
Correct answers score points
Incorrect answers lose points
Score can’t be negative
Points awarded decrease ...
Tuesday, 22 April 14

35. Teams start with a score of 0
Acceptance criteria:
Tuesday, 22 April 14

36. Feature: Team Scoring
Teams start with zero score
Scenario: Score starts at 0
Given I register a team
When I retrieve my score
Then my score is 0
Tuesday, 22 April 14

37. Tuesday, 22 April 14

38. Correct answer gets 10 points
Acceptance criteria:
Tuesday, 22 April 14

39. Feature: Team Scoring
Teams start with zero score
Correct answer gets points
Scenario: Score starts at 0
Given I register a team
Then my score is 0
Scenario: Correct answer gets 10 points
Given I register a team
When I submit a correct answer
Then my score is 10
Tuesday, 22 April 14

40. Points awarded for an answer
depend on its difficulty
Acceptance criteria:
Tuesday, 22 April 14

41. Teams start with zero score.
Correct answer gets points depending on
how difficult it is.
Scenario: Score starts at 0
Scenario: Correct easy answer scores 10
Given I register a team
When I submit a correct easy answer
Then my score is 10
Scenario: Correct hard answer scores 50
Given I register a team
When I submit a correct hard answer
Then my score is 50
Tuesday, 22 April 14

42. Acceptance
criteria
User Story
Examples
Feature: Team Scoring
Teams start with zero score.
Correct answer gets points depending on
how difficult it is.
Scenario: Score starts at 0
Given I register a team
Then my score is 0
Scenario: Correct easy answer scores 10
Given I register a team
When I submit a correct easy answer
Then my score is 10
Scenario: Correct hard answer scores 50
Given I register a team
When I submit a correct hard answer
Then my score is 50
Tuesday, 22 April 14

43. Acceptance
criteria
User Story
Examples
Feature: Team Scoring
Teams start with zero score.
Correct answer gets points depending on
how difficult it is.
Scenario: Score starts at 0
Given I register a team
Then my score is 0
Scenario: Correct easy answer scores 10
Given I register a team
When I submit a correct easy answer
Then my score is 10
Scenario: Correct hard answer scores 50
Given I register a team
When I submit a correct hard answer
Then my score is 50
Tuesday, 22 April 14

44. Acceptance
criteria
User Story
Feature: Team Scoring
Teams start with zero score.
Correct answer gets points depending on
how difficult it is.
Scenario: Score starts at 0
Given I register a team
Then my score is 0
Scenario: Correct easy answer scores 10
Given I register a team
When I submit a correct easy answer
Then my score is 10
Scenario: Correct hard answer scores 50
Given I register a team
When I submit a correct hard answer
Then my score is 50
Tuesday, 22 April 14

45. Acceptance
criteria
User Story
Feature: Team Scoring
Teams start with zero score.
Correct answer gets points depending on
how difficult it is.
Scenario: Score starts at 0
Given I register a team
Then my score is 0
Scenario: Correct easy answer scores 10
Given I register a team
When I submit a correct easy answer
Then my score is 10
Scenario: Correct hard answer scores 50
Given I register a team
When I submit a correct hard answer
Then my score is 50
Tuesday, 22 April 14

46. User Story
Feature: Team Scoring
Teams start with zero score.
Correct answer gets points depending on
how difficult it is.
Scenario: Score starts at 0
Given I register a team
Then my score is 0
Scenario: Correct easy answer scores 10
Given I register a team
When I submit a correct easy answer
Then my score is 10
Scenario: Correct hard answer scores 50
Given I register a team
When I submit a correct hard answer
Then my score is 50
Tuesday, 22 April 14

47. User Story
Feature: Team Scoring
Teams start with zero score.
Correct answer gets points depending on
how difficult it is.
Scenario: Score starts at 0
Given I register a team
Then my score is 0
Scenario: Correct easy answer scores 10
Given I register a team
When I submit a correct easy answer
Then my score is 10
Scenario: Correct hard answer scores 50
Given I register a team
When I submit a correct hard answer
Then my score is 50
Tuesday, 22 April 14

48. Feature: Team Scoring
Teams start with zero score.
Correct answer gets points depending on
how difficult it is.
Scenario: Score starts at 0
Given I register a team
Then my score is 0
Scenario: Correct easy answer scores 10
Given I register a team
When I submit a correct easy answer
Then my score is 10
Scenario: Correct hard answer scores 50
Given I register a team
When I submit a correct hard answer
Then my score is 50
Tuesday, 22 April 14

49. -JVM
Seb Rose,
Tuesday, 22 April 14

50. -JVM
Seb Rose,
Available 2014
(hopefully)
Tuesday, 22 April 14

51. Seb
Rose
TwiBer:
@sebrose
Blog:
www.claysnow.co.uk
E-­‐mail:
seb@claysnow.co.uk
Tuesday, 22 April 14