Resourcing people on projects and expected hours on timecodes are very different things. Resourcing is about getting an intent/need to have a person working on a project for certain hours in certain time periods. It is the cat herding part of the product. Expected hours on timecodes can be used if you want to specifically allocate certain hours for a person for a particular project. The values can be used for a variety of reporting, but isn’t directly linked to resourcing.
- This is the process of scheduling people onto a project, showing the hours per week (soon can be done as daily or monthly) that you are wanting them to work.
- It helps with letting people know what they have coming up and is an important tool for the business to see which people/teams etc are stretched or have availability.
- Within each project the future resourcing is used to calculate projected burn and feed into projected margin calculations
Expected hours on timecodes
- This is different to resourcing and can be used to set a number of hours “budget” for a person.
- It is a good tool for communicating to a person the total number of hours they will have available on that particular timecode.
- On their timesheet a person can see how many hours they have remaining (total expected hours less worked so far).
- Project Managers can use it as a way to see which timecodes (or parts of projects) are tracking to the expected hours.
- There is a system setting where you can prevent people exceeding their allocated hours for a timecode when doing their timesheet.