# Scrum Team Functions

## Video Version&#x20;

{% embed url="<https://youtu.be/xAXU4lAd0L8>" %}
Credit: Tech Fleet <https://youtu.be/xAXU4lAd0L8>
{% endembed %}

## Scrum Functions

Scrum has 3 different roles that make up a Scrum team: the Product Owner, the Scrum Master role, and the "Doer" role. These 3 roles may be operated by one single person, or 3 separate people.&#x20;

In Tech Fleet, the Product Strategy team typically owns the responsibilities for Scrum  teams. This could change based on RACI chart decisions ([learn more here!](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts)).

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FlbdvjjfhZniKJS4XMwas%2FTech%20Fleet%20Project%20Structure.png?alt=media&#x26;token=5363a120-72d5-4ab7-8627-f54b093661b7" alt=""><figcaption><p>This shows the typical project structure for Tech Fleet project training. Learn more on this page: <a href="https://guide.techfleet.org/project-portal/learn-about-project-training/commitment-vs.-job-function-vs.-people-on-teams">https://guide.techfleet.org/project-portal/learn-about-project-training/commitment-vs.-job-function-vs.-people-on-teams</a> Credit: Tech Fleet.</p></figcaption></figure>

{% hint style="info" %}
Remember: Roles are not job titles! They are simply commitments of responsibilities on teams that team members assign themselves each sprint. One person can own many roles. Learn more in this section of the guide: <https://guide.techfleet.org/project-portal/learn-about-project-training/commitment-vs.-job-function-vs.-people-on-teams>
{% endhint %}

### Product Owner Function

#### Who owns it?

This function is fulfilled by the [The Product Strategy Team](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/product-strategy-function) in Tech Fleet.

#### What is it?

The product owner function is the keeper of the backlog and the orchestrator of product work. They direct the priorities of work based on key needs and roadmap outcomes. They work in tandem with a product manager to set roadmap and vision, and focus on delivering the vision near-term.

* Product Backlog Management: Create, prioritize, and refine the product backlog, ensuring it is aligned with the product vision and strategy. Prioritization: Prioritize features and user stories based on business value, customer needs, and technical feasibility.&#x20;
* Stakeholder Management: Collaborate with stakeholders, including customers, business owners, and team members, to ensure that product decisions align with their needs and expectations.&#x20;
* Communication: Communicate product plans, priorities, and progress to stakeholders, including daily stand-ups, sprint planning, and sprint reviews.&#x20;
* Market and Customer Research: Gather, manage, and prioritize market/customer requirements, acting as a customer advocate to articulate user needs.&#x20;
* Decision Making: Make decisions on product features, priorities, and trade-offs, balancing business, customer, and technical requirements.&#x20;
* Team Alignment: Ensure the development team understands the product vision, priorities, and goals, and aligns their work accordingly.&#x20;
* Backlog Refinement: Refine the product backlog regularly, ensuring it remains relevant, up-to-date, and aligned with the product vision and strategy.&#x20;
* Sprint Planning: Participate in sprint planning, ensuring the team has a clear understanding of the product backlog and priorities.&#x20;
* Sprint Review: Participate in sprint reviews, ensuring the team demonstrates working software and receives feedback from stakeholders.

### Scrum Master Function

#### Who owns it?

This function is fulfilled by the [The Product Strategy Team](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/product-strategy-function) in Tech Fleet.

#### What is it?

The Scrum Master function is a facilitator and coaching function that ensures the Scrum framework is followed and the team is empowered to achieve its goals. Here are the key responsibilities:

* Facilitating Scrum Ceremonies Lead daily stand-ups (or daily scrums) to ensure team members are aligned and aware of their tasks and progress Facilitate sprint planning meetings to ensure the team understands the sprint goals and objectives Lead sprint review meetings to demonstrate the team’s work and gather feedback Facilitate sprint retrospective meetings to identify areas for improvement and implement changes
* Removing Impediments Identify and remove obstacles (impediments) that hinder the team’s progress Collaborate with team members and stakeholders to resolve issues and find solutions Ensure the team has the necessary resources and support to complete their work
* Coaching and Mentoring Coach team members in Scrum principles and practices Mentor team members to improve their skills and knowledge Encourage self-organization and empowerment within the team
* Team Support Provide guidance and support to team members as needed Help team members understand their roles and responsibilities Foster a positive and collaborative team culture
* Reporting and Analysis Analyze burndown charts and other metrics to identify trends and areas for improvement Report on team progress and performance to stakeholders Provide insights and recommendations for process improvements

### "Sprint Do'er" Function

#### Who owns it?

The people performing sprint work are Sprint Do'ers. &#x20;

#### What is it?

Anyone who takes ownership of a ticket in a sprint is a Do'er.&#x20;

In the industry, Scrum teams may call this the "development team", although they are not always developers! This is confusing to people who are not doing development in Scrum teams. This is why we call them "Do'ers". People doing the sprint work.

This function is fulfilled by the [UX research team](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/user-experience-functions/ux-research-function), the [UX design team](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/user-experience-functions/ux-design-function), the [UX writing team](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/user-experience-functions/ux-writing-function), the [project management team](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/project-management-function), and the [development team](https://guide.techfleet.org/team-portal/new-teammate-handbook/project-training-teams/supported-team-functions-in-project-training/development-function) in Tech Fleet.&#x20;

## Scrum Team Activities and Responsibilities

Here is a picture showing a [RACI chart](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts) of which roles on Agile teams are set to work on Agile deliverables. [Learn more about how to make your own RACI charts here](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts).

1. **Responsible** = the person who performs the work.
2. **Accountable** = the person who oversees and ensures that the work progresses.
3. **Consulted** = the person who provides considerations and is asked advice.
4. **Informed** = the person who is told what happens after it happens.

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FrtpXaJJVXvz2d01DOWWd%2FRACI%20for%20agile.png?alt=media&#x26;token=31357341-3b14-46bb-bd25-a724808edb4f" alt=""><figcaption><p>A RACI chart depicting the typical responsibilities based on team function for Sprint work. Credit: Tech Fleet.</p></figcaption></figure>

## Head to the Next Lesson


---

# Agent Instructions: 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:

```
GET https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-methods/scrum-method/scrum-team-functions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
