...

1. The scrum master should ensure the agendas are created for the following meetings (in conjunction with the Technical Lead), as well as ensure meeting minutes are captured
   • Sprint Planning (example)
   • Sprint Stand-ups (example)
   • Thursday Fedora Committers (example)
   • Sprint Wrap-up (example)
2. Encourage developers to contribute wiki pages on software design.
3. Ask developers to provide at least a minimal how-to page for acceptance testing a new feature. (Create a template page if necessary.)
4. Make sure new sprint wiki pages are situated properly within the project wiki.

...

JIRA

The scrum master should be in touch with the theme of the sprint and the progress of the relevant tickets. In regards to Pivotal Tracker JIRA, the scrum master has the following responsibilities:

• Facilitate the creation of tickets
• Help prioritize tickets by arranging them in priority order within PivotalJIRA
• Review/Build/Test tickets when they have been put into "FinishIn Review" ed (in coordination with the Tech Lead)
• "DeliverClose" or "RejectReopen" tickets based on review (in coordination with the Tech Lead)
• Squash/Merge/Push commits if they have been "Deliver"ed"Accept" tickets that have built successfully after commit in Travis-CIClosed"