# Agile

## Basic idea

A family of adaptive process methodologies that deliver value in short iterations, prioritise responding to change over following a plan, and treat customer collaboration as the source of truth.

## Key facts

* Four Agile Manifesto values: individuals > processes; working SW > docs; collaboration > contracts; responding to change > plan.
* Iterations (sprints): 1-4 weeks; produce shippable increments.
* Practices: daily stand-up, retrospective, backlog grooming, velocity tracking.
* SCRUM, XP, Kanban are common implementations.
* Focusses on adapting to change.
* Reliant on constant and regular feedback.
* Focuses on iterative outcomes delivering value as quickly as possible and collaboratively.
* Small manageable actions and activities.
* Involvement and ownership across the team.
* Customer focus over formalised sign offs.

## Pros

* Retains flexibilty while continually producing outcomes - less rework.
* Greater communication and engagement - increased buy in across the team of the end outcome.

  **Cons**
* Difficult to do without experience - especially an experienced Scrum master.
* Large projects - co-location a problem.
* Difficult to contract suppliers.


---

# 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://isubasinghe.gitbook.io/isithas-wiki/software_engineering/management/process_and_management/agile.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.