> For the complete documentation index, see [llms.txt](https://guide.techfleet.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.techfleet.org/project-portal/project-success-handbook/keys-to-project-success/approaching-deliverables-in-an-agile-way.md).

# Approaching Deliverables in an Agile Way

## The Agile Ways of Building Products and Services

For any type of project, teams who live the Agile Ways of Work behave differently when building products and services. They interact with each other, build working results, collaborate with users to define needs, and respond to change. Learn more here in the Agile Handbook:

{% content-ref url="/pages/AwZlhESQWjhhmFWby5xX" %}
[Building MVP's and MMP's with Agile](/agile-training-portal/agile-handbook/agile-philosophies/building-mvps-and-mmps-with-agile.md)
{% endcontent-ref %}

## Milestones Happen in Parallel

Different kinds of teamwork happens at the same time instead of in stages on an Agile team project. For instance, a team may start with drafting a vision before they start researching to use it as a grounding for research to test assumptions. After doing research they may iterate on the vision and the product definition while also iterating on designs. 

The sooner teams deliver the work outcomes into the hands of users in the [Agile project lifecycle,](/project-portal/project-success-handbook/project-components/agile-project-lifecycle.md) the sooner they will be able to validate if their direction is the right way to go.

## Deliverables Are Constantly Adjusted

Agile teams should never treat work as "final" or "done", but simply the "next version". If they are [always performing discovery](/project-portal/project-success-handbook/project-components/project-milestones/continuous-discovery-milestone.md), they are always learning new things. If they are always learning new things they should always be shifting their scope and vision. Only they can decide whether, how, and when as a [self-organized team](/agile-training-portal/agile-handbook/agile-teamwork/making-strong-agile-teams/self-actualized-agile-teams/self-organization.md). 

## Head to the Next Lesson


---

# 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://guide.techfleet.org/project-portal/project-success-handbook/keys-to-project-success/approaching-deliverables-in-an-agile-way.md?ask=<question>&goal=<endgoal>
```

`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.