F
F
fr1zzer2017-06-12 15:41:30
Project management
fr1zzer, 2017-06-12 15:41:30

How to analyze the work of developers in Hubstaff?

Hubstaff has such a line as activity, tell me what kind of activity a developer should have (for example, there is at least 70%) and if there are possible examples ..

Answer the question

In order to leave comments, you need to log in

5 answer(s)
T
tema_sun, 2017-06-12
@tema_sun

None. The developer is not a loader. Most of my working time I think, not write code. At this point, activity may be at zero.
Evaluating activity in isolation from the result is a meaningless exercise.

S
sim3x, 2017-06-12
@sim3x

None
There is a suspicion that someone can do the job faster + better?
Find a replacement and pay her

I
Igor, 2017-06-18
@imikh

It depends on the task, on the developer, on the technologies.
For example, a junior on a new task for him with unfamiliar technology will obviously google and read a lot, which means the activity will be lower.
If the task requires mostly coding and the employee may not google, then the activity will be higher.
All this can be assessed by a person who is familiar with the task, the level of the employee and has similar experience with such trackers, i.e. representing from experience which task/employee should show which activity.
We work a lot with such trackers, so we can evaluate our employees.

N
Novamoscow, 2019-03-13
@Novamoscow

You can nagovnokodit without Google and the investigation, with the slogan "yes, and so it will do", or you can understand the problem with your mind (Google), find a more correct / suitable solution.
In the first option - High activity
In the second option - lower than in the first
option. Third option - YOU do not understand and do not understand what your employees are doing, maybe just nothing.
And about the activity of 60%. Try to work in the office for 8 hours with more than 60% activity.

K
Kotaro Hiba, 2020-12-16
@lina666

I don’t know how relevant the answer is for this holivar, I worked for half a year on hubstaff and that’s what method is good in my opinion.
Evaluate the task, say 8 hours, coordinate.
Proger starts doing it, coped with it in 4 hours and passed the task, well done, get it for 8, because initially they agreed on this amount, did not pass the task, we are looking for a reason, the tracker is needed for this and it doesn’t matter what activity will be shown in the statistics (for example, I have moments when I can sit and think for 20-30 minutes, and then describe the algorithm in 2 lines, and sometimes when I write several options at once and select by random. the same)
The proger will be pleased knowing that I will quickly and well do the tasks, I will do 2 tasks freely in a day that are calculated for 8 hours, I will receive a salary in 2 days and the employer will not be left in the loser. Well, this is how I see it.
Just an example from life, there was a fierce blockage, we set 2 tasks in parallel on different projects, both were calculated for 40 hours, I did both spent 48 hours on them in total, I got it as a result as for one task, although I gave it my all for a week complete, insulting
UPD in the same way and in the opposite direction, too, should work.
If, for example, if a task designed for 8 hours was done by 10, either you explain yourself or you get it for 8
I think it will be fair

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question