Skip to main content
System StatusContact Support
VersionOne Community

Managing Projects/Releases

This feature is available in all editions.

editions-all.png

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

Overview

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

  • coordinate/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/Releases

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

All Members

Project Administrators

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/customers, and even vendors. See Project Administration for details.

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