User Stories Flashcards
What is the difference between requirements of a project in Scrum versus Waterfall?
Waterfall, all requirements are known up front. Scrum the user stories are developed over time as the knowledge of the solution increases.
In a Scrum project, are requirements completely known up front?
No they are not known. Some may be added or removed as the project progresses or the market needs change.
How do requirements emerge in a scrum project?
Through conversations with customers, end-users and stakeholders.
What is the definition of a user story?
Represents a small unit of work that has some value to an end-user or customer and can be addressed or delivered at the end of a sprint or a series of sprints.
Whose voice should user stories reflect?
Voice of the customer
What is a typical format of a user story?
As [user role], I want to [goal] so that I receive [benefit]
What are some tests that can be applied to determine a user story is created adequately?
- Offer value to the customer or end-user
- Must be estimable
- Testable
What are sources user stories when working in a project?
- Customers/users
- Internal team members
- Social media/internet reviews
What 2 items should be determined about each user story to help understand their importance and prepare them for the sprint backlog?
Effort
Priority
What is the reason for discussing and validating each user story?
Reach a common understanding and verify that it contributes to the vision. It describes what needs to be done to deliver it.
What is the evolution of user stories from the beginning to the end of the project?
They tend to start as high level stories that are then broken down into more focused user stories.
What is the term that is used to refer to high level user stories?
Epics
In a waterfall approach, are all requirements equal?
Yes they are.
What does it mean to have just in time user stories?
Collecting and creating just before they are needed in the planning process.
