Ranking rules configuration

 

The algorithm of the system for assigning an executor to a Task takes into account the weight of the executor (personal rating of the executor in the system) and considers three levels of competencies:

• Junior (entry-level specialist)
• Middle (competent at an intermediate level)
• Senior (high level of competence in the skill)

Not only as components of the personal rating but also from the following criteria perspective:

The user can change the criteria selection at any time during the project.

A mandatory condition for the following criteria: at least one criterion must be marked by the user, i.e., entered into the system, as a requirement for selecting performers for task execution.

• Return the matching competence level with exponential backoff team member.

Assign tasks to an executor, given all other equal factors, whose competency level either fully matches or exceeds the specified level.

For example, suppose the task specifies a Middle competency level. In that case, the system will not assign an executor with a Junior competency level but may assign an executor with a Senior competency level.

• Return the matching previous reviewer

If a task was under review and got returned, the priority will be to assign the same reviewer who returned the task (if they are available).

• Return the matching reviewer competence level with exponential backoff team member

Assign tasks to a reviewer, given all other equal factors, whose competency level either fully matches or exceeds the specified level.

For example, suppose the task's review specifies a Middle competency level. In that case, the system will not assign a reviewer with a Junior competency level but may assign a reviewer with a Senior competency level.

• Return the strict competence matching team member.

Assigning tasks to an executor, with other things being equal, the system takes into account the competence level strictly corresponding to the level defined when setting the task.

For example, if the competence level "Middle" is defined for a task, the system will assign only those executors who possess this competence. Even if the executors with "Senior" and "Junior" competencies are free and not involved in either the execution or quality control of other tasks in the project, the system will not assign them.

• Determines the executor by the number of completed predecessors

Assign the task to an executor who is most familiar with the production process, i.e., has already completed previous tasks related to the current task in a logical sequence of work within one technical process, all other things being equal.

For example, when it is impossible to start task B without completing the previous task A, i.e., these tasks are logically linked in the sequence of work, and executor #1 has completed task A, whose successful completion led to the possibility of starting the next task B in the production process, then priority will be given to this executor #1 for task B execution, as the most experienced member of the team and already familiar with the process of completing previous tasks within one technical process.

• Return the most experienced team member.

The task will be assigned to the performer who has already completed the maximum number of tasks within a single Solution Item, all other factors being equal in terms of performers' weight in the team. In other words, the performer with the most experience in completing tasks that lead to achieving the project's business goal will be assigned to the task.

For example, to implement a Solution Item, it is necessary to complete 20 technical tasks (Task). Performer #1 has already completed 11 tasks out of the total number, performer #2 has completed 5 tasks, and performer #3 has completed 1 task. Priority in assigning the next task will be given to performer #1, as the most experienced member of the team in implementing a single Solution Item.

• Only members connected to a team can perform tasks.