EVENTS PARTICIPANTS GOALS ANSWER KEY

Release Planning
Product Owner Product Owner confirms priority of the Product Backlog
Points:
800 = (400 + 400) Scrum Master Scrum Team breaks Users Stories into tasks, creating the Sprint Backlog

Scrum Team Scrum Team relatively estimates the User Stories

Customers Product Owner publishes the Release schedule

Management Product Owner gains clarity needed to create/update roadmap

Other Stakeholders, as needed Scrum Team commits to the scope at a high level

Backlog Refinement
Product Owner Product Owner confirms priority of the Product Backlog
Points:
600 = (300 + 300) Scrum Master Product Owner confirms all User Stories meet Definition of Ready (DoR)

Scrum Team Product Owner and Scrum Team refine ~2 Sprints-worth of backlog to be “Sprint Ready”

Customers Scrum Team breaks User Stories into tasks, creating the Sprint Backlog

Management Scrum Team relatively estimates the User Stories

Other Stakeholders, as needed Scrum Team commits to User Stories and PBIs they can complete in the Sprint

Sprint Planning
Product Owner Product Owner prioritizes the Product Backlog
Points:
600 = (300 + 300) Scrum Master Product Owner confirms all User Stories meet Definition of Ready (DoR)

Scrum Team Product Owner and Scrum Team refine ~2 Sprints-worth of backlog to be “Sprint Ready”

Customers Scrum Team breaks User Stories into tasks, creating the Sprint Backlog

Management Scrum Team relatively estimates the User Stories

Other Stakeholders, as needed Scrum Team commits to User Stories and PBIs they can complete in the Sprint

Daily Standup
Product Owner What did I do yesterday that helped the team meet the Sprint Goal?
Points:
600 = (300 + 300) Scrum Master Can I describe a technical issue in detail for help on it from the team?

Scrum Team What will I do today to help the team meet the Sprint Goal?

Customers Can I share an idea on something new I think we should add to our Sprint?

Management Ask the Product Owner to have a detailed discussion on the expectations of a User Story

Other Stakeholders, as needed Are there any impediments to the team in meeting the Sprint Goal?

Mid-Sprint Review
Product Owner Scrum Team determines what went well in their Sprint
Points:
500 = (200 + 300) Scrum Master Scrum Team demonstrates working product features

Scrum Team Team identifies what could have gone better in their Sprint

Customers Product Owner provides feedback on a User Story’s completeness, if revisions needed

Management Team identifies actions to improve, vote on what to take into the next Sprint (Kaizens)

Other Stakeholders, as needed Scrum Team identifies any additional actions needed to prep for End of Sprint Review

End of Sprint Review

Product Owner Scrum Team determines what went well in their Sprint
Points:
900 = (600 + 300) Scrum Master Scrum Team demonstrates working product features

Scrum Team Scrum Team identifies what could have gone better in their Sprint

Customers Product Owner formally rejects or accepts each User Story based on DoD criteria

Management Team identifies actions to improve, votes on what to take into the next Sprint (Kaizens)

Other Stakeholders, as needed Sprint is formally closed in Jira and Team/Stakeholders celebrate accomplishments

Sprint Retrospective
Product Owner Scrum Team determines what went well in their Sprint
Points:
600 = (300 + 300) Scrum Master Scrum Team demonstrates working product that was accomplished in the Sprint

Scrum Team Scrum Team identifies what could have gone better in their Sprint

Customers Product Owner formally rejects or accepts each User Story based on DoD criteria

Management Team identifies actions to improve, votes on what to take into the next Sprint (Kaizens)

Other Stakeholders, as needed Sprint is formally closed in Jira and Team/Stakeholders celebrate accomplishments

Your points Your points

2400 Available points 2200 Available points

Scoring: 100 points for each correct check mark

100 points lost for each incorrect check mark

0 points for missed answers