CS 2450 Product backlog, user stories, & acceptance criteria
What is the product backlog?
A list of features and functionalities for the project The team's to-do list
What is the purpose of Acceptance Criteria?
Acceptance criteria ensures that the correlated requirement has been met Acceptance criteria is a way of know that the user story is done Acceptance criteria ensure user stories are testable
Where are the details for a user story?
Added on the back of the card or listed with the acceptance criteria
Which phases of the SDLC have we been covering this semester?
Design Analysis
What is an upside to waterfall methodology
Excellent documentation
How does the scrum development methodology cycle through the phases of the SDLC?
It cycles through all the phases multiple times. Each cycle is only weeks long.
Phases of the SDLC are executed _________________.
It depends on which development methodology is used.
How does the waterfall development methodology cycle through the phases of the SDLC?
It does not cycle, it moves through each phase only one time.
What is are some positive results from a conversation elicited by the user story, remembering that user stories are supposed to help us dig into the product's details.
More requirements can be generated More user stories can be created based off of the detail gathered Positive & collaborative conversation between business analysts and the developers of the software
Why does the user story formula tend to work well?
They are simple to write & understand They are effective for team collaboration during planning and design They resolve communication issues by eliciting conversation about each given requirement
Why is it important to use a specific user role when writing user stories?
This helps the team have a shared understanding of who their customers are and creates buy-in and empathy The system most likely will have more than one contextual role A user story should elicit conversation, and as a designer of the system, you will need to know details for every kind of user
What is the product backlog used for?
To keep everyone on the same page A prioritized list of work To create design documents
Scrum is one variation of agile development out of many.
True
The analysis phase answers the questions of who will use the system, what the system will do, and where and when it will be used.
True
User stories are written from the perspective of ______________.
a user using the system
About how often are user story-writing workshops recommended?
about every three months
scrum is an example of ____ development
agile
Who are the creators of user stories
both, developers and business analysts
What is the downside to waterfall methodology
cannot get customer feedback while building
What is the first C of user stories?
card
What is the third C of user stories?
confirmation
What is the second C of user stories?
conversation
The story text we write in a user story is less important than the ___________ we have.
conversations
t/f User stories are only effective for expressing requirements using an agile development methodology.
false
An approach to continuously improving a concept, design, or product is a(n) _________ process
iterative
One of the reasons to use user stories is they support and encourage
iterative development
Phased development is an example of _____________ development
rapid development
The _____________ methodology has one criticism and that is that it does not easily scale up to large sized or mission critical projects.
scrum
While writing user stories it is likely the designer will think of additional functionality that could be added to the system. When that happens the designer is to
talk to the product owner about adding the functionality to the system requirements.
User stories promote more
talking
The parallel development methodology is different than the waterfall methodology because it breaks the project into smaller sections for _________________ .
the design and implementation phases.
t/f The product owner is responsible for the project's outcome
true
User stories are a technique for creating
units of work
What us the second way to get at the user story details?
write smaller stories