Backlogs and Planning

Question 1

What is the product backlog?

Answer 1

List of features that the project is expected to deliver.

Question 2

Who develops the product backlog?

Answer 2

Product owner in collaboration with the scrum master and development team.

Question 3

What is the single source for maintaining what needs to be done in the project?

Answer 3

product backlog

Question 4

What is the product backlog made up of?

Answer 4

User stories

Question 5

What is an acronym that helps us identify that we have a good product backlog?

Answer 5

I - Independent, PBI is self-contained and not dependent on other PBIs
N - Negotiable, should leave room to discuss and possibly modify the feature
V - Valuable, PBI must deliver value to users and customers
E - Estimable, PBI must be estimated in terms of effort and priority
S - Small , PBI should be small enough for sprint planning with reasonable accuracy
T - Testable, outcome can be tested by end users and customers

Question 6

What is a PBI?

Answer 6

Product Backlog Item

Question 7

What is it important to establish priorities?

Answer 7

Express importance, significance and urgency associated with the features.

Question 8

What benefits does it offer to complete high priority items first?

Answer 8

Evaluate value early in the project life cycle.
Customers can determine if results correspond to what they expected.
Establishes control of the project.

Question 9

When should the decomposition process of user stories take place?

Answer 9

Just in time to deliver the stories to the development team for development but not too soon to avoid unnecessary work because something is changing.

Question 10

What are the benefits of a visible product backlog?

Answer 10

The team needs to see the overall plan.
Able to identify where the team is in relation to the plan
Anticipate what comes next

Question 11

What affect does grooming have on the product backlog?

Answer 11

Changes:

1. Features (Add or remove)
2. Priorities
3. Effort

Question 12

Who is responsible for backlog grooming?

Answer 12

Product owner in collaboration with the ENTIRE team

Question 13

For large projects that have multiple teams, what happens to the backlogs for the project and each team?

Answer 13

Each team will be managing their own backlog. There will be a master backlog.

Question 14

Who participates in the release planning session?

Answer 14

The whole team.

Question 15

What is the result of a release planning session?

Answer 15

Release Plan

Question 16

What is involved in release planning?

Answer 16

Assigning features to the release plan from the product backlog. Then features are assigned to sprints in a manner that creates a product or incremental release.

Question 17

How often should releases take place?

Answer 17

Depends upon the product, customers and end-users. Rule of thumb is deliver when the last sprint can be testable and creates value.

Question 18

How many releases are typically scheduled at a time?

Answer 18

1

Question 19

Although all members of the team participate in the Release Planning Session, who is ultimately reponsible?

Answer 19

Product Owner

Question 20

What three issues should the product release plan consider?

Answer 20

1. Prioritization
2. Value
3. Risk

Question 21

When considering the items that should be worked on first, what should be the focus?

Answer 21

The items that present the greatest risk of failure to the project and highest priority. Solving items with the greatest risk and priority can prevent major issues downstream.

Question 22

What is minimum viable product?

Answer 22

Enough features to evaluate and determine whether a product meets its objectives.

Question 23

What is minimum releasable features?

Answer 23

This is the same as minimum viable product.

Question 24

What is Rapid Prototype Development similar to?

Answer 24

Minimum Viable Product

Question 25

How do constraints affect Release Planning?

Answer 25

It helps to identify the capacity of the team and what can occur in the given release.

Question 26

Does release planning focus on the details or high level features?

Answer 26

High level

Question 27

When does sprint planning take place?

Answer 27

At the beginning of a sprint.

Question 28

Who takes an authoritarian role in the sprint planning meeting?

Answer 28

No one. The product owner and scrum master are facilitators.

Question 29

During sprint planning, who makes decisions about what can and cannot be delivered?

Answer 29

Development Team but the product owner leads the discussion

Question 30

What is the focus of the sprint planning?

Answer 30

1. What will be done?

2. How will it be done?

Question 31

What is acceptance criteria?

Answer 31

Mutually agreed upon criteria that setup a clearly identified state to complete a sprint.

Question 32

What inputs are needed for a good sprint plan?

Answer 32

1. Well groomed product backlog.
2. Team velocity is known.
3. Business and technology constraints that can affect the velocity of the team
4. Team Capability
5. Sprint goal established by product owner

Question 33

Which are assigned to sprints, tasks or features?

Answer 33

Tasks.

Question 34

How can you balance a sprint to minimize careover?

Answer 34

Look for smaller items that can be used to finish time or move a large item to the next sprint and add several smaller items to the current sprint.

Question 35

What rule is carryover breaking?

Answer 35

We must have a potentially shippable product at the end of each sprint.

Question 36

What is a sprint backlog?

Answer 36

features and tasks identified in the sprint planning sessions and assigned to a sprint.

Question 37

Should you overplan a sprint?

Answer 37

No