> For the complete documentation index, see [llms.txt](https://docs.codeyourfuture.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codeyourfuture.io/archive/archived-pages/cyf-products-final-projects/roles/scrum-master.md). # Scrum Master This role is only part of the **Product Teams** responsible for building features that support the day-to-day processes of CYF. The expected **commitment** is 5 hours per week for at least three months. This is so you and Code Your Future get the most out of the experience. **Who are you?** * Looking to **volunteer** in a Product team * Experience as **Scrum Master** of at least one year in the role) or someone with experience in the tech world who wants to **transition into this role** * Efficient communication skills and great problem-solving to ensure delivery is done effectively #### **Your responsibilities:** * [ ] Work closely with the Product Owner to maintain the team's backlog according to the priority * [ ] Ensure the team understands the project’s goal and user story requirements. * [ ] Raise if the development team requires further clarification on scope and user stories. * [ ] Coaching the development team in self-organisation * [ ] Plan and communicate releases that should happen at least once every two weeks. * [ ] Checking in with the progress of the team at least once every two days, if possible, daily * [ ] Helping to remove obstacles to the team’s progress * [ ] Organising and facilitating Agile processes and Scrum events as needed * [ ] Sprint Planning (acceptance of stories, estimation, sprint goal, communication) * [ ] Daily Scrum (i.e. Slack update) * [ ] Backlog Refinement (support the Product Owner and represent them, if possible) * [ ] Sprint Demo (organise and support team to be ready) * [ ] Sprint Retrospective (run sessions every two weeks, ensure actions are reviewed and assigned to team members) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.codeyourfuture.io/archive/archived-pages/cyf-products-final-projects/roles/scrum-master.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.