3 ms·
But you can rate them by metrics such as are they completing all their assigned work in a reasonable amount of time, and are they producing code that's up to th
by eridius 9y ago
But you can rate them by metrics such as are they completing all their assigned work in a reasonable amount of time, and are they producing code that's up to the quality standards of the team (which could be measured by tracking whether they're introducing new bugs).
- SamReidHughes 9y agoYou can do that, and it sounds like a good idea as a backstop for subjective evaluations, but if this metric becomes important to the process, then people fight over estimates and game the bug tracker.
- gaius 9y agoBut you can rate them by metrics such as are they completing all their assigned work in a reasonable amount of time No you can't, unless you have a method for dividing a project up into blocks of exactly equal difficulty. The person who takes more time to do genuinely difficult things is probably closing fewer JIRAs than the one quickly cranking through easy ones, which would score more highly on that metric, but which is the more valuable to your organisation?
- eridius 9y agoThe metric isn't "number of completed tasks". That would be a terrible metric. The metric is "amount of valuable work completed", which is a combination of number of tasks and how much work (and value) each task is. The manager who assigns tasks should have an understanding of the expected amount of work for each task and the expected difficulty.
- jschwartzi 9y agoExcept you can't even do this unless you're managing a team of contractors who never communicate with each other or the rest of the company. Otherwise how do you propose to rate the person who is often behind on their own tasks but boosts the productivity of the rest of the team?