Estimated Resources -> Scheduled Resources -> Actual Resources Used
- An estimate project is created using an estimate form
- Deliverables or ad hoc resources are planned in the estimate
- A workflow is utilized for Estimate approval
- Once approved the Estimate form is pushed and mapped to a pipeline project
- The pipeline project is created with pipeline tasks created from estimate form
- The user can then move around the pipeline tasks to find openings in the resource planner
- The pipeline is approved via a workflow and the status changes from pipeline to live project
Capacity planning allows managers to forecast resourcing requirements based on estimates
The Form Builder is updated to include new element type options:
The attribute matrix has been updated for an additional output type 'Role'. A role will be added as a new column and hours can be assigned to the role within the column. This will translate to the number of role hours required for the deliverable (a deliverable can be a row in the matrix). When adding a role, the user will be prompted to select from the current list of roles configured within the system.
The workflow builder has been updated to allow for new triggers:
• To create a Pipeline Project from an Estimate form. Consisting of tasks built from the estimate form.
• To turn a Pipeline Project into a live Project
• The existing Form to Project trigger is updated to create Project tasks from the form elements
An Estimate Form to gather adhoc, OOP and scheduled resources by role or name:
An estimate is then created and progressed through an approval workflow to create a Pipeline Project:
Tasks within these projects are flagged as Pipeline Tasks. These tasks and resources will be excluded from live reporting, as they have not yet been approved. Pipeline projects will be used for Capacity planning i.e. if this project and tasks come in and are approved how will it impact my existing resourcing.
In a parent pipeline project, there may be a number of sub pipeline projects. As the parent is still a pipeline, the subs module will default to the pipeline project view, since this is the status of the parent project.
Likewise, if the parent project is live, the subs module will default to the standard live view.
In this way, the view for both the parent and subs are the same i.e. both pipeline or both live.
Pipeline Projects can be filtered in the Resource Planner View:
Work in the estimate assigned to roles can be assigned to available resources in the pipeline project now
Once resourced and approved the Pipeline Project can be converted to Live via a workflow or directly from the Pipeline Project. When Live we can monitor Estimated (Budget) vs Scheduled.
Estimated, Forecasted and Burned View in each project:
And from the project List View in the Resource Planner:
Tasks are updated to allow you to assign them to Roles - then you can assign them to users either from the Task view in the project or direct in the Resource Planner
Then later the Task can be allocated either completely to one or distributed to various users in the role: