10X: Create Objectives

Objectives are high-level goals that teams, programs, solutions and portfolios achieve through the delivery of work. In Jira Align, you can create and organize objectives at each of these levels to ensure cross-team collaboration and focus.

Teams create team objectives at the PI Planning meeting, indicating what will be ready by the end of the PI. The objectives created by the team are then aggregated up to the program level and higher. They are built bottom-up.

Objectives may be arranged in a hierarchy: team objectives can have a program objective set as a parent, and program objectives may be children of solution or portfolio objectives. View objective hierarchies from the Objectives Tree report.

To create an objective:

  1. Select Team from the left menu bar.
  2. Under the Manage section of the menu bar, select Team Objective; the Objectives page displays.
  3. Select the Add Objective button from the top-right of the page. Use the Tier dropdown menu to select the objective level: team, program, solution, or portfolio.
  4. The panel updates with fields relevant to the selected tier. Type the name and a description for the objective in the corresponding boxes, then fill out the following fields according to the tier you’ve selected:

Portfolio objectives

  1. Select an associated portfolio from the corresponding dropdown menu.
  2. Select one or more programs and PIs from the corresponding dropdown menu.
  3. Select the owner of the objective from the corresponding dropdown menu.
  4. Select the target synchronized sprint for the objective from the corresponding dropdown menu.
  5. Set the following key dates in the Dates field. These entries are required for objectives to display on roadmaps, and are useful for waterfall projects:
    • Portfolio Ask: This date is set early in the process by the portfolio groups when they perform planning to request the delivery date for an objective.
    • Start/Initiation: This date indicates when the objective will start. It is used to do the strategic planning activities more effectively.
    • Target Completion: This date indicates the target completion date. It reflects the date the scheduler believes the objective can actually be completed (versus the Portfolio Ask date, which is the date the business wants the objective to be delivered).
  6. Set the status and health for the objective, and then select if the objective is blocked or not. Status is then displayed on a number of reports, such as the Program Board. The Health dropdown represents the health of the objective and its deliverables on the organizational level.
  7. From the Category dropdown menu, select the type of the objective:
    • Critical Path: The critical path is a series of tasks that controls the end date of the project.
    • Stretch Goal: Stretch goals push the team to work harder to meet more difficult targets.
  8. Select the theme to which your objective belongs. Portfolio objectives are the only objectives that may be associated with themes. 
  9. Select an associated Yearly goal from the corresponding dropdown menu.
  10. From the Type dropdown menu, set the type of objective:
    • Feature Finisher: An objective that lists activities needed to bring a feature to market.
    • Non-code: An objective where no coding or testing activities are needed. This type is usually used for business objectives.
    • Incremental Delivery: An objective that delivers a portion of business value to market. This type is usually used for beta or limited release evaluation periods.
    • Roadmap Milestone: Indicates the objective is a milestone to be met, generally a specific date or event.
  11. Set the planned and delivered value for the objective.
  12. Add notes if needed.
  13. Click Save.
  14. Additional sections display at the bottom of the Details panel. Use the Dependencies, Links, Epics, Capabilities, Features, Risks, and Impediments sections to add or associate these types of items to the objective. Objectives should be tied to epics or features to appear on roadmaps.
    Notes on additional fields:
    • The section for Epics, Capabilities, or Features displays depending on the objective mappings set in Portfolio Settings.
    • Optionally, you can view Related Dependencies, Risks, and/or Impediments (dependencies, risks, and impediments tied to work items (and their children) linked to your objectives, but not directly associated with the objective) if it’s been configured in your Portfolio Settings.
    • When searching for existing items by name, only items you have access to will be available.
    • Assigning a portfolio to a portfolio objective will auto-populate the Program field with all programs in the portfolio.
  15. Use the Key Results section to create and update key results that will measure the success of the objective.
  16. Click Save & Close.

Solution objectives

  1. Select an associated solution from the corresponding dropdown menu.
  2. Select one or more PIs from the corresponding dropdown menu.
  3. Select the owner of the objective from the corresponding dropdown menu.
  4. Select the target synchronized sprint for the objective from the corresponding dropdown menu.
  5. Select a parent objective from the corresponding dropdown menu.
  6. Set the following key dates in the Dates field. These entries are required for objectives to display on roadmaps, and are useful for waterfall projects:
    • Portfolio Ask: This date is set early in the process by the portfolio groups when they perform planning to request the delivery date for an objective.
    • Start/Initiation: This date indicates when the objective will start. It is used to do the strategic planning activities more effectively.
    • Target Completion: This date indicates the target completion date. It reflects the date the scheduler believes the objective can actually be completed (versus the Portfolio Ask date, which is the date the business wants the objective to be delivered).
  7. Set the status and health for the objective, and then select if the objective is blocked or not. Status is then displayed on a number of reports, such as the the Program Board. The Health dropdown represents the health of the objective and its deliverables on the organizational level.
  8. From the Category dropdown menu, select the type of the objective:
    • Critical Path: The critical path is a series of tasks that controls the end date of the project.
    • Stretch Goal: Stretch goals push the team to work harder to meet more difficult targets.
  9. From the Type dropdown menu, set the type of objective:
    • Feature Finisher: An objective that lists activities needed to bring a feature to market.
    • Non-code: An objective where no coding or testing activities are needed. This type is usually used for business objectives.
    • Incremental Delivery: An objective that delivers a portion of business value to market. This type is usually used for beta or limited release evaluation periods.
    • Roadmap Milestone: Indicates the objective is a milestone to be met, generally a specific date or event.
  10. Set the planned and delivered value for the objective.
  11. Add notes if needed.
  12. Click Save.
  13. Additional sections display at the bottom of the Details panel. Use the Dependencies, Links, Epics, Capabilities, Features, Risks, and Impediments sections to add or associate these types of items to the objective. Objectives should be tied to epics or features to appear on roadmaps.
    Notes on additional fields: 
    • The section for Epics, Capabilities, or Features displays depending on the objective mappings set in Portfolio Settings.
    • Optionally, you can view Related Dependencies, Risks, and/or Impediments (dependencies, risks, and impediments tied to work items (and their children) linked to your objectives, but not directly associated with the objective) if it’s been configured in your Portfolio Settings.
    • When searching for existing items by name, only items you have access to will be available.
    • Assigning a solution to a solution objective will auto-populate the Program field with all programs in the solution. The Program field only displays after initially saving a solution objective.
  14. Use the Key Results section to create and update key results that will measure the success of the objective.
  15. Click Save & Close.

Program objectives

  1. Select an associated program from the corresponding dropdown menu.
  2. Select a PI from the corresponding dropdown menu.
  3. Select the owner of the objective from the corresponding dropdown menu.
  4. Select one or more teams from the corresponding dropdown menu.
  5. Select the target synchronized sprint for the objective from the corresponding dropdown menu.
  6. Select a parent objective from the corresponding dropdown menu.
  7. Set the following key dates in the Dates field. These entries are required for objectives to display on roadmaps, and are useful for waterfall projects:
    • Portfolio Ask: This date is set early in the process by the portfolio groups when they perform planning to request the delivery date for an objective.
    • Start/Initiation: This date indicates when the objective will start. It is used to do the strategic planning activities more effectively.
    • Target Completion: This date indicates the target completion date. It reflects the date the scheduler believes the objective can actually be completed (versus the Portfolio Ask date, which is the date the business wants the objective to be delivered).
  8. Set the status and health for the objective, and then select if the objective is blocked or not. Status is then displayed on a number of reports, such as the Program Board. The Health dropdown represents the health of the objective and its deliverables on the organizational level.
  9. From the Category dropdown menu, select the type of the objective:
    • Critical Path: The critical path is a series of tasks that controls the end date of the project.
    • Stretch Goal: Stretch goals push the team to work harder to meet more difficult targets.
  10. From the Type dropdown menu, set the type of objective:
    • Feature Finisher: An objective that lists activities needed to bring a feature to market.
    • Non-code: An objective where no coding or testing activities are needed. This type is usually used for business objectives.
    • Incremental Delivery: An objective that delivers a portion of business value to market. This type is usually used for beta or limited release evaluation periods.
    • Roadmap Milestone: Indicates the objective is a milestone to be met, generally a specific date or event.
  11. Set the planned and delivered value for the objective.
  12. Add notes if needed.
  13. Click Save.
  14. Additional sections display at the bottom of the details panel. Use the Dependencies, Links, Epics, Capabilities, Features, Risks, and Impediments sections to add or associate these types of items to the objective. Objectives should be tied to epics or features to appear on roadmaps.
    Notes on additional fields: 
    • The section for Epics, Capabilities, or Features displays depending on the objective mappings set in Portfolio Settings.
    • Optionally, you can view Related Dependencies, Risks, and/or Impediments (dependencies, risks, and impediments tied to work items (and their children) linked to your objectives, but not directly associated with the objective) if it’s been configured in your Portfolio Settings.
    • When searching for existing items by name, only items you have access to will be available.
  15. Use the Key Results section to create and update key results that will measure the success of the objective.
  16. Click Save & Close.

