Cross-Project Releases

A Release is a period of time during which a defined scope of work should be completed. The scope can include work from one or more projects. Cross-project Releases allow you to plan and track your backlog from several projects at once. They provide you with aggregated status while still allowing you to drill into each project. Cross-project Releases help you to organize and coordinate between all of your teams in a portfolio initiative or in a Release train.

Requires Targetprocess 3.5.4+

Create a Cross-Project Release

Click on +Add at the top left corner and select the Release option from the menu. You can then choose which projects a Release is related to. The projects which are selected in the Projects & Teams Context menu are available.

You can also create a Release from any Board, List or Timeline via Quick Add.

The detailed review about how to add Lanes and Cards with the in-view Quick Add is available here.

Release Detailed View

You can change the set of assigned projects at any time from the Release's detailed view. On the Projects tab you can assign more projects by choosing from existing list or creating a new project. It is possible to un-assign a project only if a release does not contain work from that project.

Plan Work

Work in Targetprocess is hierarchical. You can assign Features, User Stories, and Bugs to a Cross-Project Release.

Here is a board that shows Projects as rows and Releases as columns. This view is beneficial for a management view of work across Projects that share the same release schedule. To assign a single new work item or multiple items in a batch to a Release simply use drag-and-drop.

Let us consider an example about work visibility in a Release:

We have the following projects: Project A, Project B, and Project C. We want to release a piece of new functionality which would include work from Project A and Project B. We create a new Release called Release AB and assign it to Project A and Project B. Now we can assign work from those two Projects to this Release. Work from Project C can not be assigned to Release AB.

If you select only Project C in the Projects & Teams Context menu, you will not see Release AB. If you select either Project A or Project B then Release AB will be visible.

If you have access to Project A only, you will still see Release AB. When looking at User Stories from this Release, you will see User Stories from Project A only.

Effort Units

It is not possible to create a Release across Projects with different effort units (story points and ideal hours). If you assign a Release to several Projects and then change the effort units for the process of one of the projects, you will see a warning.

The recommended workaround solution in this case is to run two Releases in parallel, one using points and the other using hours. Aside from changing your effort units, creating a second cross-project Release is the only reasonable option.

Tracking Progress

The easiest way to track the progress of a Release is the Burndown chart. It provides you with aggregated status across several Projects while still being able to drill into each Project. With the help of the Project filter you can filter the content of the report by one or several Projects assigned to a Release. Find more information about how to track progress with the Burn Down chart here.

Custom Fields

Only if all Projects in a cross-project Release have the same process specific custom fields will these custom fields be available. A mix of different custom fields from different processes is not supported. If projects have different processes, then a cross-project Release takes the process of the first chosen project upon creation. If you need custom fields from different processes, let us know, and we’ll consider this for future improvements.

Use Cases

Iterative Development

For the iterative development we suggest that you use Team Iterations. A Team Iteration is similar to a Project Iteration, but it is not related to a single Project. It is related to a team and can contain work from multiple Projects.

Project iterations are supported for single-project releases only. In the case of cross-project Releases, you can not use Project Iterations but Team Iterations only. If the combination of Team Iterations and cross-project Releases doesn’t meet the needs of the way you work, tell us about your case.

In the view below Team Iterations are rows and Releases are columns. The Release “CRM Release v3.5.4” includes work from several Projects. There are three teams working parallel to another to contribute work in this Release.  Each of the teams works according to its own schedule planning Team Iterations. Each Team Iteration may include work from one or several Projects assigned to the Release.

From this view each Team Lead sees the performance of his team in the global Release and a Release Manager can understand the status of the entire Release by aggregating data from multiple teams.

There is no direct relationship between a Team Iteration and a Release because Releases relate to Projects and Team Iterations relate to Teams. If you use Team Iterations for Release work decomposition, you need to manually assign work to both the Release and Team Iteration.

If you want to change this behavior, please give us your feedback which will help us create future improvements!

Program Release

The Program level in Targetprocess gives you the ability to share certain aspects between multiple Projects and Teams. First, select all projects from a particular Program by one click from the top Projects & Team menu. Then create a Release for the Projects of the chosen Program using the +Add button or a Quick Add functionality.

Working on the Program level it is important to have a high-level vision of the overall progress and be able to drill into the details. List View mode works great for that.

Filters for Releases

You can select, hide or highlight data in Views and Visual Reports by Releases and related properties using Advanced Filters for Releases.

  • Kiley Hykawy

    When is it appropriate to use cross-project releases (multiple projects) versus just having one project with multiple teams? There seems to be an overlap in the use case and want to understand what would drive one kind of solution.

  • Sergey Gnedin

    Kiley Hykawy Cross-projects releases are not exactly related to multiple teams.

    Let me illustrate that with an example. Say, you have two projects: iOs app and Android app. You introduce a new feature that affects both mobile versions. In this case it may be natural to use Cross-Project release to track it: user stories from different projects will go there.

    Whether you need Teams is a different story. It is somewhat described at https://guide.targetprocess.co… . You may also want to discuss it with your dedicated Product Specialist. Feel free to contact support@targetprocess.com if you do not have his contacts.

  • Grégoire Bélorgey

    Are there any plans to allow linking iterations to a multi-project release ? We don’t need multi-projects iterations, just the ability to link our iterations on both projects to the upcoming common releases !

  • Anna Ko

    Cross-project Releases were added to Targetprocess as a new feature with very minimal scope.
    Please consider using Team Iterations (they are cross-project but single-cross-project-team tied) instead – as a workaround: https://guide.targetprocess.co….
    You may also want to vote for this idea: http://tp3.uservoice.com/forum

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.

Get started for free

How many people would be using Targetprocess?
  • Myself
  • 2–20
  • 21–100
  • 101–1000
  • 1000+
By clicking Continue you agree to our Terms of service and Privacy policy