Content
 BigPicture

About BigPicture

BigPicture installation and updates

Quick start with BigPicture

BigPicture Sizing Guide

Cloud vs. Server - Key Differences in BigPicture on These Platforms

BigPicture Export

Tutorials and tips

Integrations

 BigPicture release notes

BigPicture Cloud Backlog

 BigGantt

About BigGantt

BigGantt - Important Notice

BigGantt installation and updates

BigGantt Cloud Backlog

Cloud vs. Server - Key Differences in BigPicture on These Platforms

 BigGantt release notes

Shortcuts
 Release notes
 BigPicture
 Jira Cloud

 Jira Server

 Trello

 BigGantt
 Jira Cloud

 Jira Server

 BigTemplate
 Jira Cloud

 Jira Server

 BigPicture Enterprise
 Jira Cloud

 Jira Server

Knowledge Base

Tutorials and tips

Search

Attaching objectives

Depending on the approach, top-down or bottom up, the objectives should derive from each other. To show such relationship attach the team objective to to the general objective to create parent -> children relationship.

There are multiple scenarios when such an attachment is required. Achieving program increment objective like "release new version of the software" can be dependent on achieving other team objectives related to the new functionalities. From the other side some Iteration Main objective (an objective of a whole Agile Release Train) can be derived from multiple Team objectives.


The status of an attached objective is always inherited from only the last position(s) of a base objective (in the all teams) and it cannot be overwritten by a user.

An app sets it automatically based on the following rules:

  • if at least one position is set as "failed" → set an attached objective as failed
  • if at least one position is set as "open" and any position is set as "failed" → set an attached objective as open
  • if at least one position is set as "completed" and any position is set as "failed" or "open" → set an attached objective as completed
  • if all positions are set as abandoned → set an attached objective as abandoned
  • No labels