Review how the Progressing Engine and resource assignment types are used to support a series of use case scenarios
Overview of Business Outcomes and Use Cases
A strong partnership of the customer’s Core Team and Planview’s Implementation Team is the key to the success of the implementation.
Each team brings to the implementation group:
- Expertise of current and desired business processes and outcomes,
- Plus, in depth knowledge of the application features and business rules.
Planview Enterprise offers robust functionalities, that can be used to support the planning of work, assignment of resources, and tracking of progress.
Each customer solution is crafted to produce the desired business outcomes by combining functionalities and appropriate configuration options. This is achieved through understanding of the customer’s desired business outcomes and the Planview Enterprise business rules. The following sections detail seven different business outcome driven use cases.
Business Outcome Driven Use Cases
Details and examples of how these use cases are implemented in Planview Enterprise follow the tables.
Use Case |
Business Outcome |
Description |
|
---|---|---|---|
Project Stage/ Milestone Date Tracking Only |
The progress of projects can be monitored by planning, baselining, and tracking the dates of key governance points in the project process. |
The project schedule only includes the phases/stages of the project and key (normally governance) milestones that represent the start and/or end of the phases of the project and key events/decision points in the process. Information about the milestones is included in status reports. There is no resource planning or time tracking. |
|
Actual Hours Time Tracking Only |
Project/Work actual hours are available for costing and recharge processes, including for capitalisation purposes. |
There is no forward planning of project dates or the resources required to deliver the project. The project WBS is composed simply of time reporting codes/work items. |
|
Project Stage/ Milestone Date Tracking and Actual Hours Time Tracking |
UC1 and UC2 |
There is no forward planning of resource demand. The project WBS is planned out with the dates/durations of each stage and key milestones. Resource timesheet hours are recorded against time reporting “buckets” and the key project milestones are managed in the schedule alongside these bucket work items. |
|
Resource Demand and Assignment Tracking Only |
Forward looking resource demand is available to drive capacity planning and work prioritization decisions. |
High-level project plans drive capacity planning and resource assignment management, no time reporting – answers the question; “who is assigned to which project.” |
|
High Level Schedule, Resource Planning and Time Tracking |
UC1, UC2 and UC4 |
High-level project plans drive capacity planning and resource assignment management using a work breakdown structure based on Phases/Stages, high level planning/time tracking activities and milestones. Resource demand and assignments are tracked and resources report actual hours through timesheets against the high level planning activities. |
|
High Level Schedule, Resource Budget Management and Time Tracking |
UC1, UC2 and UC4, plus consumption and forecasting of budgeted project hours. |
High-level capacity planning and resource assignment management, with the planning and tracking of the consumption of budgeted project hours. Project hours are captured and are used to determine progress on the project. |
|
Mature Rolling Wave Activity Level Planning & tracking |
UC1, UC2, UC4, UC6, plus detailed project schedule management |
System supports a fully mature rolling wave planning process; role based demand, soft booking of resources and activity planning and tracking. |
Use Case Recommendations
Use Case |
Run Progressing Engine? |
Use Time sheets? |
Use Progress as Planned? |
Assignment Types to Use |
Use Manual Status |
Progress Allocations Option (WBS16) |
Progress Reserves Option (WBS17) |
Progress Requirements Option (WBS15) |
Recomm-ended Max Utilization |
|
---|---|---|---|---|---|---|---|---|---|---|
Project Stage/Milestone Date Tracking Only |
Yes |
No |
Recommended –just adjust exceptions |
N/A |
Yes For all non-progressed as planned work |
N/A |
N/A |
N/A |
N/A |
|
Actual Hours Time Tracking Only |
Yes |
Yes (Authorizations) |
N/A |
Authorizations only |
N/A |
N/A |
N/A
|
N/A |
N/A |
|
Project Stage/Milestone Date Tracking and Actual Hours Time Tracking |
Yes |
Yes (Authorizations) |
Yes |
Authorizations only |
Yes |
N/A |
N/A
|
N/A |
N/A |
|
Resource Demand and Assignment Tracking Only |
Yes |
No |
Yes |
Requirements and Reserves |
Yes |
Expire Effort |
Expire Effort
|
Expire Effort |
N/A |
|
High Level Schedule, Resource Planning and Time Tracking |
Yes |
Yes |
Yes |
Requirements and Allocations |
Yes if non-time reported work items (milestones) |
Expire Effort |
Expire Effort |
Expire Effort |
150% |
|
High Level Schedule, Resource Budget Management, and Time Tracking |
Yes |
Yes (Allocations) |
Recommended –just adjust exceptions |
Requirements and Allocations |
Yes (Milestones and non-time entry work) |
Respect Finish Date |
Respect Finish Date
|
Maintain Effort |
150% |
|
Mature Rolling Wave Activity Level Planning and Tracking |
Yes |
Yes (Allocations) |
Optional |
Requirements, Reserves and Allocations |
Yes |
Respect Duration |
Expire Effort
|
Maintain Effort
|
125 |
Use Case 1 – Project Stage/ Milestone Date Tracking Only |
---|
Business Outcome: Key project milestones can be tracked and reported on.
Figure 2: Project Stage/ Milestone Date Tracking Only |
Use Case 2 – Actual Time Tracking Only for Cost Capture/Recharge |
---|
Business Outcome: Actual resource hours spent on projects are captured and costed for financial reporting/recharging.
Figure 3: Actual Time Tracking Only for Cost Capture/Recharge |
Use Case 3 – Project Milestone Date and Actual Time Tracking |
---|
Business Outcome: Key project milestones and actual resource hours spent on projects are captured and costed for financial reporting/recharging.
Other consideration:
Figure 4: Project Milestone Date and Actual Time Tracking |
Use Case 4 – Resource Demand and Assignment Tracking Only (no time reporting) |
---|
Business Outcome:Forward resource demand is forecasted at the role and named resource levels, driving capacity planning without resource time tracking.
Other considerations:
Figure 5: Resource Demand and Assignment Tracking Only (no time reporting) |
Use Case 5 – High-Level Schedule, Resource Planning and Time Tracking |
---|
Business Outcome: Forward resource demand is forecasted at the role and named resource levels, key project milestones and actual resource hours spent on projects are captured and costed for driving capacity planning and financial reporting/recharging.
Figure 6: Use Case 5 - High-Level Schedule, Resource Planning and Time Tracking |
Use Case 6 – High-Level Schedule, Resource Budget Management and Time Tracking |
---|
Business Outcome: Forward resource demand is forecasted at the role and named resource level, key project milestones and actual resource hours spent on projects are captured and costed for driving capacity planning, tracking of consumption for budgeted hours, and financial reporting/recharging.
Figure 7: Use Case 6 - High-Level Schedule, Resource Budget Management and Time Tracking |
Use Case 7 – Mature Rolling Wave, Activity Level Planning and Tracking |
---|
Business Outcome: Forward resource demand is forecasted at the role and named resource levels driving capacity planning. Full visibility into the day by day utilization of resources. Project actual hours are captured for costing/recharging.
Figure 8: Use Case 7 - Mature Rolling Wave, Activity Level Planning, and Tracking
Figure 9: Use Case 7 - Mature Rolling Wave, Activity Level Planning, and Tracking |