Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Utilisation Rate #374

Closed
ghost opened this issue Aug 18, 2017 · 7 comments
Closed

Utilisation Rate #374

ghost opened this issue Aug 18, 2017 · 7 comments
Assignees
Labels
finance priority-1 Highest priority issue. This is costing us money every minute that passes. question A question needs to be answered before progress can be made on this issue

Comments

@ghost
Copy link

ghost commented Aug 18, 2017

Linked to #321

Utilisation Rate for each person in the team/company

@nelsonic can you confirm that this is the utilisation rate on client projects to the nearest half hour divided by a 35h week?

@ghost ghost added finance priority-1 Highest priority issue. This is costing us money every minute that passes. labels Aug 18, 2017
@ghost ghost assigned nelsonic Aug 18, 2017
@ghost ghost added the question A question needs to be answered before progress can be made on this issue label Sep 20, 2017
@ghost
Copy link
Author

ghost commented Oct 26, 2017

@nelsonic 🙌 not sure if you saw the above q so thought I would post again

@nelsonic
Copy link
Member

Yes, utilisation is based on statutory working hours (35h/week).

@nelsonic nelsonic assigned ghost and unassigned nelsonic Nov 20, 2017
@ghost
Copy link
Author

ghost commented Nov 20, 2017

@nelsonic statutory maximum working hours are 48 hours a week. The reason I asked to confirm if you meant 35 hours or not is because our contractor contracts are 7 hours a day and our supplier agreements provide for 7 hour days. Whereas our employee contracts are 40 hours a week.

@ghost ghost assigned nelsonic and unassigned ghost Nov 20, 2017
@nelsonic
Copy link
Member

Yes, EU Working Time Directive is 48h/week,
so technically it would not be "unreasonable" for us to expect people to work 48h/week,
however we don't; we prefer people to have a "work-life-balance_
and therefore only expect 35 hours of (effective) work per week.
The remaining 5h (to make up 40h/wk) should be spent on learning, spikes or internal work.

AFAIK we only bill clients for 7h per day (and don't charge "over time").
Therefore developers should log 7h per day in order to determine their "utilisation"
(7h x 5 days = 35h/week)

@iteles iteles removed the question A question needs to be answered before progress can be made on this issue label Nov 21, 2017
@iteles
Copy link
Member

iteles commented Feb 6, 2018

@rub1e Let's take a look at how best to get step one of this done this week please, it's been an open priority-1 issue for the last 9 months. 😒

  • Figure out what we need in terms of Xero/spreadsheets/info to get this done
  • Gather info and send out support queries where/if needed
  • Get it done (to be expanded on of course) 😊

@iteles iteles assigned rub1e and unassigned nelsonic Feb 6, 2018
@rub1e
Copy link
Member

rub1e commented Feb 7, 2018

We can split Utilisation Rate (UR) into two:

  • Resource - how much of their time are people actually spending working
  • Billable - how much of the time are people actually spending working on billable projects

So, following #374 (comment), we'd start with contracted hours of 40h/wk, multiply it by 52 weeks, take off holiday allowance & public holidays, and the result would be our baseline hours.

So then the task is just to figure out how many hours the employee has worked (resource), and how many they've worked on client projects (billable) - and divide that by the baseline to get their utilisation rate.

Freelancers

The above works is a fairly simple estimation of how utilised people are based on their contracted hours - so obviously that works just fine for contracted employees.

But for freelancers, that's less obviously helpful as their resource UR should be 100% and their billable UR is the same, except for a few freelancers who've worked on internal non-billable projects.

So my question to you, @nelsonic, is how are you wanting to use the results of this?

Instinct is that something like per-project profit rate would be more usable data than UR when it comes to freelancers, but if you had something else in mind, or if I've got the wrong end of the stick, just let me know 😺

@rub1e rub1e added the question A question needs to be answered before progress can be made on this issue label Feb 7, 2018
@iteles iteles unassigned rub1e Feb 7, 2018
@iteles iteles assigned rub1e and unassigned nelsonic May 24, 2018
@rub1e
Copy link
Member

rub1e commented Jun 5, 2018

I should have closed this a while ago - Nelson agreed verbally with #374 (comment), so this is closed in favour of #373

@rub1e rub1e closed this as completed Jun 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
finance priority-1 Highest priority issue. This is costing us money every minute that passes. question A question needs to be answered before progress can be made on this issue
Projects
None yet
Development

No branches or pull requests

3 participants