If, during work on tasks in SI, a user encounters the need to redistribute tasks among several teams or transfer work from one task to another team within the SI, they can manually move tasks to another SI or utilize automatic work redistribution by creating multiple SI with the necessary tasks and dependencies between them (both within SI and between tasks in these SI).
For example:
Requirement: Distribute work in the current SI among multiple teams. Action: Select an existing task in the current SI to transfer to a new one. If this task has dependencies, System: Automatically create one or two SI according to the sequence of work defined in the current SI.
For example, in SI.45, there are three tasks Task.1, Task.2, Task.3.
Option 1: T.1 is a predecessor for T.2 and T.3. T.1 needs to be assigned to another team. The system will divide SI.45 into 2 solutions: SI.45 with T.2, T.3 and SI.46 with T.1. SI.46 is a predecessor for SI.45.
Option 2: T.2 is a predecessor for T.3. T.2 needs to be assigned to another team. The system will divide SI.45 into 3 solutions: SI.45 with T.1, SI.46 with T.2, SI.47 with T.3. SI.45 and SI.46 are predecessors for SI.47.
Thus, the system divides SI into the necessary number of additional SI and determines dependencies between them based on the sequence of work execution in the current SI. If the task that needs to be assigned to another team has work before and after it with dependencies, the system will divide it into three SI. If the task is at the beginning or end of work, then into two SI.
Rules and limitations:
✅ Work can be divided in any SI. Automatic division preserves:
-
all existing SI data and connections (efforts, teams)
-
all existing data and connections of tasks within SI. If a task with a predecessor ends up in another solution, the Predecessor-Successor connection is established at the SI level.
-
dividing into no more than three SI is allowed.
✅ Editing data and connections in divided and newly created SI.
✅ Creating new tasks in SI.
✅ Editing data and connections in tasks according to existing rules.
If a task that needs to be assigned to another team is at the stage:
-
To Do with an assigned performer - the task remains at the To Do stage, but the assignment will be removed, and a new performer will be assigned to the task.
-
Doing, QMP - the task is returned to the To Do stage, work is stopped, and the assignment from the performer will be removed.
Comments
0 comments
Please sign in to leave a comment.