For the complete documentation index, see llms.txt. This page is also available as Markdown.

Projects

Use Projects to manage one transformation initiative end-to-end.

Overview

Projects are delivery containers inside an Organization. They hold the work needed to deliver one initiative.

Key Concepts

  • Project scope: requirements, tasks, tests, artifacts, and settings for delivery work

  • Project configuration: defaults, fields, and roles that shape day-to-day workflows

  • Project sections: grouping mechanism for phases, sprints, and workstreams

How It’s Used

Create a Project per initiative, such as an ERP implementation phase or a process redesign effort. Use Projects to track scope (requirements), execution (tasks), and validation (testing).

Benefits

  • Clean separation of initiatives within an Organization

  • Repeatable governance through templates and settings

  • Better reporting and review through consistent configuration

Setup Steps

1

Create a Project

2

Configure Project settings

3

Define Project sections (optional)

Best Practices

  • Establish naming conventions before creating many Projects.

  • Configure custom fields before importing large volumes of work items.

  • Keep shared settings stable and review changes quarterly.

Summary

Projects hold delivery work for one initiative. Project settings and sections standardize execution and reporting.

Related:

Last updated