Skip to main content
System StatusContact Support
VersionOne Community

Adding a Backlog Goal/Objective on the Release Scheduling Page

Overview

Define Backlog Goals/Objectives right from the Release Scheduling page to:

  • Help keep the development efforts focused on the right business outcomes.

  • View any previously defined items using the Backlog Goals (or Objectives) tab under any project/release scope.

  • See scope-level objectives and view team-level objectives by selecting a team within the dropdown. 

Objectives can be defined in a top-down manner to help drive the features/stories that will be done.

SAFe uses the terms 'Objective' in place of 'Backlog Goal' and 'Program Increment' or its shortened version 'PI' instead of Release. While the meanings are slightly different, the functionality on this page works the same regardless of which terminology set you are using.

Bottom-Up Objectives in the SAFe Framework

For those following the SAFe framework, objectives are defined bottom-up to first represent what each team has planned within a program increment (or release), and then a set of PI-level objectives are defined to represent the business goals of the entire scope of work across all teams for the PI (program increment). Stretch objectives are those that are not committed to by the team, but may be reached, so act as a sort of extra credit if achieved.

Business Owners review the set of objectives for a team and assign a relative Business Value (typically on a 1-10 scale) for each Objective. At the end of the period when the work has been completed, the Actual Business Value delivered for each objective is captured. 

Top-Down Objectives for Traditional Management

Objectives can be defined in a top-down manner to help drive the features/stories that will be done. You will see any previously defined objectives when viewing the Objectives tab. Add new objectives at the team level to define the business goals of the team during the release.

Adding a Release/PI Objective

  1. Click on the Objectives (or Backlog Goals) tab under the appropriate release/PI scope.

  2. Click on Add Objective (or Add Backlog Goal) button.

  3. Enter the Title. 

  4. Click the Save button.

SAFe guidance is to enter business value at the team level only.

Adding a Team Objective

  1. Click on the Objectives tab under the appropriate release/PI scope.

  2. Select a team from the dropdown under the Team Objectives heading.

  3. Click on Add Objective (or Add Backlog Goal) button.

  4. Enter the Title and optionally the planned business value.

  5. Click the Save button.

Updating Actual Business Value

At the end of the selected scope period, update team-level business value to capture the amount of business value actually delivered on each team-level objective. 

  1. Click on the Objectives tab under the appropriate release/PI scope.

  2. Select a team from the dropdown under the Team Objectives heading.

  3. If the BV Actuals column is not editable, Double-click on the column heading to make it editable. 

  4. Enter the actual business value achieved for each objective. (Yes, this is  subjective measure.)

  5. Click Save. 

Program Predictability Report

The Program Predictability Report shows the percentage of business value delivered for each team within each release (or PI). View the Program Predictability report right from the Release Scheduling page using the Reports menu in the upper right.  See Program Predictability Report for additional details.

  • Was this article helpful?