June's average performance?

U

underwater2019-02-27 13:40:34

Project management

underwater, 2019-02-27 13:40:34

It is clear that I am discussing a spherical horse in a vacuum, but for an initial guide, I would like to hear opinions.
For example, let's take a long week sprint, 40 hours. Everyone knows that a programmer does not code for 8 hours in a row and usually the average performance of a strong middle is about 70%, that is, in its sprint we throw tasks for 28-32 hours depending on the complexity, and then we look at what and how, the question is not in that.
The question is, what is the performance of the June? 1.5 times worse? IN 2? If there was a weekly sprint of one June, then it turns out that he can throw tasks for 12-15 hours out of 40, right?
It’s clear that the tasks are different, that some juniors won’t do it, etc., etc., that’s not the point, but if I have a team of one middle and four juniors, two of which are closer to the middles, can I take the number of 90 hours as a guide for a weekly sprint tasks (30 + 15 + 15 + 15 + 15) or will it be fat?

Reply

Answer the question

In order to leave comments, you need to log in

4 answer(s)

I

Ilya Soldatenkov, 2019-02-27
@dyfran

Why evaluate the performance of a jun in the number of task hours at all?
Isn't it better to evaluate the complexity of these tasks in the upgrade? And of course, put a certain limit, say, a person must "join" in a month. You do not expect that June will be very useful for business at first, do you?

P

Puma Thailand, 2019-02-27
@opium

And why should he do less than hours? The hours are absolute and June works great as well as middle and senior

G

GavriKos, 2019-02-27
@GavriKos

So calculate empirically. There should always be "adaptation time" when performance and overall performance in different situations and with different tasks are pretended. And then it's all individually and lined up.

P

Peter, 2019-02-27
@petermzg

If you equate programming with hammering nails, then the middle will most likely score more per unit of time. But programming is not the simplest operation. Some tasks require more experience, others skill, others cunning, perseverance, and also both together. And in fact, it may turn out that the middle will do much less tasks per sprint than the junior, and the senior will not be able to cope at all.