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 "Doc Status YYYY/MM/DD page on Documentation Weekly Statuses page. For steps on how to create this page, see Update weekly summary reports.
• Monday and 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. Remind the team to update the summary table in the weekly status page, as this is included via an Excerpt Include macro in the SOS weekly status page, and is used by the CTO/Eng Leads to better understand what Engineering is working on. 
• Wednesday: On Scrum of Scrums Notes pages, under Doc, include the Excerpt Macro:
  1. On the appropriate week's Scrum of Scrums page, select Edit at the top of the page.
  2. Under Docs, remove the placeholder text. 
  3. In the toolbar at the top of the page, click + (Insert More Content) dropdown, and select Other Macros. The Select Macro dialog box appears.
  4. In Search, type Excerpt Include. Select the macro.
  5. Under Page Containing the Excerpt *, start typing the name of the latest doc status page (for example, Doc Status 2017/11/6). Select the appropriate week's status page. 
  6. Check the Remove Surrounding Panel checkbox. This removes the doc status page's wrapper.
  7. Click Insert.
  8. Click Publish.
• Thursday: Make sure the Scrum of Scrums Notes page has been updated. Provide a friendly reminder to doc team members who have not filled out the summary table for the week.

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 follow-ups or other.
• Act as liaison between doc team and other teams.

Rotation