As the Fedora development employs the common Agile approach of sprints (two-week long sprints in our case) which are facilitated by a Scrum Master, this document is intended to provide some detail to the role and responsibilities of the scrum master.
Meetings
The scrum master should facilitate the following meetings
- Sprint Planning (example)
- Sprint Stand-ups (example)
- Thursday Fedora Committers (example)
- Sprint Wrap-up (example)
Wiki Pages
- 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)
- Encourage developers to contribute wiki pages on software design.
- Ask developers to provide at least a minimal how-to page for acceptance testing a new feature. (Create a template page if necessary.)
- Make sure new sprint wiki pages are situated properly within the project wiki.
