> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/transformations/working-with-transformations.md).

# Working with Transformations

Deliver a Project end-to-end using requirements, tasks, testing, and governance.

### Overview

Transformations are the Projects where delivery work happens. Some UI labels may refer to Projects as Transformations.

Transformations connect scope, execution, and validation. This connection supports traceability and governance.

### Key Concepts

* **Requirement**: scope statement with acceptance criteria
* **Task**: executable work that implements scope
* **Test case**: validation steps linked to a Requirement
* **Artifact**: supporting reference linked to delivery work
* **Traceability**: relationships that connect scope to delivery and validation

### How It’s Used

Use requirements to define scope. Use tasks to execute scope. Use testing to validate scope before release.

### Benefits

* Clearer scope and reduced change confusion
* Better accountability through ownership and status tracking
* Faster audits through traceability across work items

### Setup Steps

{% stepper %}
{% step %}

### Capture requirements

Create requirements directly. Generate requirements from artifacts when enabled.

* [Requirements](/transformations/requirements.md)
* [Requirements Management](/transformations/requirements-management.md)
  {% endstep %}

{% step %}

### Plan and execute work

Break requirements into tasks. Assign ownership and track progress.

* [Task Management](/transformations/task-management.md)
* [Create and Assign Tasks](/transformations/create-and-assign-tasks.md)
  {% endstep %}

{% step %}

### Validate with testing

Create test cases and link them to requirements. Track execution and coverage.

* [Testing](/transformations/testing.md)
* [Linking Tests to Requirements](/transformations/linking-tests-to-requirements.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Link tasks and tests to requirements early.
* Keep statuses consistent across Projects.
* Capture decisions in comments on the affected items.

### Summary

Transformations connect scope, execution, and validation inside Projects. Requirements, tasks, tests, and artifacts provide end-to-end traceability.

Related:

* [Working with Views](/getting-started/working-with-views.md)
* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.md)
* [Statuses](/transformations/statuses.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/transformations/working-with-transformations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.