WashU IT has adopted a 32-hour resource allocation model based on vendor-recommended best practices to improve our resource planning. Our goal is to allocate or plan, on average, 32 hours per week per resource for project or service operation (i.e., service op) projects, leaving 8 hours weekly for administrative (i.e., admin) tasks. While the plan sets a 32-hour target, it is an estimate that can be adjusted based on project demands or individual needs. Resource and project managers should collaborate to make the appropriate allocations.
Allocation and Capacity Explained
- Allocation: The time that a resource has been planned to work on a project/service op.
- Capacity: The total allocatable time that a resource has for planned work. This is set at 32 hours per week. However, 8 hours per week, which is ideally used for admin time, may be used for project/service ops if needed. Admin time includes all-hands meetings, department meetings, training, vacation, sick time, and other non-project work. Based on reports and research, “on average” over longer periods, admin time averages out to around 8 hours per week.
Allocations represent the amount of time a resource is planned to work on project/service op tasks. These estimates are used to plan project work and forecast WashU IT labor for future projects. Resource and Project Managers collaborate to determine allocations. As estimates, the allocations planned for a person’s work probably won’t exactly match the time entered on the timesheet. It is important that what is entered on the timesheet accurately reflects the time that was worked.
Using a 32-hour allocation capacity for project and service ops improves our planning and forecasting capabilities. This, in turn, helps us to plan our time and resources more effectively so we can heighten our focus on delivering the ImpacT Strategic Plan.
Check out the Capacity Management project page to find the exciting enhancements the project team is working on.
Please Contact us with any questions you may have.