User Stories Flashcards

1
Q

What are User Stories?

A

Stories that explain a specific action a certain type of user can take within your application.

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

User stories are part of the _____ methodology.

A

Agile

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

What is the goal of User Stories?

A

To distill your requirements down to small, readable and executable parts.

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

User stories are a great tool for simplifying what?

A

product requirements

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

As a , I want to , so that .

A

As a , I want to , so that .

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

The in the user story defines what?

A

The goal that your user has.

This can be based on a feature you would like to develop.

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

What is a feature?

A

A distinctive attribute or element of a website or app that helps a user achieve their goal.

  • Features can be anything from auto-saving when writing an email to allow users to leave a review on a product they’ve purchased.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

The

A

Describes the benefit or motivation behind the user completing their action. What’s in it for them?

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

What are user stories ultimately translated into?

A

Visual user flows

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

What is visual user flows?

A

Diagrams that show how a user makes their way through a feature of your software.

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

When do user stories come into play?

A

After conducting your user research, performed your competitive analyses, and defined your business requirements.

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

What is the main goal of user stories?

A

To divide your work up into reasonable chunks.

For example, once you’ve exhausted all user stories and divvied them up amongst the team, it’s much easier to gauge how low a development cycle will take.

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

What are job stories?

A

Focuses on the context in which a persona wants to complete a particular action.

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

When are job stories more useful than user stories?

A

When context is more important than the individual characteristics of your users and can help designers focus on answering the “Why” in regards to a particular situation or motivation.

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

What is the semantic structure of a job story?

A

When , I want to , so I can .

eg.)
When <i>, I want to , so I can .</i>

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

When it comes to writing user stories, there are a number of variations. What are the three basic building blocks in their most basic formats?

A

Role, feature, and outcome

17
Q

Why is it important to keep your user stories updated?

A

To ensure they’re still accurate

18
Q

Why is it important to convert business requirements into user stories?

A

To shed light on unnoticed needs

19
Q

Why are user stories compatible with the Agile methodology?

A

They break issues down into small chunks

20
Q

What does user story explain?

A

A specific action a certain type of user can take within your app