Direct and Manage Project Work is the process of overseeing and carrying out the tasks listed in the project management plan (PMP) and putting accepted changes into action in order to reach the project’s goals. The main benefit of this method is that it manages the project work and deliverables as a whole, which increases the chances of the project succeeding. The project as a whole goes through this process. Below is a picture of the Direct and Manage Project Work process’s inputs, tools and Techniques , and outputs.
Directing and managing project work means carrying out the planned project actions to meet goals and finish the project deliverables. It is possible to see what tools are available, make good use of them, and make changes to project plans based on data and information about work performance. The project application area has a direct effect on the Direct and Manage Project Work method. As directed in the project management plan, deliverables are the results of the steps taken to complete the project work as planned and expected.
Direct And Manage Project Work: Inputs
Project Management Plan
This process can use any part of the project management plan.
Project Documents
It’s possible to use the following project documents as inputs for this process:
Change log
The change log contains the status of all change requests.
Lessons learned register
We use what we’ve learned to make the job better and stop making the same mistakes again. The register helps you figure out where to put rules or guidelines so that everyone on the team follows them.
Milestone list
The milestone list shows the scheduled dates for specific milestones
Project communications
Performance reports, deliverable progress, and other information made by the project are all part of project communications.
Project schedule.
At least a list of work tasks, their lengths, resources needed, and expected start and end dates are on the schedule.
Requirements Traceability Matrix
The requirements traceability matrix helps you keep your focus on the end results by connecting product requirements to the outputs that meet them.
Risk Register
The risk register lists threats and chances that could affect the project’s execution.
Risk Report
The risk report lists the sources of the overall project risk and gives a brief summary of each discovered project risk.
Approved Change Requests
The Perform Integrated Change Control process creates accepted change requests. These are the requests that have been looked over by the project manager or, if necessary, the change control board (CCB) and given the go-ahead to be implemented. The accepted change request could be a fix for a problem, a way to keep it from happening, or a way to fix a mistake. The project team plans and carries out approved change requests, which can have an effect on any part of the project or the project management plan. Approved change requests can also make changes to parts of the official project management plan or project documents.
Enterprise Environmental Factors
Some of the enterprise environment factors that can affect the Direct and Manage Project Work (pmp)process are the following: Infrastructure (such as existing facilities and capital equipment); Stakeholder risk thresholds (such as the percentage of cost overruns that are acceptable); and Organizational structure, culture, management practices, and sustainability.
Organizational Process Assets
The following organizational process assets can have an effect on the Direct and Manage Project Work (pmp) process:
- standard policies, processes, and routines for the organization;
- issue and defect management processes that spell out controls for issues and defects, how to find and fix issues and defects, and how to keep track of action items;
- problem and defect management database(s) that store historical information about issues and defects, how they were fixed, and the results of actions taken;
- It’s a performance measurement database that gathers and shares measurement information on products and processes.
- change control and risk control procedures; and
- project information from previous projects
Direct And Manage Project Work: Tools And Techniques
Expert Judgment
You should look for advice from people or groups who have expert knowledge or training in the following areas: Technical understanding of the project’s focus area and industry, management of costs and budgets, legal and purchasing, laws and rules, and leadership of the organization.
Project Management Information System (PMIS)
The PMIS gives you access to software tools for information technology (IT), like scheduling software, work authorization systems, configuration management systems, information collection and distribution systems, and more. It also connects you to other online automated systems, like corporate knowledge base repositories. This method can include automated ways to track and report on key performance indicators (KPIs).
Meetings
Project managers and leaders use meetings to talk about and deal with important issues related to the project. The project manager, the project team, and other relevant parties interested in or affected by the topics being discussed may be present. To make sure everyone participates properly, each person should have a clear job. Among the different kinds of meetings that can happen are kick-off, technical, sprint or iteration planning, Scrum daily standups, steering group, problem-solving, progress and review meetings.
Direct And Manage Project Work (pmp ): Outputs
Deliverables
In order to finish a process, phase, or project, you need to produce a deliverable, which is a unique and verifiable product, result, or ability to do a job. Deliverables are usually the things that the project produces, but they can also be parts of the project management plan.
When you finish the first revision of a product, you should use change control. Configuration management tools and methods help keep track of all the different versions or editions of a deliverable, like software, documents, and building blocks.
Work Performance Data
Work performance data are the raw observations and measurements identified during activities being performed to carry out the project work. There is a common belief that data are the most basic units of knowledge that other processes can use to find out more. As work is done, data is collected and sent to the managing processes to be analyzed further.
Tasks finished, key performance indicators (KPIs), technical performance measures, actual start and end dates of planned activities, story points completed, deliverables status, schedule progress, number of change requests, number of defects, actual costs, actual durations, and more are all types of work performance data.
Issue Log
There will often be problems, gaps, errors, or conflicts that come up out of the blue during the execution of a project. The project manager will need to take action to make sure these issues don’t affect the project’s performance. The issue log is a project document that keeps track of all the problems. Some types of data on problems are:
- Issue type,
- Who raised the issue and when,
- Description,
- Priority,
- Who is assigned to the issue,
- Target resolution date,
- Status, and
- Final solution
The issue log will help the project manager keep track of and handle problems more effectively, making sure they are looked into and fixed. This process creates the issue log for the first time, but problems can happen at any point in the project. During the life cycle of the project, monitoring and control actions keep the issue log up to date.
Change Requests
This is an official request to change any document, deliverable, or baseline. For any problems that come up during the project, people can make change requests. These requests can change the project’s policies or procedures, the scope of the project or product, its cost or budget, its schedule, or the quality of its results. Some change requests include the necessary repair or preventative actions to keep bad things from happening later in the project. Anyone involved in the project can ask for a change. The Perform Integrated Change Control process takes change requests and lets you decide what to do with them. Requests for changes can come from inside or outside the project, and they can be required by law or contract. Requests for changes may include :
Corrective action
a planned action that brings the project work back in line with the project management plan
Preventive action
The act of making sure that the future work on the project is in line with the project management plan.
defect repair.
A planned action to change a nonconforming product or part of a product
Updates.
Changes made to officially approved project documents, plans, etc., to include new or changed ideas or content
Project Management Plan Updates
People in the company have to fill out a change request for any changes they want to make to the project management plan. Because of this process, any part of the project management plan may need a change request.
Project Documents Updates
During this process, project documents may be updated with the following, but not only those:
- Activity list.
- Assumption log
- Lessons learned register
- Requirements documentation
- risk register
- stakeholder register.
Organizational Process Assets Updates
If you follow this process, you can update any organization process asset.
References :