Product Owner

Question 1

A legacy list of requirements is…

Answer 1

a liability, not an asset

Question 2

Strategies to prioritize the backlog

Answer 2

business value - how much money we’ll make
business risk - what’s the risk and how we can mitigate
technical necessity - what do we need to do first technically to move ahead?

Question 3

the 20/30/50 rule

Answer 3

20% of the backlog should be well refined able to be picked up and worked on
30% suitable for a productive discussion with others
50% summary and possibly a description

Question 4

last responsible moment

Answer 4

the act of delaying the decision until the cost of not making one becomes greater than the cost of making it

Question 5

DEEP for product backlogs

Answer 5

Detailed Appropriately
Estimated
Emergent
Prioritized

Question 6

Elements of the Product Backlog Item

Answer 6

concise description of the intent of the item
estimate of the effort required
estimate of the business value the item will yield
order in the product backlog

Question 7

Each item should require 3-5 pieces of ____

Answer 7

acceptance criteria

Question 8

If some items have more than 5 acceptance criteria

Answer 8

break down the item

Question 9

Sprint planning consists of 2 parts:

Answer 9

1. PO introduces sprint objective and the items that will support it - Dev team debates and estimates and selects top items to go to sprint backlog
2. Dev team creates a plan to tackle each item for the sprint

Question 10

Sprint planning is timeboxed to

Answer 10

8 hours for 1 month sprints and proportionately lower for shorter sprints (4 hours for 2 weeks)

Question 11

Estimate in

Answer 11

complexity points, not time

Fibonacci sequence 0 to 21, 1 point = half-day’s effort

Question 12

Planning poker

Answer 12

everyone gets a deck of cards from 1 to 21
each votes for the item
if everyone places the same card, we’ll move on
if not, we discuss and do it again after the discussion
until the majority agrees

Question 13

Estimates should encompass

Answer 13

everything, testing and dev

Question 14

Estimates are a forecast, not a

Answer 14

commitment

Question 15

Daily Scrum key aspects

Answer 15

timeboxed to 15 mins
enables planning at the daily level
keeps everyone aligned and on track

Question 16

Daily Scrum is not a

Answer 16

status update meeting but a planning meeting

Question 17

3 questions to answer at the daily scrum

Answer 17

what did i do yesterday to bring us closer to the spring goal
what will i do today to bring us closer
what is impeding my progress

Question 18

Removing the impediments from the path is the responsibility of

Answer 18

the scrum master, however, the PO can help out

Question 19

Participants of the daily scrum meeting

Answer 19

the dev team, not PO & SM (they can be there but they don’t have to speak)

Question 20

Scrum team should commit ___% of their time to refinement

Answer 20

10%

Question 21

Backlog refinement requires

Answer 21

1 hour of commitment per week
not all members are required to be in it
scrum masters are not required - usually a rep from every function

Question 22

Blocking and Tackling…

Answer 22

the first week of refinement is blocking: build an ordered list of items to be considered for the next sprint
tackling: refine each item so that it can be discussed in the next sprint

Question 23

Goals of Blocking

Answer 23

1. Explain the objective of next sprint
2. Explain how each item selected contributes to that
3. Identify any issues that would block any item from selection for the next sprint
4. Take action items for any issues that are unable to be resolved during the session

Question 24

Goals of Tackling

Answer 24

1. Consider each selected item in more detail
2. Review Acceptance criteria for each item
3. Discuss supporting materials such as wireframes
4. Follow up on outstanding action items

Question 25

Spikes are raised

Answer 25

during Blocking, as a way to investigate certain unknowns before committing to anything

Question 26

Spikes should have …

Answer 26

a clearly defined goal (what should be learned) and in what time

Question 27

schedule spikes

Answer 27

1 sprint ahead

Question 28

POs next steps at refinement

Answer 28

further refine each item selected for the next sprint

answer any outstanding questions

Question 29

Yesterday’s weather

Answer 29

the idea that the team’s velocity is best predicted by their last sprint’s results

Question 30

Elements of a sprint review

Answer 30

validates that the work is on track to meet stakeholder needs
engaging - everyone in attendance is fully interactive
informative and iterative - feedback feeds into the next sprints

Question 31

Prepare for sprint reviews

Answer 31

Make a list of completed items
make an agenda, minimizing switching between people
send the invitations to the most relevant folks

Question 32

timeline for the sprint velocity being stable

Answer 32

4 sprints

Question 33

how to handle feedback during the sprint review

Answer 33

take down in a feedback grid, but don’t commit during review until everything is considered

Question 34

traits for retrospective

Answer 34

timeboxed at 3 hours for 1 month sprint, but proportionately smaller (1.5 for 2 weeks)

Question 35

goals for retro

Answer 35

inspect the sprint for processes
identify things went well/didn’t go well
create a plan for improvement in the next sprint

Question 36

who usually facilitates the retro?

Answer 36

scrum master

Question 37

What’s a release plan

Answer 37

a projection over time for a few next release cycles of what themes, goals and metrics we’re planning on for the future

Question 38

A way to test how good the user stories are

Answer 38

INVEST

independent, does not depend on other user stories
negotiable, can be rewritten and reprioritized
valuable, provides some value to the user, keep technical stories to the minimum
estimatable, the team knows enough to estimate and slow enough
small, not too complex
testable, must be defined to the point that it can be tested