How to solve problems that cannot be quantified by the developer's work

According to the river Wang Hai know many internet companies will perform KPI assessment. A frontline developer's KPI workload is not only troubling the company's HR but also the developers themselves. At the end of the month how to analyze the work of each developer through effective data is a headache. Therefore, many developers KPI performance assessment is direct leadership by virtue of the feeling of playing out.

Many internet companies have opportunities to promote their jobs every year. However, the developer is ready to fill out the promotion table when the data can be taken to get a little less. Every day in busy, but busy no results.

1. Basic article1.1. Product line Ideas

Developers are the foundation of web companies, like the ingredients in the hands of chefs. A lot of the time is in the corresponding product manager, the company's business needs. Each developer is subordinate to the administrative division of the Intelligent Department has subordinate to the virtual division of the product line. Therefore, each developer is associated with at least one product line.

First step: Define the number of tasks:

The workload of the product line is the workload of the developer. Like what. A product line in the first cycle of an iteration, the product manager outputs 30 requirements. These 30 requirements were then broken down into 90 tasks by the project manager, typically the development supervisor. Suppose this product line has a total of 5 developers. The task that you collect and the leader assigns to you is 20.

Step two: Clear hours:

The processing of each task requires the Code farmer (developer) to keep code code below. After the code is finished, you need to record the hours. Many yards of the peasant association questioned, how can I clearly figure out the time I spent on the task? The answer is that it's not accurate at first, but as you and the team gradually take care of the parameters of the work, you think the value will be more and more accurate.

Step three: Identify the bug:

A task is sure to produce a bug. The 20 tasks assigned to you are unlikely to be bug-free, and if not, congratulations, you have become "Mission King". Fewer bugs can reflect the quality of task execution.

Summary: Task number + work +bug is the focus of the evaluation of developers.

PS: Many times, new recruits are dealing with bugs left by former developers. This bug can be interpreted as a task at this time. When the developer is dealing with this task, there is a bug that the developer will need to generate the bug. Also conforms to the above examination logic.

1.2. Technical point of thinking

First Step: Unit Testing

1.3. Pending

reserved

2. Promotion Chapter2.1. Patents

reserved

2.2. Publish an article

reserved

How to solve problems that cannot be quantified by the developer's work