User Stories Flashcards
What is broken down into user stories?
A feature
How are features prioritized?
According to customer value
How long is a sprint?
Typically, can be 2 weeks or 4 weeks depending on what the team decides.
What is a user story?
Similar to a work package - it’s the smallest piece, decomposed, that a person or team can work on.
What are the 3 Cs of user story creation?
Card, conversation, and confirmation
What is a card?
Typically, a tile shown on a kanban board represents a user story.
Conversation
Conversations that occur between customers or users, developers and testers, and triad or three amigos to work through the requirements, solution, and acceptance test criteria.
Confirmation
Confirming that the item meets the requirements, the customer can sign off, showcase the increment at the sprint review, and ensure a definition of done is in place.
Definition of ready (user story)
The team’s criteria for when a user story is ready to be analyzed or developed
Definition of done (user story)
Team’s criteria for when a user story is complete.
What does INVEST stand for?
Independent, negotiable, valuable, estimable, small, and testable
Independent
The user story should be a usable piece, independent of others, that we can demonstrate at the end of a sprint.
Negotiable
We should be able to negotiate the requirements and solution or even move them out of the sprint if necessary.
Valuable (or vertical)
The item should have customer value, and be a vertical slice.
Estimable
The item’s effort should be able to be estimated by the team.
Small
It should be small enough to be completed in a sprint.
Testable
Often we write the tests or the acceptance criteria first.
Behavior driven development
Born out of automated testing and test driven development (TDD)
What does TDD stand for?
Test-driven development
What does BDD stand for?
Behavior-driven development
What is test-driven development?
The team agrees on the acceptance criteria for the work, writes the test first, ensures the test fails, and then writes the code to pass the test. Tests are often automated or part of writing code.
Red refactor
Test fails –> write code
Green refactor
Test passes
Refactor
Tidy up the code
Behavior-driven development (BDD)
Given a condition when something happens, I want this to happen, describing the acceptance criteria from the user’s perspective. Often automated tests.
User-based acceptance criterias
Can be done in many different ways - describe what needs to be done. As a role I want something to happen so I can my objective.
