ScrumMaster Cheat Sheet, Summaries of Project Management

This cheat sheet provides a quick list of the actions a ScrumMaster performs. ... Update and review the current Burndown chart for the current Sprint, ...

Typology: Summaries

2021/2022

Uploaded on 09/07/2022

nabeel_kk
nabeel_kk 🇸🇦

4.6

(65)

1.3K documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
4100 E. Third Ave, Suite 205
Foster City, CA 94404
650-931-1650
1
ScrumMaster Cheat Sheet
This cheat sheet provides a quick list of the actions a ScrumMaster performs.
1 Every Day
Do these things every day.
1.1 Start of Day
1. Update and review the current Burndown chart for the current Sprint, for each Team of interest.
a. If a Team is running behind schedule, investigate, and try to help bring it back on track.
Make sure that tasks that been have completed have a Completed status, so they
contribute to the progress.
2. Review the Sprint Backlog items and their associated tasks.
a. Check to see if any tasks have missing information.
Missing Estimates for Backlog items
Missing Detail Estimates for tasks
Missing To-Do values for tasks
Missing Owners for tasks that are In Progress or Complete
b. Look for inconsistencies.
Backlog Items with status values that can be selected in the tracking tool, but
which we have decided not to use.
Tasks marked as Complete, which have non-zero To-Do values
Tasks with zero To-Do values, which are not marked as Complete
Backlog Items marked as Complete, which have any tasks not marked as
Complete
Backlog Items that have been finished (all of their tasks have been marked as
Complete), and should be marked as Complete, but are not
c. Follow up with appropriate Team members, to ensure they supply missing information,
and correct inconsistencies
1.2 Throughout the Day
1. Assist Team members to resolve issues, as needed.
a. Protect Team members from interference
b. Teach them to solve problems first, and come to you when they can’t solve them
2. Facilitate the Daily Scrum meeting.
a. Show the Burndown chart
b. Listen to answers to the standard three questions
c. Ensure follow-up actions and participants are defined
d. Provide any additional information the Team should know
3. Review new User Stories, Technical Stories, and Defects added to the Product Backlog, for clarity
and completeness
a. Make sure new Product Backlog items are assigned to the right Teams
pf3

Partial preview of the text

Download ScrumMaster Cheat Sheet and more Summaries Project Management in PDF only on Docsity!

Foster City, CA 94404 650-931-

ScrumMaster Cheat Sheet

This cheat sheet provides a quick list of the actions a ScrumMaster performs.

1 Every Day

Do these things every day.

1.1 Start of Day

  1. Update and review the current Burndown chart for the current Sprint, for each Team of interest. a. If a Team is running behind schedule, investigate, and try to help bring it back on track. Make sure that tasks that been have completed have a Completed status, so they contribute to the progress.
  2. Review the Sprint Backlog items and their associated tasks. a. Check to see if any tasks have missing information.  Missing Estimates for Backlog items  Missing Detail Estimates for tasks  Missing To-Do values for tasks  Missing Owners for tasks that are In Progress or Complete b. Look for inconsistencies.  Backlog Items with status values that can be selected in the tracking tool, but which we have decided not to use.  Tasks marked as Complete, which have non-zero To-Do values  Tasks with zero To-Do values, which are not marked as Complete  Backlog Items marked as Complete, which have any tasks not marked as Complete  Backlog Items that have been finished (all of their tasks have been marked as Complete), and should be marked as Complete, but are not c. Follow up with appropriate Team members, to ensure they supply missing information, and correct inconsistencies

1.2 Throughout the Day

  1. Assist Team members to resolve issues, as needed. a. Protect Team members from interference b. Teach them to solve problems first, and come to you when they can’t solve them
  2. Facilitate the Daily Scrum meeting. a. Show the Burndown chart b. Listen to answers to the standard three questions c. Ensure follow-up actions and participants are defined d. Provide any additional information the Team should know
  3. Review new User Stories, Technical Stories, and Defects added to the Product Backlog, for clarity and completeness a. Make sure new Product Backlog items are assigned to the right Teams

Foster City, CA 94404 650-931-

1.3 End of Day

  1. Same as Start of Day: Review status, look for missing or inconsistent information, and follow up with Team members to resolve.

2 Just before the Sprint Planning Meeting

Prepare for the Sprint Planning meeting. Do this at the scheduled time before the Sprint Planning Meeting.

  1. Read through the Product Backlog Items the Product Owner has requested that the Team address in the Sprint Planning meeting. a. Review for clarity and completeness, and assist the Product Owner with any necessary revisions.
  2. Define Sprint parameters a. Estimate the Team’s capacity for work in the Sprint (velocity)
  3. Add Sprint-related information to any tool that requires it

3 In the Sprint Planning Meeting

Facilitate the meeting.

  1. Go through the top Product Backlog items, ranked by the Product Owner, and read each one to the Team.
  2. Facilitate the Planning-Poker estimation process.
  3. Enter the estimate for this item into the tool used to record this information.
  4. Move the item into the Sprint Backlog.
  5. Repeat, and stop when the Sprint is full.

4 In the Sprint Review Meeting

The ScrumMaster has little to do, except for the important part of making sure that the meeting happens. The Team members are responsible for demonstrating the completed Sprint Backlog Items to the Product Owner, and for deciding who will do the various parts of the demonstration.

5 In the Retrospective Meeting

The ScrumMaster facilitates this meeting, which is attended by the Product Owner and all Team members.

  1. The ScrumMaster reviews with the Team the status of work items they selected in the previous Retrospective meeting.
  2. The ScrumMaster facilitates information collection, recording what the Team members, Product Owner, and ScrumMaster have to say about a. What went well, that we should do again b. What didn’t go well c. Specific suggestions for improvement