Project Management Case Study: Analysis of Bespoke System Project

This project management case study analyzes the development of a bespoke system, covering essential aspects such as scope definition, cost estimation, stakeholder management, and work breakdown structures. It includes detailed estimates using analogous, parametric, and bottom-up approaches, along with a stakeholder management plan identifying key stakeholders and their influence. The case study also presents a comprehensive work breakdown structure, communication plan, and risk analysis. Furthermore, it features a procurement plan, Gantt chart, critical path analysis, critical chain analysis, cost baseline, and S-curve to illustrate project scheduling, cost control, and progress tracking. The document concludes with a bibliography of relevant project management resources.

Running head: PROJECT MANAGEMENT
Case Study-Bespoke System
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
1. Scope statement...........................................................................................................................2
2. Estimates......................................................................................................................................2
3. Stakeholder management plan.....................................................................................................5
4. Work breakdown structure..........................................................................................................7
5. Communication plan....................................................................................................................7
6. Risk analysis................................................................................................................................9
7. Procurement plan.......................................................................................................................10
8. Gantt chart.................................................................................................................................12
9. Critical path...............................................................................................................................13
10. Critical chain............................................................................................................................14
11. Cost baseline............................................................................................................................15
12. S-curve.....................................................................................................................................16
Bibliography..................................................................................................................................17

2
PROJECT MANAGEMENT
1. Scope statement
The project scope is mainly categorized into in-scope as well as out-scope.
The project in-scope is as follows:
 The system must create the baseline of the project clearly
 The forecasting of cash value as well as earned value must be done with the help of
the system
 Both the facility of importing as well as exporting data must be present within the
system.
 The system server must be incorporated within the network of the existing system
The project out-scope are as follows:
 The system is not capable of analyzing the reasons of cash flow estimation
 The data type is not determined by the system
2. Estimates
The estimates include:
Analogous estimate: It is found that analogous estimate is one of the acts that mainly
utilize former projects for estimating both budget as well as time that is needed for completing
the project. It is estimated by the project manager that the time that is require for executing the
project successfully will be around 157 days whereas the budget that is needed is around $
72,920 as per ROM.

3
PROJECT MANAGEMENT
Parametric estimate: Parametric estimation is generally defined as one of the task in
which past projects are generally analyzed in order to get proper information which can be
utilized for implementing the present project successfully. The project manager is the person
who is responsible of undertaking feasibility study for the project and for this the project
managers requires to know about the budget as well as time that is needed for completing the
project. They generally uses information as well as past data and it is found that cost of the
resources in context to hour is around $30 and time is around 3 days. Thus, the project manager
assumes that he budget that is needed is around (30*8*4=4960.00)
Bottom up estimate: It is identified that bottom up estimate is one of the procedures that
mainly assist in allowing the ability to achieve appropriate redefined estimate for a particular
specific work component. The cost that is needed in order to complete all the project activities is
around $ 72,920. It is found that the other additional project cost that can be required is around
$20,000.00 and thus it is assumed that the entire cost of the project is around 92,920. The table
below highlights the cost that is required for completing a specific activity of a project.
Task Name Cost
Development of project costing system $72,920.00
Project initiation phase $8,920.00
Development of business case $1,120.00
Undertaking feasibility $720.00
Project charter establishment $1,120.00
Appointment of project team members $2,600.00
Gathering of requirements $1,120.00

4
PROJECT MANAGEMENT
Specification of technical requirements $2,240.00
Initiation phase completion $0.00
Project planning phase $17,240.00
Creation of project plan $3,640.00
Creation of resource plan $1,200.00
Creation of financial plan $1,440.00
Creation of quality plan $2,080.00
Creation of risk plan $1,680.00
Creation of acceptance plan $2,400.00
Creation of communication plan $2,640.00
Developing procurement plan $2,160.00
Planning phase completion $0.00
Project execution phase $39,800.00
Installation of server $7,200.00
Set up of client server $10,920.00
Development of unit test $8,400.00
User acceptance $7,280.00
Configuration of PC $6,000.00
Execution phase completion $0.00
Project closure phase $6,960.00
Training of staff $5,760.00
Go live support $720.00

5
PROJECT MANAGEMENT
Project review $480.00
Completion of project closure $0.00
3. Stakeholder management plan
The key stakeholders who are involved with the project are listed below:
 Project manager
 Project sponsor
 Supervisor
 Sub-contractor
 Contractor
 Web analyst
 Server administrator
