Simplify Task Management with Task Relationships
In this blog post, I would like to explain how to simplify task management with task relationships.
- Maintaining task relations:
- Link start and end date of an item to an event (e.g., timeboxes, releases or predecessors/successor)
- Create a chain of related tasks
An excellent illustration of the functionality’s power is through cut over planning. In our Roadmap, we have an accelerator and as we approach the end of implementation, the cut over phase becomes crucial, where it meticulously transfers all the remaining data from the old legacy system to the new system. This functionality was precisely designed to address when you are nearing the go live. There are certain critical cut over activities that must follow a specific sequence of cut over tasks to ensure readiness for the actual go live.
1. Maintaining task relations: We can establish relationships between tasks. This means you can create connections and dependencies among different tasks, making it easier to efficiently manage dependencies and track the flow of work. For instance, if you have one task serving as a predecessor and another task designated as its successor, by establishing and managing these connections you gain better control over your tasks.
2. Link start and end date of an item to an event (e.g., timeboxes, releases or predecessors/successor)
A new feature is the ability to link the start and end dates of task. This means you can choose a start date and by opening the dropdown menu, you can customize the task relationship. You have the following options to choose:
- Pick a specific date or
- Link to a Milestone
- Link to an assigned Release
- Link to an assigned Timebox
- Or link a successor task to its Predecessor.
For instance, you can set Task 2 to begin automatically when Task 1 is completed. This helps simplify task scheduling.
- Pick a specific date – Choose a particular date to link with your task’s start and end dates.
- Link to a Milestone – Link your task to a milestone. For instance, if a task must be completed in the ”prepare” phase, link it to the milestone representing the end of the prepare phase.
3.Link to an assigned Timebox – Create a link between your task and a Timebox, allowing you to align the task’s start date with the start of the related Timebox and the end date with its end.
4.Link to an assigned Release – Link your task with a Release, allowing you to align the Task’s timing with the start and end dates of the release its linked to.
5.Link a successor Task to its Predecessor – Create a clear dependency between tasks by linking a task to its predecessor, ensuring that one Task will commence only after the completion of its predecessor, streamlining your workflow. (Note: For roadmap tasks the predecessor/successor relation cannot be changed)
3. Create a chain of related tasks
Recently, we introduced a new feature, Dynamic schedule, which allows you to have the flexibility to specify the duration of tasks. Previously, you could only link the start and end dates, but now you can select a start date and set a specific duration for example; 4 days and the planned end date will be automatically calculated based on these inputs. By combining these functionalities, you gain the capability to seamlessly chain tasks together.
This functionality now offers the ability to Daisy Chain Tasks. A daisy chain refers to a series of interconnected tasks that are interdependent. If a delay occurs in one task or if some tasks have the potential to end earlier than planned, it can affect the entire chain. It implies that when you delay a Task by a day, the entire sequence of linked Tasks experiences a corresponding delay. In the past, project leaders had to modify other tasks in response to interdependencies manually. This feature enables a solitary Task adjustment to automatically extend its delay throughout the entire chain, eliminating the necessity for manual modifications. The Daisy chain task feature combines dynamic scheduling and automatic delay adjustment for greater efficiency.
Relationships need to be maintained.
As a result, the planned completion date is calculated by the system
Repeat this step for all relevant tasks within your series of tasks.
Have you tested this functionality? Your voice is a valuable part of our community. We encourage you to share your insights and experiences with us. Please feel free to leave your feedback in the comment section.