Work Management
Work Management
The Work Management capability’s enablers include Planning and Scheduling, Changes, Risks, and Issues, and Execution and Tracking. Each capability within the Planview Capability Framework has a distinct set of features and functionality, business processes, best practices, and analytics and reports that deliver value to customers in the form of specific business outcomes.
Enablers and Business Outcomes
Planning and Scheduling
Provides work managers with the ability to view and manage all work details. They can develop the schedule or plan by defining the timeline, milestones, activities, and resources required to deliver the work. Resulting business outcomes include:
- We can implement a standardized work planning and scheduling process for projects and other planned work.
- We can plan work milestones and categorize these milestones to drive project status reporting.
- We can define the phases of work or activities at a detailed level that supports resource forecasting and planning.
- We can forecast the effort required to deliver the work, expressing this demand against the relevant organizational and resource type.
- We can use schedule templates to apply planning standards and to drive consistency and efficiency.
Changes, Risks, and Issues
Supports the definition and classification of change requests, risks, and issues and the tracking of any subsequent actions, approvals, or escalations. Resulting business outcomes include:
- We have a standard and consistent method for capturing and managing project change requests, risks, and issues.
- We have a single organization-wide repository of change request, risk, and issue information, which can be automatically consolidated into project status reports.
- We can measure the volume of project risks and group and categorize them to understand their impact on the successful delivery of projects.
- We can measure the volume of project issues and categorize them to identify projects that could deliver late, over budget, or outside scope or quality.
- We can understand the impact of change requests on project schedules and financial plans and approve or re-baseline accordingly.
Execution and Tracking
Supports the project manager to manage the project through the execution and delivery stages and to report on the overall status and health of the project. Supports the management of all work types, whether project-based or lights-on work. Resulting business outcomes include:
- We can monitor actual effort reported to timesheets and determine how this effort has contributed to project progress.
- We have a single, timely, and accurate organization-wide view of project status, with all reporting needs being met from this single version of data.
- We can view portfolio level status reports based on project status information.
- We can compare the performance of a project against financial and schedule baselines and schedule variance alerts, ensuring that remedial action takes place.
Best Practices
Standardize processes
Standardize the process for defining work and associated timelines, milestones, and activities. Create a formal and standard process for creating and closing a new Change, Risk, or Issue (CRI) to provide transparency into how work is defined and CRIs are received.
Ruthlessly prioritize
To produce successful results, work managers must proactively prioritize. Throughout the process of creating timelines, milestones, and activities, it’s critically important to remain aligned to organizational priorities and not lose sight of the overall goal while using the detailed frame of reference needed to plan work.
Centralize information
Centralize project information to monitor work progress and health, coordinate execution, and ensure timely delivery aligned to strategic objectives. Provide a single source of truth for all project details to enable visibility into dependencies, risks, and shared commitments.
Track everything
Provide access to relevant, accurate, and timely data, ideally in an easy-to-understand report or dashboard. Use visual tools that compare performance to financial and schedule baselines that enable upward and downward transparency for alignment throughout the organizational hierarchy. Actively work with stakeholders to capture KPIs that can quickly identify the need to pivot, adjust funding or capacity, or pull back.
Manage stakeholders
Understand what your stakeholders need to know about the project and provide accurate and timely updates to stakeholders. Keep an open line of clear communication with all stakeholders and keep all internal communication within a centralized location to minimize confusion.
Empower teams
PMO leaders should empower teams to deliver in a manner that supports the methods and approaches that best suit the team—whether waterfall, agile project execution, or a mixed hybrid approach. Execution today is a mix of technologies and hybrid methodologies that when aligned, provide a single line of sight that ensures strategic delivery.
Manage complexity
Follow these Work Breakdown Structure (WBS) rules to simplify risk identification, improve planning and accountability, implement smarter budget and resource allocation, and enhance visibility. Following these guidelines helps ensures no duplicate work will take place—and facilitates the management of challenges project managers face.
Avoid scope creep
Scope creep occurs when a project’s requirements or tasks change so much that it puts the project at risk for not finishing on time or within budget. Make sure you’re adhering to the boundaries laid out in the scope statement once you’re in the execution phase, and that stakeholders know the implications of making any changes.
Processes and Reports
Work management provides project managers the ability to develop a work plan or schedule by defining the timeline, milestones, activities, and resources required to deliver the work. This capability allows work managers to define and classify risks, issues, and change requests, track and manage project execution and delivery, and report on the overall status and health of projects.
Project Planning and Scheduling Process Steps
Project planning and scheduling process flow
| Process Step | Description |
|---|---|
| Define project/work breakdown structure | Define the project by building out the work breakdown structure to form the basis of the project schedule. As part of this step, you should also add dates, durations, dependencies, and assign resources to the project. The project schedule consists of any elements in the work breakdown structure (WBS) that exist below the project level in the hierarchy, such as phases, tasks, and activities as well as dates, durations, and categorizations. You can add the relevant associated resource assignment information to produce a full project delivery plan. |
| Determine durations and relationships | Determine the duration of work tasks and establish logical relationships between work items in the project schedule that you defined in the previous step. |
| Plan resources | Plan which resources will work on tasks and activities and populate the project schedule with an accurate and realistic role-based forecast in the form of resource requirements. |
| Baseline schedule | Take a baseline of the project schedule to capture a snapshot of the project's schedule as it proceeds into execution. This schedule baseline provides a record of the planned work phases, tasks, milestone dates, and durations as of the end of the planning phase to track any variances as the work progresses. |
| Assign resources | Assign resources to work on tasks and activities. Resource assignments built out in the project schedule in the form of role-based Reserves and Allocations provide a method of capturing the short-term planned resource effort for named individuals who will be working on projects. |
Change, Risk, and Issue Management Process Steps
Change, risk, and issue management process flow
| Process step | Description |
|---|---|
| Add risk |
Record the risks associated with the delivery of the work, including additional details to describe and categorize the risks. Risks identify and track things that may happen, including their impact and likelihood. Risks require a response or mitigation plan to address them. For more information: |
| Add issue |
Record the issues associated with the delivery of the work, including additional details to describe and categorize the issues. Issues identify and track things that are happening now that require an owner to take action. For more information: |
| Add change |
Record the changes associated with the delivery of the work, including additional details to describe and categorize the changes. Changes are alterations to a project's scope or expected deliverables. Changes can be a result of addressing a risk or an issue or the result of changing needs from the customer or management. For more information: |
| Transfer or move |
Modify the subtype of a change, risk, or issue (CRI) from one type to another (for example, from a change to a risk) or move a CRI from one project or work item to another as needed. |
| Close |
Close changes, risks, and issues when appropriate in a timely manner to help maintain a current overview of the factors affecting a project's progress. Use the following guidelines to close CRIs: Risks—when they are no longer determined to be risks and have not been escalated or otherwise changed. Issues—when they have been resolved or mitigated. Changes—when all associated actions are finished. |
Execution and Tracking Process Steps
Execution and tracking process steps
| Process step | Description |
|---|---|
| Do work |
Resources carry out the work that has been assigned to them. |
| Capture data on the progress of work |
As work progresses, resources' actual time spent on work is tracked, project managers update milestones and other dates as needed, and the Progressing Engine integrates actual time reported records with all the planning records in the database. Resources' time can be captured in the following ways:
|
| Review progress of work |
Track and monitor the progress being made on work using tools such as baselines to compare the current status with the planned progress. For example, project managers can monitor the scheduled and actual dates and track the variance against initial expectations, such as an initial baseline, to obtain a full understanding of the project progress. Then, they can take a new baseline to compare against a baseline taken at the start of the project. This helps project managers have a clear understanding of how a project is progressing in relation to the original baseline and identify where dates have slipped or been brought forward. Any variance from the original project baseline may have financial implications or require the proactive reassignment of resources in order to negate any negative impact on the project. |
| Plan/re-plan remaining scheduled work | Manage the schedule for the remaining scheduled work, adjusting dates and durations if necessary. |
| Manage exceptions and report on project status and progress |
Ensure the project/work status and work details are correct and current, evaluating and reprioritizing any items that aren't going to plan. Project managers can review or update the status of work on the Work and Assignments screen. Also, project stakeholders can view a summary of work status information on the WRK14 – Project (and Portfolio) Highlight Report, which is a FastTrack analytic. |
Project Planning and Scheduling Process Steps
Project planning and scheduling process flow
| Process Step | Description |
|---|---|
| Define project/work breakdown structure |
Create a new project to form the basis of the project schedule. In the Work Plan, build out the work breakdown structure (WBS) by adding work items such as sub-projects, milestones, tasks, and sub-tasks. As part of this step, you can define the project start and end date, duration, and dependencies. The project schedule consists of any elements in the WBS that exist below the project level in the hierarchy, such as projects, milestones, and tasks, as well as effort, dates, and durations. The WBS can be displayed as a grid or as an Interactive Gantt view; this view also provides alternative project schedule views in the Gantt settings, such as critical path, baseline, or baseline vs. actuals. For more information: |
| Determine durations and relationships |
Determine the dates and durations of work items and establish logical relationships between work items in the project schedule you defined in the previous step, such as establishing a successor or using Shortcuts to add inter-project dependencies to the plan. As a best practice, update the Work (effort) or Duration column in the Work Plan for each work item, and have the system automatically calculate the work item start and due dates. For more information: |
| Plan resources |
Estimate the effort required to deliver the work at the project-level or for individual work items; define resource effort in the Work (effort) column using the Work Plan grid view. Use the Work Plan Resource Planning view to check resource availability and assign resources to projects. For more information: |
| Baseline schedule |
Create a Work Plan baseline to capture a snapshot of the project's schedule as it proceeds into execution. This schedule baseline provides a record of the planned work tasks, milestones, dates, and durations to be monitored and compared to actual progress. To view baseline values and variances, add them to Work Plan columns, or search for them in the project Property Card. Baseline variances can also be viewed on the resource level in the Resource Planning view in the Work Plan. |
| Assign resources |
View resource availability and assign resources to work items using the Work Plan Related Panel, or the Resource Planning View, where project managers can detail out resource assignments by day, week, or month. If multiple resources are assigned to a work item, by default effort is spread equally across the resources, but can be adjusted on an individual basis. Note: the project work load is automatically assigned to the project manager until it is assigned to a resource. |
Change, Risk, and Issue Management Process Steps
Change, risk, and issue management process flow
| Process step | Description |
|---|---|
| Add risk |
Risks identify and track things that may happen, including their impact and likelihood, and require a response or mitigation plan to address them. Create standalone risk case types in the Risks module. Add details to the Risk Properties card to describe and categorize the risks (e.g. risk rating), then associate the risks to one or more work items in the Add Related Panel. For more information: |
| Add issue |
Issues identify and track things that are happening now that require an owner to take action. In the Issues module, create and record the issues associated with the delivery of the work, including additional details to describe and categorize the issues. |
| Convert to change |
Changes are alterations to a project's scope or expected deliverables. Changes can be the result of addressing a risk or an issue, or the result of changing needs from the customer or management. In the Requests module, create requests then associate them to the delivery of a work item in the Request Properties card. Include additional details to describe and categorize the request. Requests that capture changes to project scope, timeline, or budget can be converted into a change request once approved. Requests that are used as an idea intake can be converted into a project request once approved—however, the most efficient method is to create a new project then mark its state as Requested. Managers can view all projects by type (requested, approved, etc.) |
| Transfer or move |
Convert a change, risk, or issue from one case type to another (for example, from a change to a risk) or move a change, risk or issue from one project or work item to another as needed. Risks, issues, and changes can be associated to projects or work items as well as converted to other case types in the Property card. |
| Resolve/Close |
Close changes, risks, and issues when appropriate in a timely manner to help maintain a current overview of the factors affecting a project's progress. Establish automatic workflow rules to automate resolving a case once a work item is complete. Use the following guidelines to close changes, risks, and issues:
|
Execution and Tracking Process Steps
Execution and tracking process steps
| Process step | Description |
|---|---|
| Do work |
Resources carry out the work that has been assigned to them. |
| Capture data on the progress of work |
As work progresses, resources' actual time spent on work is tracked, and project managers update milestones and other dates as needed. Resources' time can be captured the following ways:
|
| Review progress of work |
Track and monitor work progress using baselines to compare the current status with planned progress, or use Project Roadmaps and the interactive Gantt tool for planned vs. actual, critical path, or other views of the Work Plan. For example, project managers can monitor the scheduled and actual dates and track the variance against initial expectations, such as an initial baseline, to obtain a full understanding of the project progress. Then, they can save the Work Plan as a new baseline to compare against a baseline taken at the start of the project. This helps project managers have a clear understanding of how a project is progressing in relation to the original baseline and identify where dates have slipped or been brought forward. Any variance from the original project baseline may have financial implications or require the proactive reassignment of resources in order to negate any negative impact on the project. |
| Plan/re-plan remaining scheduled work |
Manage the schedule for the remaining scheduled work, adjusting dates and durations if necessary. |
| Manage exceptions and report on project status and progress |
Ensure the project/work status and work details are correct and current, evaluating and reprioritizing any items that aren't going to plan. Review and update the status of work in the Work Plan, and generate related status reports. |
Related Capabilities
Resource Management
This capability provides a single repository of resource availability information to an organization. Managers can track and manage assignments of named resources to forecast future demand. Time reporting information is also collected.
Read moreFinancial Planning
This capability supports the planning and management of financial plan information connected to products, programs, and projects, including the creation of high-level estimates as well as approved and baseline budgets.
Read moreCapacity Planning
This capability provides the mechanism to set resource capacity targets which can be used to analyze capacity against demand, and assess the organization's ability to continue with existing investments or adopt new investments.
Read more
Supported Solutions
Project Portfolio Management
With a line of sight from strategy to delivery, Planview enables leaders to optimize program and project portfolios, balance capacity against demand, prioritize work, focus resources, and empower teams to deliver.
Read moreProduct Portfolio Management
Planview’s Product Portfolio Management solution provides scalable enterprise-level software that enables the management, prioritization, and continuous innovation of products in development.
Read moreStrategic Portfolio Management
With dynamic planning and execution, Planview’s Strategic Portfolio Management solution enables leaders to invest incrementally, quickly shift resources, and use cross-functional teams to align organizational goals to an ideal team work structure.
Read more