Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Programming > Agile Software Development: Prioritization > Flashcards

Agile Software Development: Prioritization Flashcards

1
Q

Prioritization

A

Working on the things that provide value to the customer first.

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

Lack of priority

A

Too much Scope
Poor quality
unsatisfied customers
unsuccessful product

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

Two major perspectives to begin prioritizing

A
  1. Business Value

2. Technical Complexity

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

Determining Business value

A
  1. What is most important for our customer?
  2. Are we building what will make our customer successful?
  3. Are we building something that our customer will benefit from?
  4. Are we delivering Value?
  5. What is not ciritical for success?
  6. What is the customer asking for that they don’t actually need?
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

User stories at the top of the team’s to-do list are high-priority and should have what type of details?

A

Well-defined details so that the team can work on them

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

Product Backlog

A

List of all the remaining work for a product

Planning tool for the team developing the product

Contains, user stores, features, and epics for a product

Centralized and prioritized “To DO list” for the product

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

Who owns the product backlog?

A

Product Owner

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

Criteria for a Good Product backlog

A

Good Product Backlog: DEEP

The key aspects of a good product backlog are being Detailed Appropriately, Estimated, Emergent, and Prioritized.

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

Which user stories are prioritized in the product backlog?

A

Highest value and highest Risk

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

User stories at the top of the product backlog

A

1 Higher priority user stories

  1. Well defined user stories
  2. Higher risk user stories
  3. REady to be implemented
  4. INVEST criteria applied to stories
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

User stories at the bottom of the product backlog

A
  1. Lower priority
  2. Lower risk user stories
  3. User stories that are not well defined
  4. Invest Criteria not fully applied
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Progressive Elaboration

A

A techique for prioritizaing the product backlog

Combine the backlog and any new user stories. Then prioritize user stories to the top of the backlog the items of high priority, well defined, and finer granularity. While the low priority, not well defined, and courses granularity user stories will be at the bottom of the backlog.

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

When are user stories split?

A

Too complex or too big
Dependencies are present
Not able to estimate
INVEST criteria is not met

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

Sprint Backlog

A

Teams backlog of committed work for a sprint

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

Creating the Sprint Backlog

A
  1. PO prioritize the product backlog
  2. The team commits to as much work as they can deliver.
  3. The team pulls the work
  4. The team only focuses on what is in the sprint backlog
  5. The PO prioritizes the work for the next sprint in the product backlog, while team members are working on the sprint backlog items
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Who is responsible for the sprint backlog?

A

The team

17
Q

MoSCoW

A

Backlog prioritization technique

Must have - critical
Should have - important
Could have - nice to have
Won’t have - never

Use Swim lanes or a Matrix

18
Q

Basic Prioritization

A

Prioritize user stories based on value alone

User Stories are assigned Priority levels such as P1, P2, P3

High priority user stories are assigned P1 and are implemented first

P2 user stories are implemented next and P3 stores are last

19
Q

Dot Voting

A

User stores or features are posted on a board

Dots represent “votes” and are given to each person

Each person receives the same number of dots

The number of dots that are given should be less than the number of user stories being voted on

Each person places their dots on the features or user stories

User stories are prioritized according to the number of dots

20
Q

Play Money

A

Prioritization Technique

Each customer gets play money that equals the product budget

Each person distributes or spends their money on the features for the product

Features are prioritized according to the amount of the budget they recieve

Programming (80 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions