20 Questions Team: Difference between revisions
From Wayne's Dusty Box of Words
(Created page with "# How large is your product backlog? # What is the typical age of a user story in the product backlog? # What is your average lead time from an idea being added to the product...") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
=20 Questions a New Scrum Master should ask a Team to Get up to Speed= | |||
# How large is your product backlog? | # How large is your product backlog? | ||
# What is the typical age of a user story in the product backlog? | # What is the typical age of a user story in the product backlog? | ||
# What is your average lead time from an idea being added to the product backlog to its delivery? | # What is your average lead time from an idea being added to the product backlog to its delivery? | ||
# Does your product backlog contain user stories none of the current team members | # Does your product backlog contain user stories none of the current team members are familiar with? | ||
# How often are you grooming the product backlog? | # How often are you grooming the product backlog? | ||
# On how many user stories are you working in parallel during backlog grooming? | # On how many user stories are you working in parallel during backlog grooming? | ||
| Line 16: | Line 17: | ||
# What is a typical distribution of story sizes in your sprint backlogs? | # What is a typical distribution of story sizes in your sprint backlogs? | ||
# Are you reestimating user stories at the end of a sprint? If so, under which circumstances are you doing so? | # Are you reestimating user stories at the end of a sprint? If so, under which circumstances are you doing so? | ||
# What was your velocity | # What was your velocity for the last three sprints? | ||
# How many user stories are typically not finished within a sprint and for what reasons? | # How many user stories are typically not finished within a sprint and for what reasons? | ||
# Are you changing user stories once they | # Are you changing user stories once they have become an item of a sprint backlog? And if so, under what circumstances? | ||
Latest revision as of 06:21, 8 October 2020
20 Questions a New Scrum Master should ask a Team to Get up to Speed
- How large is your product backlog?
- What is the typical age of a user story in the product backlog?
- What is your average lead time from an idea being added to the product backlog to its delivery?
- Does your product backlog contain user stories none of the current team members are familiar with?
- How often are you grooming the product backlog?
- On how many user stories are you working in parallel during backlog grooming?
- How long does the grooming of a typical user story take?
- How are you creating user stories? (Is it a joint team effort with the PO or is the product owner writing the user stories and the team estimates them?)
- Where are you discussing user stories? Only during grooming sessions or also on Slack or via comments on tickets, for example?
- Do you apply a "definition of ready" standard to your user stories?
- If so, of what criteria is your "definition of ready" composed of?
- Who is writing acceptance criteria and in what format?
- How are you estimating the likely effort of a user story?
- Are you estimating in man-hours or story points?
- How are you practicing the estimation process, if the team shares different opinions?
- What is a typical distribution of story sizes in your sprint backlogs?
- Are you reestimating user stories at the end of a sprint? If so, under which circumstances are you doing so?
- What was your velocity for the last three sprints?
- How many user stories are typically not finished within a sprint and for what reasons?
- Are you changing user stories once they have become an item of a sprint backlog? And if so, under what circumstances?
