Principle of Project Management

Running head: PRINCIPLE OF PROJECT MANAGEMENT
Principle of project management
Name of the Student
Name of the University
Author’s Note

1
PRINCIPLE OF PROJECT MANAGEMENT
Introduction
An analysis is made on the principles of project management for discussing the range
of key contexts that can be collectively used as a learning body in the foundation of project
management. For the discussion tailoring, project lifecycle and project management
methodologies are evaluated for identifying their relation with each other, constraints and
implication in the project management. The topics are critically evaluated in terms of current
professional practice for the identification of interdependency between them.
Tailoring
A project is treated as unique and it is necessary that the processes involved in project
management is needed to be tailored for ensuring that the project is completed successfully.
Tailoring can happen on any time for the application of process in the project and there are
different situations where there is a need to adjust the processes for ensuring that the project
is completed within the scheduled time and budget (Pmi.org. 2019). A project management
methodology is used by the organization for allowing adjustment for management of different
types of projects. A list of base processes is created for its utilization in the current project
and allowing adding processes for meeting the base requirement. All the possible processes
can be identified for the removal of some processes aligning the project needs. An analysis
and evaluation is made on the history of project management, project lifecycle and tailoring
for finding its significance in the current professional practice (Kerzner & Kerzner 2017).
The interdependency, implication and constraints are identified and described for finding its
impact on the development of project.
Project management knowledge areas
There are different areas of knowledge for project management such as project
integration management, scope management, schedule management, cost management,

2
PRINCIPLE OF PROJECT MANAGEMENT
quality management, resource management, communication management, risk management,
procure and stakeholder management. The project management plan is created and
distributed to the stakeholders for its approval (Uhl & Gollenia 2016). The project knowledge
is needed to be managed for acquisition of additional knowledge and active management is
needed for ensuring that the project is completed within the budget and time. The progress of
work is needed to be monitored and an earned value analysis and project status report and
identification changes in the project. An integration change control is needed to be performed
for the management of change request forms and the change logs.
The project scope management is necessary to be included since the change of the
scope is the main cause of changes in the project. It is important to define the project
boundaries and the progress is needed to be monitored. After starting the project a scope
management plan is needed to be developed and the requirements are needed to be collected
from different sources. A scope statement is needed to be created for defining the scope and
creating a WBS and breaking the project work (Pmi.org. 2019). The scope is needed to be
validated for its approval from the client and monitor and control the project. A scope control
is needed to be maintained and the statement should be revisited for completing the current
project status.
Project schedule management is also necessary for the development of the project
schedule and dividing the project tasks and assign a start and finish dates to them. The project
that involves a change is needed to be continuously baselined and the plan is needed to be
updated (Kerzner 2017). For planning the schedule management the activities are needed to
be defined and the task should be sequenced according to their order or relationships. It is
also essential to control the schedule at a regular project interval status for analysing whether
the project is before or after the point of status (Muller 2017).