# Continuous Improvement

## Video Version 

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

## Where We Are in the Agile Pyramid

We're far along in the Agile self-actualization pyramid! Teams who are psychologically safe service leaders who are self-organized in their work can start continuously improving their work.

<figure><img src="https://2497269768-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaLipvRvacoLEyzC54aBy%2Fuploads%2FEDeVa7j9lSBlPLt8WwZs%2Fimage.png?alt=media&#x26;token=acd3571b-e31d-4650-927b-41795a3f9672" alt=""><figcaption></figcaption></figure>

## Continuous Improvement

Agile teams fail often. They do not look at failure in judgement, but celebration. Failure could mean that their plan didn't follow through. It could mean that a teammate didn't do something they said, or they tried and it didn't work out. Failure could mean that someone didn't show up.&#x20;

Everything that "fails" on an Agile team is looked at as learning opportunities. Teams intentionally build small value in their releases so that they can deliver quickly and "fail fast", or learn from the delivery.&#x20;

Teams who are continuously improving use retrospectives and reflection moments to listen and learn from feedback received.

Teams who are continuously improving aren't perfectionists, and they don't treat their teammates as perfectionists. They experiment with something that mat not work, and deliver quickly to get feedback quickly. They iterate by making adjustments based on feedback received.&#x20;

In order to do this, there must be a strong foundation of [psychological safety](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/psychological-safety), [service leadership in teammates](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/service-leadership), and [self-organization](https://guide.techfleet.org/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/self-organization) among leadership. These three tenets enable teams to continuously progress, continuously learn from mistakes, continuously improve.

### Continuous Improvement Video

Here's a video about failing fast and continuous improvement:

{% embed url="<https://www.youtube.com/watch?v=2elv7NtJmNo>" %}
Credit: <https://www.youtube.com/watch?v=2elv7NtJmNo>
{% endembed %}

### Continuous Improvement Checklist

1. Does your team deliver work incrementally in small chunks?
2. Does your team often reflect on previous work and identify areas of improvement?&#x20;
3. Does your team celebrate failure as progress and learning opportunities?
4. Does your team constantly involve clients, stakeholders, and users in feedback sessions?
5. Does your team work on the most important things at any given time, and deliver them quickly?

## 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-teamwork/making-strong-agile-teams/self-actualized-agile-teams/continuous-improvement.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.