Coffee Facilitator Checklist

This page shows checklist for facilitator to run main events of Coffee team.

Rotating lists for person in charge: Irene - Jackie – Kate - Keenan – Vinnie

A. Sprint Planning

Before
  • Create milestone (Format: W No. (dd/mm-dd/mm) on GitLab
  • Prepare Live note on Google Docs
  • Select a main person to take note
  • Post the following information to team channel:
    • Meet link
    • Live note link
    • Names of note taker
  • Remind ever task owner to update their issues on Gitlab with all the status and labels.
  • Join the meeting link with Magestore Meet account to admit other participants.
During
  • Record the meeting
  • Ask team about Sprint goal and activities
  • Ask the team to select which items from a prioritized list of ready product backlog items they forecast they will be able to complete during the sprint.
  • Discuss with the team in more detail how the team will deliver the selected product backlog items
    • Select assignee and supporter
    • Define value and priority
    • Set estimated time or deadline
    • Select meeting date-time if it's a meeting
    • Add milestone for these tasks

  • Review total estimated time (132.5h/team or 3w 1d 4h 30m on GitLab; 24.5h/member or 3d 30m)
  • Ask members to add more tasks if there's time
  • Take photo
  • Create or update calendar events for team meetings
B. Sprint Review
Before
  • Remind all members to update issue tasks
  • Select a main person to take note and a main person as time keeper
  • Check GitLab identify which items should be demotrated and the order of demostration
  • Create live note
  • Post the following information to team channel:
    • Meet link
    • Live note link
    • Names of timekeeper and note taker
  • Join the meeting link with Magestore Meet account to admit other participants.
During
  • Record meeting
  • Review Team OKR & Marketing Metric Review
  • The Development Team demonstrates the work that it has delivered to reach the sprint goal.
  • Ask the Development Team to discuss what what bugs/website issues they ran into, and how those bugs were solved
  • Ask the entire group to collaborate on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning
  • Remind team of who's in charge of next week's presentation and training.
After
  • Close the milestone at the end of Friday
C. Sprint retro
Before
During
  • Allow all members to create cards for Glad / Sad / Mad / Start doing columns
  • Let members explain their cards and group
  • Ask everyone to vote maximum 3 items they want to discuss and solve
  • Discuss solutions for selected items and owner for these solutions
  • Check out
After
  • Create issues for selected items on GitLab