4.5.1 Collaborative User Story Writing Flashcards

1
Q

A user story represents a feature that will be valuable to either a “ “ or “ “ of a s…

A

user
purchaser
system or software.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

User stories have 3 critical aspects (3 Cs):
- Card - the “ “ describing a … (an i… an entry in an e…
- Conversation - explains how the “ “ will be “ “ (can be d…
- Confirmation - the a…

A
  • Card - medium
    user story
    index card,
    electronic board)
  • Conversation - software
    used
    documented or verbal)
  • Confirmation - acceptance criteria
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Most common format for a user story is:

“As a “ “, I want [goal to be “ “, so that I can [resulting business value f…”, followed by a…

A

[role],
[accomplished],
[for the role],”
acceptance criteria.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Collaborative authorship of the user story can use techniques like “ “ and m…

A

brainstorming
mind mapping.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

The collaboration allows the team to obtain a shared vision of w… by taking into account 3 perspectives:
- b…
- d…
- t…

A

what should be delivered

  • business
  • development
  • testing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Good user stories should be (INVEST):
- i…
- n…
- v…
- e…
- s…
- t…

A
  • Independent
  • Negotiable
  • Valuable
  • Estimable
  • Small
  • Testable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

If a stakeholder doesn’t know how to test a user story, this may indicate that the u… is not c… , or that it doesn’t reflect something v… , or that the “ “ just needs help in “ “.

A

user story
clear enough
valuable to them
stakeholder
testing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly