Can different users record different % of hours logged?

[PhilSpo]

Im looking for a solution for different users to be able to log different % of hours worked.

For example.

Developer A is experienced and for every hour logged they do 1 hours worth of work.

Developer B is junior and for every hour logged they do 0.75 hours worth of work.

Developer C is new and for every hour logged they do 0.5 hours worth of work.

Is there any way in Jira we can set this up (or addons) so that when we do our end of month reporting we have the 'hours logged' report per developer and the 'hours worth of work logged' per developer?

Cheers

Phil

[Bill Sheboy · Accepted solution]

Hi @PhilSpo 

Would you please explain the problem you are trying to solve?

It seems you want to track development time keeping and a separate measure of people's "value" or "worth".  What are you gonna do with that second measure?

Best regards,

Bill

[PhilSpo]

Hello @Bill Sheboy 

Yes of course.

So for our reporting we use WIP (work in progress). Once an issue is resolved we can add up the hours logged on that task and add it to the WIP figure and this lets us know how much chargeable work we have so far delivered for the month.

We are finding that although the hours are being logged, the amount of work being done doesn't match up.

For example we take 2000 hours to deploy a product to a new customer. We are finding that if Developer A (as the example above) does all the work it is complete in 2000 Hrs. 

If Developer C does the work although they have logged 2000 hours we are only actually half way through the project.

So we somehow need to set a % of 1 hour against developers and then that figure gets added up for each hour they spend in timesheets so we can see how much work is actually done.

I hope this makes sense.

Cheers

Phil

[Nic Brough -Adaptavist-]

Ah, that's not a problem you should try to be solving by bodging the numbers.

Your resourcing and planning needs to start putting in accurate estimates, not bodging completion after you've got the estimates wrong.

[PhilSpo]

Hi @Nic Brough -Adaptavist- 

I totally agree with you 100%

 Lets just say my question doesn't reflect my own views on the matter!

Cheers

Phil

[Bill Sheboy]

Hi, and thanks for this discussion.

One better approach to handle delivery is to: split work into small, valuable, similar-sized chunks; count the chunks; and determine progress by paying attention and adjusting as you go, while improving your experience and skills.

However...Sometimes teams decide to forecast effort and use that forecast for various things: understanding complexity, assessing improvement, and...yes...sometimes forecasting delivery time frames.

When doing this last one, please consider two practices to improve chances success:

• Determine what you know, believe, and don't know. Then define an appropriately sized contingency estimate to add to the end of the forecast.  Intentionally draw from the contingency bucket when needed.
• People are different, as you first noted.  They have different skills and experiences, and as they learn, they can delivery more effectively.  Cross-training helps speed learning.  Until then, base forecasts on anyone on a team doing the work, even the less experienced people, as that is more likely to be closer to what eventually happens.

Best regards,

Bill

[PhilSpo]

Thanks @Bill Sheboy 

These are solutions we should definitely try to implement.

Phil

[Nic Brough -Adaptavist-]

No, because there is no adjustment.  If someone needs to log an hour, while the next one needs to log a half, then they should log 1h and 30m respectively.