# Common Agile Deliverables

## Video Version

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

## Common Agile Deliverables

Here are some common deliverables when you are operating with Agile methods. Some of these pertain to the Scrum method only, and some of them are also created in other Agile methods.

Each of these deliverables has a guide you can dig into. Learn more about each one in the [Agile Deliverables section of the Agile Handbook](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables).

## Project Roadmaps (AKA "Sprint Plans")

This deliverable is exclusive to Scrum method.

A sprint plan outlines a future plan for sprint work. It determines an estimate for the kinds of work that future sprints will hold based on the best guess of the team.

Here's what it looks like:&#x20;

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FCdmyskxitoPb3Snv0N4z%2Fimage.png?alt=media&#x26;token=098452e9-5286-4271-985c-65ea0db00c0f" alt=""><figcaption><p>A picture of a project phase roadmap. Credit: Tech Fleet.</p></figcaption></figure>

Learn more here:

{% content-ref url="../../agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/project-phase-roadmaps" %}
[project-phase-roadmaps](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/project-phase-roadmaps)
{% endcontent-ref %}

## Sprint Planning Items

This deliverable is exclusive to Scrum method.

Spring Planning Items happen after a [Sprint Planning meeting](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-methods/scrum-method/scrum-meetings) where the team outlines their shared goals for a sprint and assigns committed team members. &#x20;

Here's what it looks like:&#x20;

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FbHUxAbfp2cdy3XKn5J4y%2FSprint%20Goals.png?alt=media&#x26;token=53fdefa4-d82d-4f0c-88e0-e33bdc8d6085" alt=""><figcaption><p>Sprint planning items include background, sprint goals, and sprint responsibilities. Credit: Tech Fleet.</p></figcaption></figure>

Learn more here:

{% content-ref url="../../agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-planning-items" %}
[sprint-planning-items](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-planning-items)
{% endcontent-ref %}

## Sprint Velocity

This deliverable is exclusive to Scrum method.

Spring Velocity is a number that indicates how much work a team is estimated to be able to get done in one sprint.&#x20;

Learn more here:

{% content-ref url="../../agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/agile-team-maturity-measurement" %}
[agile-team-maturity-measurement](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/agile-team-maturity-measurement)
{% endcontent-ref %}

## Kanban Boards

This is not exclusive to Scrum method, it is common with Scrum teams and Kanban teams.

Kanban Boards outline the team's process and allow teams to track the work in different statuses. This helps teams gain visibility into their collective work.

Here's what it looks like:&#x20;

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FTRL27a99cHxv5GlwhqRk%2Fkanban.png?alt=media&#x26;token=339f8e66-7685-420a-8aeb-d8afaf473fac" alt=""><figcaption><p>A picture of a Kanban Board. Credit: Tech Fleet.</p></figcaption></figure>

Learn more here:

{% content-ref url="../../agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/backlogs-and-kanban-boards" %}
[backlogs-and-kanban-boards](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/backlogs-and-kanban-boards)
{% endcontent-ref %}

## Sprint Retro Boards

This deliverable is exclusive to Scrum method.

[Sprint Retrospectives](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-methods/scrum-method/scrum-meetings) are a crucial part of the Agile process and Scrum Method. Sprint Retro Boards are the place where the team reflects in their process from the previous sprint.&#x20;

Here's what it looks like:

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FeMtKuKGH5Gr4WtNDa9Fw%2Fimage.png?alt=media&#x26;token=9a70be2b-dba0-4097-8214-adc7b2c903ec" alt=""><figcaption></figcaption></figure>

Learn more here:

{% content-ref url="../../agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-retro-boards" %}
[sprint-retro-boards](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-during-projects/sprint-retro-boards)
{% endcontent-ref %}

## RACI Charts

This is not exclusive to Scrum method, but common with Scrum teams.&#x20;

A RACI (which stands for Responsible, Accountable, Consulted, Informed) chart outlines daily tasks and breaks down who does them on Agile teams. This deliverable is a key alignment deliverable to come to agreements about how work gets done.&#x20;

Here's what it looks like:&#x20;

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2Fs1YBcl9JC3789B3vd6gq%2FRACI.png?alt=media&#x26;token=557be5ea-c863-4d8e-adb3-89207519d6da" alt=""><figcaption><p>An example of a RACI chart. Credit: Tech Fleet.</p></figcaption></figure>

Here's a more visual representation of a RACI, as[ developed by Tech Fleet in workshop form](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%2FGUdklnuVC3iVyiGRAX9C%2FRACI%20hat.png?alt=media&#x26;token=6ec41081-8f4d-4267-80e9-adafca411be7" alt=""><figcaption><p>Here's the visual RACI chart up close. Each person "wears different hats" on the cross-functional Agile team. Credit: Tech Fleet.</p></figcaption></figure>

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2F67Lqd79A9TGpm2VIz70V%2Fraci%20chart.png?alt=media&#x26;token=4157ddd7-f7a4-4d6b-b2ee-323c58526715" alt=""><figcaption><p>People on cross-functional teams wear different hats of responsibilities. This is a RACI chart in visual form! Credit: Tech Fleet.</p></figcaption></figure>

Learn more here:

{% content-ref url="../../agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/raci-charts" %}
[raci-charts](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)
{% endcontent-ref %}

## Working Agreements

This is not exclusive to Scrum method, but common with Scrum teams.&#x20;

Working agreements are lists of statements that outline how a team agrees to work together. They are flexible and defined by the [self-organized teams](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/self-organization) that run themselves.&#x20;

Here's what it looks like:&#x20;

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FKaqKGseInXvR0XYRvjjd%2Fworking%20agreement.png?alt=media&#x26;token=1af081e0-79d9-4fd0-857e-3ef611d50ac9" alt=""><figcaption><p>An example of a team working agreement. Credit: Tech Fleet</p></figcaption></figure>

Learn more here:

{% content-ref url="../../agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/working-agreements" %}
[working-agreements](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-related-outputs-and-deliverables/team-outputs-for-agile/agile-team-outputs-before-projects-begin/working-agreements)
{% endcontent-ref %}

## Head to the Next Lesson