Doc team members rotate scrum master duties monthly. See table below.

Responsibilities

Scrum masters should join the "scrum-masters" Google group, and ask the outgoing scrum master to make sure you are on the Scrum of Scrums wiki template.

Daily

• Forward learner support messages received at docs@edx.org to info@edx.org. We get many fewer of these, now that the email address no longer appears in the Learner's Guide. Instead, learners use the feedback form. You may use the following boilerplate:
  Hi <name>,
  

  Thanks for contacting us! I'm forwarding your message to the student support team, who will be happy to help you.

  All the best,
  <name>

• Review documentation feedback spreadsheet and create DOC tickets as necessary.

• Triage incoming JIRA doc tickets; follow up if urgent, otherwise leave for grooming.
• Handle incoming requests (and delegate as necessary) from the following and other channels.
  
  • E-mail
  • HipChat
  • edX Code
  • Slack: Open edX, Documentation, General, Theming, Product
  • User feedback

Weekly

• Check open PRs for any that are stale.
• Check Google Analytics. (We don't actually have anything to check in Google Analytics yet.)
• Monday: Create new "Documentation Projects Week of <date>" page on Documentation Weekly Statuses page. For steps on how to create this page, see Update weekly summary reports.
• Monday, Wednesday, Friday: Run standup. Update stories as needed; facilitate clearing any blockers.
• Tuesday: Meet with George Song (Deactivated) to review OSPRs that need documentation. Often, George handles this by email.  
• Tuesday: Run /wiki/spaces/DOC/pages/98369937 meeting. Review JIRA discovery board for new stories, ensure team has groomed and ready for work stories, ensure team is clearing backlog.
• Wednesday: On Scrum of Scrums Notes pages, add latest "Documentation Projects Week of <date>" and any additional team updates.
• Thursday: Make sure the Scrum of Scrums Notes page has been updated.

Bi-Weekly

• Review edx-code and create doc tickets as necessary.

• Review openedx-analytics and create doc tickets as necessary.

• Coordinate signups for doc demos at engineering demos. You can see the list of PRs merged since the last demo session by filtering the PR page for the edx-documentation repository. The syntax for that filter is is:pr merged:>=2016-03-25. (This happens very rarely.)

Monthly

• Outgoing scrum masters should update the Engineering Teams page and Scrum of Scrums Notes pages (when they become available) to list the new scrum master.

As Necessary

• Schedule meetings for followups or other.
• Act as liaison between doc team and other teams.

Rotation