Task period alignment allows integration of the Board with the Gantt or, in other words, presenting the agile plans using a traditional waterfall approach.
The task can be aligned with the time box defined using the Agile Schedule.
Task's period will not align with the box's period. The fields mapped as start and end dates will not get updated when a task is planned in one of the time boxes.
This setting is recommended for purely agile teams who do not want to use BigPicture as a 'Solution Roadmap' and present their plans using the Gantt module.
(see Iteration 1)
Task's period will align exactly with the box's period. The fields mapped as start and end dates will get updated to match the boxes start and end dates when a task is planned in one of the time boxes.
This setting is recommended for agile and non agile teams who want to use BigPicture as a Roadmap tool and present their plans using the Gantt module.
(see Iteration 2)
Task's period will align to the start or end date of the box without changing the tasks duration (if possible). The fields mapped as start and end dates will get updated, when a task is planned in one of the time boxes, such that the task will start on the start date of the box (when moved to a future box) or end on the end date of the box if moved to a previous box.
This setting is recommended for agile and non agile teams who want to use BigPicture as a Roadmap tool o present their plans using the Gantt module in a waterfall way.
Please note, that this sync mechanism is:
- one-directional: a task period is being updated once the task planned for a Box, but the task is not planned for a Box once task period is updated,
- one-shot operation: a task period is always being updated once the task is planned for a Box (e.g. using Board module), but if you adjust the task period once it is planned for a box (e.g. on the Gantt module) the app will not validate the adjustment even if a new period would not fit the Box's period.
The above-mentioned update of the task period will be executed properly only if all task scheduling rules (parent-child relation, task mode, inward dependency, etc.) allow executing the operation. E.g. if Story has a parent task in the task structure that has a "lock" mode set, the app may not update the Story period if it exceeds the parent period after the update.
Please note, that once a task period is rescheduled, it may trigger a rescheduling of related tasks (linked tasks or parent/children in the task structure).
To learn how to show time boxes using the Gantt module go to New Gantt - Show - Time boxes.