Skip to main content
Version: 24.3

Managing Projects or Releases

This article explains how to manage Projects or Releases in Agility.

A project (also called a release) comprises of a set of activities that must be completed in order for work to be considered done over a defined period of time.

Overview

A "project" in Digital.ai Agility is general term used to group sets of work into a hierarchical structure. You can use them to:

  • coordinate or centralize multiple backlogs using the project tree (hierarchy).
  • manage multiple projects and relationships (including projects, releases, departments, organizations, geographic locations, clients, customers, partners, etc.).

Working with Projects or Releases

Depending on your role, the following project-level options are available.

All Members

  • Select a project or release to work on in the Project Navigator
  • Perform Sprint Scheduling tasks

Project Administrators

  • Project Administration (create, edit, close, or delete projects or releases)
  • Assign project roles (or grant member access to projects) to control who can access projects
  • Assign members to a project

No matter what you call it, a project can be used to represent more than just a project. You can also use it to group releases, teams, internal organizations, clients or product owners, and even vendors.

Understanding the Project Tree
Organizations use the project tree to organize sets of related work (e.g., releases, sprints, backlog items, etc.) that will be delivered over time. Sometimes, however, the definition of a project needs to be extended as they split up large projects across incremental sets of delivery (e.g., alpha, beta, and releases), divide efforts around distributed teams, roll up multiple projects into an overall organizational view, or track the efforts of multiple modules that, together, make up a suite. In each case, the project tree can help organize it all.

Advancing your Process

  • Align project efforts with business needs using portfolio items, backlog groups, and objectives.
  • Define Target Swag and Target Estimate values for Release Capacity Planning purposes.
  • Conduct product and release planning activities
  • Defining Programs, cross-cutting groupings of projects
  • Assigning Release Schedules to a Project

Project or Release Administration

Release Scheduling

Managing Stories Backlog Items

Designing Your Project Hierarchy

Selecting Data Using the Context Navigator

Managing Stories Backlog Items

Portfolio Item Overview

Assigning Project Role

Adding or Assigning a Member to a Project

Understanding System (All Projects)

Release Scheduling

Release Capacity Planning

Watching Backlog Goal or Objective

Why can't I edit a story

Why can't some members or users see stories

Planning

Acceptance Tests

Backlog Goals or Objectives

Backlog Groups

Sprint or Iteration Scheduling

Project or Release Administration

Programs

Product

Release Planner

Managing Budgets

Retrospectives

Regression Tests

Regression Planning

Roadmapping

Strategic Themes Overview

Teams Feature Administration

Test Sets