Team objectives

  1. Select an associated program from the corresponding dropdown menu.
  2. Select a PI from the corresponding dropdown menu.
  3. Select the owner of the objective from the corresponding dropdown menu.
  4. Select the primary team from the corresponding dropdown menu.
  5. Select the target synchronized sprint for the objective from the corresponding dropdown menu.
    Note: Target sync sprints are required for team objectives.
  6. Select a parent objective from the corresponding dropdown menu.
  7. Set the following key dates in the Dates field. These entries are required for objectives to display on roadmaps, and are useful for waterfall projects:
    • Portfolio Ask: This date is set early in the process by the portfolio groups when they perform planning to request the delivery date for an objective.
    • Start/Initiation: This date indicates when the objective will start. It is used to do the strategic planning activities more effectively.
    • Target Completion: This date indicates the target completion date. It reflects the date the scheduler believes the objective can actually be completed (versus the Portfolio Ask date, which is the date the business wants the objective to be delivered).
  8. Set the status and health for the objective, and then select if the objective is blocked or not. Status is then displayed on a number of reports, such as the Program Board. The Health dropdown represents the health of the objective and its deliverables on the organizational level.
  9. From the Category dropdown menu, select the type of the objective:
    • Critical Path: The critical path is a series of tasks that controls the end date of the project.
    • Stretch Goal: Stretch goals push the team to work harder to meet more difficult targets.
  10. From the Type dropdown menu, set the type of objective:
    • Feature Finisher: An objective that lists activities needed to bring a feature to market.
    • Non-code: An objective where no coding or testing activities are needed. This type is usually used for business objectives.
    • Incremental Delivery: An objective that delivers a portion of business value to market. This type is usually used for beta or limited release evaluation periods.
    • Roadmap Milestone: Indicates the objective is a milestone to be met, generally a specific date or event.
  11. Set the planned and delivered value for the objective.
  12. Add notes if needed.
  13. Click Save.
  14. Additional sections display at the bottom of the details panel. Use the Dependencies, Links, Epics, Capabilities, Features, Risks, and Impediments sections to add or associate these types of items to the objective. Objectives should be tied to epics or features to appear on roadmaps.
    Notes on additional fields:
    • The section for Epics, Capabilities, or Features displays depending on the objective mappings set in Portfolio Settings.
    • Optionally, you can view Related Dependencies, Risks, and/or Impediments (dependencies, risks, and impediments tied to work items (and their children) linked to your objectives, but not directly associated with the objective) if it’s been configured in your Portfolio Settings.
    • When searching for existing items by name, only items you have access to will be available.
  15. Use the Key Results section to create and update key results that will measure the success of the objective.
  16. Click Save & Close.

See also

10X: Visualize Roadmaps in Work View

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.