Keep abreast of work dynamics – using coding to measure team effectiveness

Time:2020-10-1

In the process of agile R & D, or in the re inventory stage after the end of a project, measuring and analyzing the workload, completed workload and work dynamics of team members in the cycle can make managers clearly understand the workload and work efficiency of team members; team members can also view each other’s projects, recent work trends or recent events.

The main function of effectiveness measurement is to count the number of planned items, the number of completed items and the number of wikis edited by team members for analysis. The data will be displayed on the trend panel. In addition, you can set your own group and add other members to quickly view the recent work overview of team members.

Preparation for use

The team owner or administrator can check the “view page” permission of “performance measurement” for the corresponding user group in [team management] > [permission configuration]. After checking, the workbench of the member of the user group will appear the function entry of performance measurement.

Trend panel

The panel will reflect the workload trend chart of the added members, which is displayed in three data dimensions: the number of planned items, the number of completed items, and the number of Wiki edits. You can select three statistical cycle views of day, week and month to view, and drag the date left and right through the scroll wheel horizontal axis below.

Number of planned events

The total number of events arranged by the processor at the start and end times in a time cycle will be counted. The items included in the statistics include epic, demand, task, defect and subtask.

  • If the start and end times are filled in, the number of events in each day of the time cycle is + 1;
  • If only the start time is filled in, the number of events on the day of the start time + 1;
  • If only the deadline is filled in, then the number of events on the day of deadline + 1.

For specific counting principle, please refer to the counting method of planned items.

Number of completed items

The total number of items completed by the processor in a fixed period will be counted. The do definition here covers epic, requirement, task, defect, and subtask. If a completion operation is made on these items, i.e. the status type changes from “not completed” to “completed”, the item is considered as completed.

  • If the status type is still “completed” within the time cycle and after the cycle ends, the number of completed items is + 1.

For the specific counting principle, please refer to the counting method of completed items.

Edit wiki count

The number of Wiki articles updated by team members will be counted. If the same document is modified and “submit document” is executed in the same period, the number of wikis edited is counted as one.

Add members and group management

In “add members”, you can add members in an item by their name or by searching for an item with one click. Members added to the chart can be removed. In the group drop-down component, you can add, delete, and rename groups. The added members will enter the currently selected group by default. The grouping is set by users themselves and will not be displayed in the team. It belongs to the personalized view function.

Member work overview page

Click any member in the effectiveness measurement page to enter the member’s work overview page. The page contains:

  • Members’ names and portraits;
  • The latest active time;
  • Projects involved;
  • Recent events;
  • Recent developments of the member.

Recent events

The statistical contents of recent events include:

  • Completed, query the items completed in the past one month, and arrange them in reverse order according to the completion time;
  • In progress, the items whose status type is “in progress” are sorted in reverse order according to the deadline;
  • If not started, the items whose status type is “not started” will be sorted in reverse order according to the deadline.

Work trends

Work dynamic is the daily collaboration dynamic of members, which can be queried by classification, including:

  • Project collaboration
  • Code warehouse
  • Continuous integration
  • Continuous deployment
  • Wiki
  • File network disk

Authority control

The permission module involved in this function is named performance measurement and has “view” permission. Each team owner and project manager will check the “view function” permission point by default.

Count method details

Counting method of planned items

  • If the start and end times are filled in, the number of events in each day in this time period is + 1;
  • If only the start time is filled in, the number of events on the day of the start time + 1;
  • If only the deadline is filled in, then the number of events on the day of deadline + 1.

For example, table 1:

matter start time End time
Item a January 1, 2020 January 5, 2020
Item b January 3, 2020 January 6, 2020
Item C January 4, 2020 Not set
Item D Not set January 3, 2020

According to the data in Table 1, the statistical results of the member’s planning events are as follows:

date Number of planned events matter
January 1, 2020 1 A
January 2, 2020 1 A
January 3, 2020 3 ABD
January 4, 2020 3 ABC
January 5, 2020 2 AB
January 6, 2020 1 B
January 7, 2020 0

If the time of the same event spans two cycles, then + 1 is counted in each of the two cycles. For example, if the start and deadline of event a is January 25, 2020 to February 4, 2020, then event a is counted as one event in January and February.

Counting method of completed items

If an item is completed once in a cycle and the status type is “completed” after the cycle, the number of completed items will be + 1.

Calculation method of items repeatedly opened and completed

  • If an item has been completed in a cycle, but the status type before the end of the cycle is “completed”, the number of completed items will be + 1;
  • If the item has been completed in a cycle, but the status type before the end of the cycle is not “completed”, then the number of completed items will not be contributed;
  • If an item is completed in the first cycle and is not opened until the second cycle, and the status type before the end of the second cycle is “completed”, the number of items completed in these two cycles is + 1.

For example, table 2 shows the status of event a from January to April

time State type action
January 1, 2020 Not started New creation
January 2, 2020 have in hand Transfer to processing
January 3, 2020 Completed operation completed
January 20, 2020 Not started Reopen
January 25, 2020 Completed operation completed
February 15, 2020 Not started Reopen
March 2, 2020 Completed operation completed
March 3, 2020 Not started Reopen
March 30, 2020 Completed operation completed
April 1, 2020 Completed Maintenance completed
April 30, 2020 Completed No operation

Then the number of completed items of item a from January to April are: 1, 0, 1, 0.

Learn more about coding