Project Management: Scope Changes and Risk Mitigation

Running head: PROJECT MANAGEMENT
Project management
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
Task 1: Project status report............................................................................................................2
1.1 Project integration management............................................................................................2
Task 2: Project management plan....................................................................................................4
1.2 Risk management plan...........................................................................................................4
Task 3: MS project...........................................................................................................................8
3.1 Status report of the project.....................................................................................................8
3.1 Impact on cost and time before 20 days delay.......................................................................9
3.3 Impact on cost and time after 20 days delay........................................................................10
3.4 Crashing...............................................................................................................................11
Task 4: Reflection..........................................................................................................................12
Bibliography..................................................................................................................................14

2
PROJECT MANAGEMENT
Task 1: Project status report
1.1 Project integration management
The situation that arises faces a lot of challenges as the project “implementation of RFID
based car parking” due to scope changes from the initiation phase of the project which further
have resulted in different types of challenges as well as plans that are generally required from
time to time. It is found that another scope change request was generally provided by the client
that would push the deadline of the project by 4 weeks. It is analyzed that, it is very much
important to handle the scope changes during the different phases of the project and for which
the project managers need to take proper actions.
In order to handle the scope changes within the project, it is quite necessary to solicit the
request of scope change from different stakeholders of the project by including the project
clients, sponsors as well as project team [4]. After then it is quite important to enter the request
within the scope change log for successfully tracking the entire procedure. In addition to this,
before providing approval for the scope change procedure, it is quite necessary to analyze
whether the undertaken scope change within the project would bring benefits or not. Moreover, it
is also important to properly track the impact that the scope change mainly creates on project
budget, scope as well as time [5].Moreover, the person who is making the entire scope change
request can be successfully helpful in defining the entire business value for the project such that
proper decision about the scope change can be made which would be profitable for the project
and would also helpful in achieving the project aims and objectives.
During the planning and initiation phase, if the project manager has taken proper steps
then the problem of scope changes can have not occurred. Use of proper scope management plan

3
PROJECT MANAGEMENT
can be considered as one of the important criteria for the project which further helps in
successfully managing, controlling as well as controlling different types of inevitable changes
which would generally occur within the project [2]. The most important step in the planning
phase of the project is to properly plan the project scope which will further helpful in deciding,
documenting as well as defining the scope of the project quite effectively. The scope
management plan generally includes different types of information in order to handle different
types of unforeseen expectations within the projects for accepting the deliverables effectively.
The next step is to collect different types of project requirements in order to get proper idea
about the project stakeholders effectively. The needs as well as project requirements must be
collected properly with the help of interviews, surveys as well as by developing prototypes for
the entire project.
Thirdly, for creating the scope statement, one need to properly understand the
deliverables that are expected for properly defining what is included in the scope and what is out
of the project scope. A project scope generally helpful in serving as one of the guides within the
entire project. The project team members who are involved in the project can generally refer to
the project scope for knowing about their roles in the project [1]. Moreover, it is found that
development of proper work breakdown structure is generally created based on the scope
statement such that the documents that is generally developed needs to build an appropriate WBS
that is essentially disintegrated into smaller individual tasks. In addition to this, the WBS
generally includes clearly defined project deliverables that helps both the project team as well as
project managers with a number of manageable units of work within the project [2].
After the project deliverables are generally reviewed, it is quite necessary to approve
them successfully. Proper plan is developed for successfully validating the scope of the project