You manage several big projects and each project has several members from different disciplines. Each team member has several tasks that they are assigned to.
How do you know if all your resources are allocated properly? How do you know if all members of your team have the right number of tasks assigned to them and are not underutilized? How do you know if there are team members who are overbooked? If you don’t correct these shortcomings your projects are at risk!
Resource loading or resource allocation is a great tool for viewing who is doing what throughout the project life cycle. It shows all tasks assigned to each member of the project. For each task, the application shows how many hours are allocated for each day, week or month for each team member.
This information can show if one or more project members are overloaded or have time to take on more responsibility and tasks. Using this information the project manager can be allocated resources correctly and achieve optimum balance in the projects.
To have an accurate resource loading data, the application needs to have a great task management tool.
Binfire provides a resource loading page for the workspace plus a resource loading page for each project in your workspace. The workspace resource loading page shows all tasks for each member of your team for all projects you own. It displays the resource loading across all projects. So if Sue is under-loaded in one project but overloaded in another project, you can see the issue right away and correct it. If in any day or week or month a member is overloaded, the total hours are displayed in Red.
Each project has its own resource allocation page too. Here only tasks for that project and the hours each member spend on each task are shown. If a member is overloaded or underutilized this condition is flagged by the application in the project resource loading page.
To learn more about resource loading/resource allocation in Binfire visit Features page. A good reference for learning about resource loading could be found here.
Cheers,
David Robins
