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

1

Capture requirements

Create requirements directly. Generate requirements from artifacts when enabled.

• Requirements
• Requirements Management

2

Plan and execute work

Break requirements into tasks. Assign ownership and track progress.

• Task Management
• Create and Assign Tasks

3

Validate with testing

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

• Testing
• Linking Tests to Requirements

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
• Project Settings and Configuration
• Statuses