Quality controls

Quality controls stage of task verification. The system allows users to customize the Quality controls stages, which are unique stages created by the user based on the industry, internal company policies, or the need for additional or intermediate quality checks for implemented tasks and project objectives. 

User Actions: 

 

1. Estimating the Quality control Stage 

Each stage can have one of the following estimation criteria:

• Fixed effort estimate - setting fixed timeframes in units of time (working days and hours).

• Doing multiplier estimate - a multiplier for estimates defined in tasks. The system calculates it as a multiplier of the estimated task estimate.  

For example, if the performer estimated the task completion time as 10 hours, and the defined multiplier is 0.5, the system will calculate the estimate as 5 hours for reviewing that task.

• Empty estimate—no estimates are provided. The system does not define or consider estimates for the quality control sub-stage. 

2. Definition of the verification type at the Quality control stage 

Generic It is general and does not have any specific conditions.

Visual review It involves visual artifacts and multiple versions of these artifacts in the task. Depending on the user's functional role, it provides the following capabilities: 

• Uploading visual artifacts. 
• Adding an unlimited number of artifact versions. 
• Leaving comments on artifact versions. 
• Accepting existing or adding new comments during the review process across different artifact versions. 

Pull Request Review It presupposes the presence of pull requests in the task. Depending on the functional role, it provides the user with the ability to:

• Add pull requests
• Edit pull requests
• Delete pull requests
• Preview pull requests
• Accept pull requests

3. Selection of criteria for assigning a reviewer at the Quality control stage 

Same or higher: Assigning a task, all other factors being equal in terms of the members' weights, to an executor whose level of competence either completely matches or exceeds the level specified when setting the task or when assigning skills and competence at the Quality controls stage.  

For example, if the task specifies a Middle competency, the system will not assign an executor with Junior competency but may assign one with Senior competency. 

Higher: Assigning a task, all other factors being equal in terms of the members' weights, to an executor whose level of competence is higher than the level specified when setting the task or when assigning skills and competence at the Quality controls stage.  

For example, if the task specifies a Middle competency, the system will not assign an executor with Junior competency but may assign one with Senior competency. 

Strict: Assigning a task, all other factors being equal in terms of the members' weights, to an executor with a level of competence strictly corresponding to the level specified when setting the task or when assigning skills and competence at the Quality controls stage.  

For example, if the task specifies a Middle competency, the system will exclusively assign executors who possess this competency. Even if executors with Senior and Junior competencies are available and not engaged in the execution or quality review of other project tasks, the system will not assign them. 

4. Assigning a SKILL to the Quality control stage 

Each created stage can be assigned a separate Skill different from the one used for the workflow of that stage. This means that different reviewers can be assigned to the stages. 

• If a separate skill is not assigned to the stage, the system will assign a user with the same skill and level. If the "Strict competence matching team member" option is turned off in the company settings, and a user with the exact skill and level is not found, the system will assign a user with the same skill but a higher level. 

• If a subskill is assigned to the stage, the system will specifically assign a user with that subskill without considering the parent skill. The skill and level must match explicitly. If the "Strict competence matching team member" option is disabled, and a user with the exact subskill and level is not found, the system will assign a user with the same skill but a higher level. 

Rules for editing the stage: 

• Creating a Stage: This can be done at any time, specifically on the Quality controls screen. 

• Editing a Stage:  

• Includes renaming the stage and changing its color at any time. 
• Defining/Changing Stage Estimation Criteria: This can be done at any time, allowing for the adjustment of estimation criteria for the stage. 
• Selecting the type of verification at a specific stage at any time if there are no tasks in the stage 
• Selecting the type of verification at a specific stage at any time if there are tasks in the stage: 

✅ Allowed when there are no assigned reviewers. 

❌ Not allowed when a reviewer is assigned. 

❌ Not allowed when the reviewer has started reviewing the task. 

• Assigning a Skill to an Individual Stage: If no tasks have been assigned to the stage, this can be done at any time. 
• Assigning/Replacing a Skill for an Individual Stage with Tasks: 

✅ Allowed if no reviewer is assigned to the tasks. 

❌ Not allowed if a reviewer is already assigned. 

❌ Not allowed if the reviewer has started reviewing the tasks. 

• Deleting a Stage: 

✅ If there are no tasks assigned to the Quality controls stage: Allowed.

✅ If the stage doesn't have a separate assigned Skill: Allowed.

✅ If the stage has a separate assigned Skill: Allowed. 

❌ If there are tasks assigned to the Quality controls stage: Not allowed.