How is the development work evaluation process organized?

Question

Project management

Good evening everyone!
I wondered how the process of evaluating development work is organized in different organizations.
We evaluate the dev lead, and who is yours, and how is this process built?
Interested in the assessment is not in terms of money, but how and by whom you calculate the required time and labor costs for the development of a particular functionality.

Answer 1

Depends on what is being assessed. In the context of the initial assessment, both the team leader and one of the team members can do it. Delegation and all that.
Well, the tasks themselves are evaluated by the developers who will do them.

Answer 2

Good question!
I also asked these questions and came to the conclusion that it is necessary for the company to develop an automated evaluation system.
There are 2 types of work evaluation:
1. Predicted
2. Actual (in terms of time and what was done)
Abstracting by analogy (the most simplified technical process):
Imagine that you are building a brick house.
1. Transferring one brick - costs 5r (5sec)
2. Coating the surface with mortar - 3r (3sec)
3. Putting a brick on the surface covered with mortar - 1r (1sec)
4. Removing excess mortar - 2r (2sec)
Now, suppose that some workers carry one brick at a time, and one wears 10 at a time.
Should someone who wears 10 bricks at once pay 5 * 10?
Or "steal" his hard earned money if he does it faster?
Those. we are talking about the complexity of the algorithm (nesting, recursion, etc.)
As a result : the analysis of the labor costs of simple operations and the complexity of algorithms using these operations allow us to identify the real cost of developing a part or the entire project as a whole.
1. Predicting initially and having received the actual work done - you can compare and, based on this difference, adjust the forecast algorithm.
2. Payment is always carried out according to the projected labor costs together with the developers.
3. If something requires research work, this is done in the first place and the cost of this work is negotiated in advance.

Answer 3

Question in the forehead - what project development methodologies do you work with? If it all comes down to showing the dev of the task and evaluating it, after 20 minutes of tinkering in the inspector is one thing, if you work in an agile way it's another. You can create a stack of tasks with execution time (approximate of course) and track the effectiveness of tasks, let's say on the same Gantt chart

Answer 4

Evaluation of the functionality and the final product are two different things. You can collect feature evaluations from developers, and multiply by 2, for example. But with the final product (I'm talking more about long projects), everything is very complicated. In practice, no one has clear descriptions, the product is constantly refined, and approaching the launch, the team finds itself in a pile of small tasks that have nothing to do with the finished functionality. It may even be worthwhile for some teams to move away from the practice of committing to the final product by breaking development into stages.