Estimating an Agile project Flashcards

1
Q

What do we need to take into account when developing user roles

A

C.C.C

Context, character, Criteria

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

What is context?

A

BE

The context is the bundled experiences the person will have based on where they are in your product

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

What is character ?

A

RSM &N

Role specific motivations and needs of the user

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

What is criteria?

A

U.E.O.P

A users expected outcome(s) from using the product

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

What is a user story?

A

B.S.F.P.P.U

Brief statement of functional product need from the perspective of a specific type of user.

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

Provide a user story format

A

AS A [U] I [W.N.C] SO THAT [R]
As a {user role], I {want /need/can}{goal} so that [reason}.
Example: As a {standard customer}, I{ want}to {see a list of benefits} of upgrading so that {I can see if it’s worth the cost}
In the story there is not the how but the why and what

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

What are the 3 C’s ?

A

C.C.C
card, conversation, and confirmation
Card -User stories are best recorded on a three by five index card. Many product owners are tempted to create a user story spreadsheet. If you try to do this what you’ll find is that it’s more difficult to communicate about individual stories

Conversation- you don’t want to overwhelm the group with a list of information. Instead you want to have a group conversation. Many times when an Agile team is starting out, they’re very focused on the format of a user story. What they forget is that a user story is a means to an end. It’s not about the format, it’s about having a group conversation.

Confirmation- t’s very important that the acceptance criteria closely match the user story on the front of the card. It should be the result of the conversation with the development team.

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

What is the best way to create a story?

A

3x5 I - SP
User stories are best recorded on a three by five index card. Many product owners are tempted to create a user story spreadsheet. If you try to do this what you’ll find is that it’s more difficult to communicate about individual stories.

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

What is acceptance Criteria?

A

C.K.B D.D.M
This is the confirmation that everybody knows how to deliver the story. This is typically written on the back of the card.
this will be the definition of done. It’s very important that the acceptance criteria closely match the user story on the front of the card. It should be the result of the conversation with the development team.

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

Written effective user stories:

What does I.N.V.E.S.T mean?

A

I- Independent- The story must be independent of another story.
N- negotiable-The product owner shouldn’t create user stories that focus too much on how to deliver the request.
V- valuable- The customer value is the most important part of the user story. Without it the product owner can’t prioritize the backlog
E- estimable- If can not estimate the length of time it is likely too big
S- small- the user story should be delivered in small 2 week sprints.
T- testable- your story can not be subjective- I want to find birds quickly on my app.

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

What is an epic?

A

G.S.C.O

Large Grouping of work(stories) with common objectives

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

What does the acronym F.E.E.D.B.A.C.K mean?

A
F- flow 
E- Effort 
E- Entry
D- data
B- Business rules 
A- Alternatives(
C- Complexity 
K- knowledge
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Describe F- in feedback with an example?

A

S for T
This is how the story might step through the application’s workflow.
As a bird finder, I want to see a list “of matching birds on my smartphone, “so I can learn more about birds “when I’m away from my house.” And you could substitute smartphone for a tablet for even more stories.

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

Describe first E- in feedback with an example?

A

BLM
Here you might break down the epic based on the developer’s level of effort. A new story might be, “I want to see a list of matching birds “sorted by likely matches, “so that I can learn more about bird watching.” Here you split the story based on the effort.

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

Describe the 2nd E - in feedback with an example?

A

L of B GPS
Sometimes the team might want to break down the epic by how the customer enters the data. A new story might be, “As a bird finder, I want to see a list of matching birds “based on my uploaded GPS coordinates, “so that I can learn more about bird watching.”

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

Describe D- in feedback with an example?

A

R.U.D
You may want to break up your epic based on common data operations, like read, update and delete. A new story might be, “As a bird finder, I want to see “an editable list of matching birds “so I can learn more about bird watching.

17
Q

Describe B- in feedback with an example?

A

GPS
These are the rules that help you expand on the goals of the initial epic. “As a bird finder, I want to see a list of matching birds “based on the likelihood of a match “on GPS coordinates and the image, “so I can learn more about bird watching.

18
Q

Describe A- in feedback with an example?

A

ZIP CODE
some epics can easily be broken into stories with alternative criteria. You could create another story based on alternatives. “As a bird finder, I want to see a list “of matching birds located in my zip code, “so that I can learn more about bird watching.”

19
Q

Describe C- in feedback with an example?

A

C.M GPS RA
You can break it down into stories with increasing complexity. A new story might be, “As a bird finder, I want to see a list of matching birds “based on color, GPS coordinates and recorded audio, “so I can learn more about bird watching.”

20
Q

Describe K- in feedback with an example?

A

E.K.S.S.O
sometimes the product owner will present the epic and the team will need more knowledge. They have to research the epic and break it down into stories. When this happens, the developers will create spikes. Story spikes aren’t stories but they lead to stories. They’re open questions that the team needs to answer to deliver the story.