User Stories and Estimations Flashcards
According to the Agile Alliance, a User Stories is a (2 words) __________________ that contributes (1 word) ____________________.
Functional Increment
Value
Who is the Author of User Stories Applied?
Mike Cohen
Fill in the blanks:
Mike Cohen defines a user story as a “________, _________ description of a ___________ from the perspective of the person who desires the new capability. Usually a _________ or __________ of the system.
Short
Simple
Feature
User
Customer
True or False:
A user story is NOT a use case or scenario with the Unified Process describing the most common successful interaction (success scenario) between a system and one or more actors and alternative paths.
True
What are the common sources of User Stories?
The product backlog items and includes features, enhancements and fixes.
True or False:
The three benefits of User Stories are:
That they are large and conducive to a traditional environment.
That they defer the capturing of details.
That they are large and allow for planning and estimation.
They promote verbal communication from both the business and technical teams (common understanding).
Focus on the user’s system and its attributes.
False:
The three benefits of User Stories are:
That they are small and conducive to an agile environment.
That they defer the capturing of details.
That they are small and allow for planning and estimation.
They promote verbal communication from both the business and technical teams (common understanding)
Focus on the user’s system and its attributes.
List the Three C’s of User Story Components
A card with just enough text to describe user story requirements.
A conversation that encourages the exchange of thoughts, opinions and feelings.
Confirmation, or the validation of acceptance criteria.
What are the two additional Cs in the User Story Life Cycle?
Construction (actual construction and implementation)
Consequences (results in new user stories or refinements)
Describe the three parts of the “role, feature, reason” format of a User Story.
Who: As a/an (user role or type of user)
What: I can/I want (some service or functionality, or goal)
Why: So that (the reason, business value of benefit that is achieved)
True or False:
Common user story gathering techniques are Observation, Questionnaires, Stakeholder interviews, and Story writing workshops.
False
Common user story gathering techniques are Observation, Questionnaires, USER interviews, and Story writing workshops.
Questionnaires are best used when in User Stories?
When you need additional information, such as to prioritize stories. They are not recommended as an initial approach because they lack feedback.
Describe why User Story writing workshops are the most effective method of creating user stories.
They are very effective at capturing, categorizing and prioritizing user stories. This method involves all key stakeholders, clients, end users, development teams, business managers, and Product Owners.
Describe the user interview method of creating user stories.
It is the default approach where a user that is a good representative of the identified role answers open-ended questions to capture maximum input.
True or False:
The Agile Alliance describes personas as the synthetic biographies (profiles) of fictious users of the (project’s) future product.
True.
True or False:
Personas can be composites of multiple users, rarely considered extreme characters and are concise and visual.
True.
Fill in the blanks:
Identifying personas includes _____________, _____________, Surveys, focus groups and _____________.
Brainstorming.
Interviews
Shadowing.
Describe the format of developing a persona.
Starting with a picture and adding a descriptive persona name, the persona format identifies:
the Goals,
motivations and objectives,
problems that need solving, and
the expected benefits.
And captures relevant characteristics that consider:
Job
Tasks
Lifestyle
Attitudes and
Demographics.