Stakeholder Interest Influence Goal of the
stakeholder
Contribution Best way to
manage
Project
manager
1 1 The main goal
of the project
manager is to
complete the
entire project
successfully
within the
The project
manager is
person who
mainly
contributes for
leading the
entire project
The best
way for
managing
the project
is by
arranging
meeting and

6
PROJECT MANAGEMENT
assumed
budget as well
as time.
is quite
responsible
manner so that
the project
does not face
any
challenges.
by
monitoring
the schedule
of the
project
properly in
a regular
basis.
Server
administrator
1 2 The server
administrator
mianly
involves in
setting up the
server properly
within the
project so that
the
organization
does not face
any technical
challenges.
They mainly
takes the
responsibility
of setting up
the server
accurately
within the
organization
They
generally
test the
system
before
installing
them in
order to
ensure that
the system
is proper for
meeting the
needs as
well as
requirement

7
PROJECT MANAGEMENT
s of the
project.
Supervisor 2 2 The
supervisor is
mainly
responsible of
supervising the
project
properly so
that the project
will be
executed
properly
within the
estimated
budget as well
as time.
The various
activities of
the project are
generally
supervised
with the
supervisor in
order to
ensure that the
project is
progressing
properly.
Weekly
meetings
must be
undertaken
in order to
supervise
the project
activities
properly.

8
PROJECT MANAGEMENT
4. Work breakdown structure
Figure 1: WBS
(Source: Created by Author)
5. Communication plan
Type Purpose of
communication
Audiences Medium Frequency Responsible
Weekly
meetings
To discuss
about the
requirements of
the project so
that the system
can be
developed
Project
manager
Email,
conferencing,
meetings
Weekly Network
analyst

9
PROJECT MANAGEMENT
properly
Progress
status report
To discuss
about the status
of the project
and for making
sure that the
project is
progressing as
per the
estimated budget
and time.
Project
manager
Email,
conferencing,
meetings
Weekly Team leader
Monthly
meetings
Monthly
meetings are
generally
undertake in
order to discuss
about the budget
that is utilized
for completing
the activities of
the project
Project
manager
Email,
conferencing,
meetings
Monthly Financial
manager
6. Risk analysis
Risk Cause Effect Risk level Risk mitigation
strategy

10
PROJECT MANAGEMENT
Inaccurate
estimation of
project budget
1) Improper
knowledge
about the
needs as well
as
requirements
of the project
2) Due to
improper
analysis of
the current
market
It is identified
that inaccurate
estimation of
budget creates
number of issues
as well as
challenges. It also
creates financial
pressure on the
organization.
Medium Proper market
analysis is one of
the prior need
before estimation
of project
Poor quality of
materials
1) In order to
save budget of the
project
2) Due to lower
project budget
It occur number
of technical issues
within the system
due to which the
system will not be
able to work
properly.
High Proper quality of
materials must be
utilized for
developing the
system so that the
system will be
developed
successfully.
Inappropriate set
up of the server.
1) Due to
inappropriate
server set up,
it is
The server of the
system is not set
up properly due to
absence of
High It is quite
important to hire
experienced
stakeholders so

11
PROJECT MANAGEMENT
identified
that number
of technical
issues are
faced by the
people
experienced
stakeholders.
that the project
will not face any
technical issues
associated with
the project.
7. Procurement plan
Type of
contract
Procurement
risk
Procurement
risk
management
Procurement
constraints
Procurement
documentation
Performance
metrics
Firm
fixed
price
Conflict with
the contract
that is in use
presently
The new
contract was
developed
before
focussing
properly on the
contract that is
used before.
Resources Contract
guidelines
Acceptable
Firm
fixed
price
Inaccurate
server set up
Experienced
network
analyst must be
hired so that
the firm do not
face any
Resources Guideline of
manual set up
server.
Acceptable

12
PROJECT MANAGEMENT
technical
related
challenges.
Firm
fixed
price
Unrealistic
schedule
Proper
experienced
project
manager must
be hired in
order to
develop
prepare the
schedule of the
project
effectively.
Scope Statement of
work
Acceptable

13
PROJECT MANAGEMENT
8. Gantt chart
Figure 2: Gantt chart
(Source: Created by Author)

14
PROJECT MANAGEMENT
9. Critical path
Figure 3: Critical path
(Source: Created by Author)