Tutorial: Creating a First Transformation

Overview

Transformations are delivered through requirements, tasks, and tests.

This tutorial creates a small, end-to-end delivery loop in one Project.

Key Concepts

• Requirement: reviewable scope statement
• Task: owned execution work tied to scope
• Test case: verification step tied to requirements
• Traceability: links across requirements, tasks, and tests

How It’s Used

Use this tutorial after the first Project is created.

Use this tutorial to align delivery teams on a standard flow.

Benefits

• Faster conversion from discovery to execution
• Clear ownership and progress signals
• Measurable coverage through linked tests

Setup Steps

1

Create 3–5 requirements

1. Navigate to Requirements.
2. Select Create.
3. Enter a requirement statement and acceptance criteria.
4. Set an initial status, such as Draft.

Related: Requirements

2

Create tasks linked to requirements

1. Open one requirement.
2. Select Create task (or equivalent action).
3. Assign one Teammate as owner.
4. Set a due date when scheduling is needed.

Related: Create and Assign Tasks

3

Create test cases for coverage

1. Navigate to Testing.
2. Select Create test case.
3. Link the test case to the relevant requirement.
4. Set status to Draft or Ready based on readiness.

Related: Create Test Cases Related: Linking Tests to Requirements

4

Review progress in a view

1. Open Tasks.
2. Filter for open work.
3. Save the configuration as a Save View.

Related: Working with Views

Best Practices

• Keep one owner per task.
• Use statuses to signal intent, not optimism.
• Link tests early to protect coverage reporting.

Summary

The Project now contains linked requirements, tasks, and tests.

Next action:

• Add dependency signals: Dependencies and Relationships