Project Management | Assessment1

Project Management

Table of Contents
1. Case Study..............................................................................................................................3
2. Scope Statement.....................................................................................................................4
Project Owner, Project Sponsor and Project stakeholders.....................................................4
Project Goals and Objectives.................................................................................................4
Project Requirements.............................................................................................................4
Project Deliverables...............................................................................................................4
Project Milestones..................................................................................................................4
3. Estimates................................................................................................................................5
Analogous estimate................................................................................................................5
Parametric estimate................................................................................................................5
Bottom up estimate................................................................................................................6
4. Stakeholder Management Plan...............................................................................................7
5. Work Breakdown Structure....................................................................................................7
6. Communication Plan............................................................................................................10
7. Risk Analysis.......................................................................................................................10
8. Procurement Plan.................................................................................................................11
8. Gantt Chart...........................................................................................................................12
9. Critical Path..........................................................................................................................12
10. Critical Chain.....................................................................................................................13
11. Cost Baseline......................................................................................................................15
References................................................................................................................................17

1. Case Study
The project involves the implementation of a comprehensive project management system for
an organisation. With the implementation of the system, there would be greater clarity among
the project management team regarding the diverse aspects of project management such as
project scope definition, project feasibility, stakeholder management, project communication,
project procurement and project costing. The project management system would be
developed by a third party and so there is an urgent requirement to educate the organisational
staffs regarding how to efficiently utilise the system and obtain the desired benefits from the
system. The project management system would be simultaneously running on 20 computer
workstations and there would be a central server that would facilitate the client request
handling process. The system would make use of data that would be imported via comma
delimited files or XML.
The project would require the successful delivery of the following minimum high level work
activities:
1) Server installation
2) Requirements gathering
3) Installing the server software
4) Installing Windows 10 on all PCs
5) Testing of each workstation
6) Parsing and importing of raw data
7) User acceptance testing of the software
8) Providing training to the staffs
9) Providing real time technical support
10) Project Review

2. Scope Statement
Project Owner, Project Sponsor and Project stakeholders
The project owner and project sponsor is a commercial organisation that wants to implement
a project management system within their business that would provide them greater leverage
in their business. The main stakeholders in the project are project team leader, location
manager, system developers, system testers, system users, project sponsors/owners.
Project Goals and Objectives
To streamline and optimise the future project management activities undertaken by the
organisation through the adoption and utilisation of advanced software systems. This would
help in increasing the efficiency of future projects by eliminating the scope of human errors
during the project implementation process. This would help in radically increasing the
chances of project success. The implementation of the project management systems would
eventually help in providing greater long term business dividends to an organisation.
Project Requirements
The project requirements include the following:
 20 computer workstations that have Windows 10 installed in them.
 1 server to facilitate request handling from client PCs.
 Highly qualified and experienced software engineers who have the technical
knowledge and competency in dealing with software projects.
 Software Testers.
Project Deliverables
The project management system upon successful completion would be integrated within the
existing organisational system and this would help the organisation is optimising their future
project management functionalities resulting in successful future projects.
Project Milestones
1) Developing and designing the Project management systems
2) Comprehensive Debugging and Testing of the system
3) Training the organisational staffs in the effective handling and utilisation of the system.
4) Reviewing the system against the client specifications and requirements.

5) Integrating the system with the existing organisational IT architecture.
3. Estimates
The project sponsors have specified a time frame of six months for the successful project
implementation. Being an IT project, the project developers would take a time frame of five
months for successful completion and integration within the organisation and an additional
moth would be consumed in providing adequate and comprehensive training to the
organisational staffs in proper handling and usage of the Project management systems.
Analogous estimate
In the installation and implementation of the project management system, analogous
estimation time is implemented. In his process ROM ranges from minus 30 to plus 30.
Expenses Tasks Explanation Total Costs
Capital Implementation Of Project Mangement System 245,000.00$
Capital Purchasing Hardware And Software Equipments 75,600.00$
Capital Installation Of Server Application And Import Data 34,200.00$
Capital Contingency 75,000.00$
Capital Training 60,000.00$
Capital Contingency 75,000.00$
TOTAL 564,800.00$
Parametric estimate
The undertaken project i.e. implementation of the project management system has an
extensive work breakdown structure and extended life, therefore project difficulties and
lengths were computed as an independent variables. In this process of estimation ROM is
between minus 20 to plus 20.

DEPENDENT VARIABLES COST PER TOTAL 294900
COMPUTER DEVICES 30 600.00$ 18,000.00$
SOFTWARE 10 160.00$ 1,600.00$
HARDWARE 40 1,000.00$ 40,000.00$
SERVER 1 220,000.00$ 220,000.00$
ELECTRICAL CONTRACTORS 10 110.00$ 1,100.00$
CONTRACT SUPERVISORS 40 80.00$ 3,200.00$
EQUIPMENTS 50 150.00$ 7,500.00$
SOFTWARE ENGINEERS 5 150.00$ 750.00$
HARDWARE ENGINEERS 15 110.00$ 1,650.00$
DATA ANALYSTS 5 220.00$ 1,100.00$
INDEPENDENT VARIABLES 224,000.00$
TEAM MEMBERS NO 0,15% 16,000.00$
CONTRACT LABOUR YES 0,5% -$
HIRING EQUIPMENT NO 0,5% 15,000.00$
PROJECT LENGTHS average 0%,33%,66% 95,000.00$
DIFFICULTIES average 0%,33%,66% 95,000.00$
EMPLOYEES HIRE CONTRACTS good 0%,5%,8%,15% 3,000.00$
TOTAL 518,900.00$
Successfully implement the project management system
Bottom up estimate
ROM has undertaken for this budget system is between minus 10 to plus 10.
WBS equipments total SEP OCT NOV DEC JAN FEB MAR APR MAY JUN JUL AUG SEP
1.0 To implement a project management system 17,460.00$
1.1 project mangement system requirements and gathering process 2,000.00$ 2,500.00$
1.1.1 Evaluation of the project mangement system 3,000.00$ 3,300.00$
1.1.2 Human resource evaluation and analysis 3,100.00$ 3,410.00$
1.1.3 Conduct the research study 2,500.00$ 2,750.00$
1.1.4 Evaluation of appropriate solution 2,500.00$ 2,750.00$
1.1.5 project submit 2,500.00$ 2,750.00$
1.2 Server and server software installation 25,200.00$
1.2.1 planning sever installation process 3,000.00$ 3,300.00$
1.2.2 Selection of the server for business 3,000.00$ 3,300.00$
1.2.3 Recruitment of hardware engineer 4,800.00$ 5,280.00$
1.2.4 Established the connection of servers 4,800.00$ 5,280.00$
1.2.5 Installation of server operating system 4,800.00$ 5,280.00$
1.2.6 Test the connectivity and server operating system performance 4,800.00$ 5,280.00$
1.3 Establishment of customer PC setup with Windows 10 94,000.00$
1.3.1Purcase PCs for system 12,500.00$ 13,750.00$
1.3.2 Evaluation of PC performance 15,400.00$ 16,940.00$
1.3.3 Install the Windows 10 operating system in PCs 1,100.00$ 1,210.00$
1.3.4 Analysis of OS and PCs performance 45,000.00$ 49,500.00$
1.3.5 Prepared a report for manager 20,000.00$ 22,000.00$
1.4 Client Project mangement software in each PCs 104,000.00$
1.4.1 Configure the solution in computers 4,000.00$ 4,400.00$
1.4.2 Installed client software in each PCs 50,000.00$ 55,000.00$
1.4.3 Configuration of the software into PCs 50,000.00$ 55,000.00$
1.5 Test the PCs 43,000.00$ 6,600.00$
1.5.1 Evaluation of testing approach 6,000.00$ 15,400.00$
1.5.2 Implement unit testing performance in each PCs 14,000.00$ 25,300.00$
1.5.3 Update the record of testing process 23,000.00$ 2,200.00$
1.6 Parse and data import 35,000.00$ 27,500.00$
1.6.1 Analysis of the data and information 2,000.00$ 2,200.00$
1.6.2 Recruitment of data engineers 25,000.00$ 6,600.00$
1.6.3 Data integration into the system 2,000.00$
1.6.4 Data import through XML 6,000.00$ 16,500.00$
1.7 User acceptance testing 22,500.00$ 2,750.00$
1.7.1 Selection of the user for user acceptance testing 15,000.00$ 2,750.00$
1.7.2 Conduct user acceptance testing 2,500.00$ 2,750.00$
1.7.3 Collect the feedback and information from user about system 2,500.00$
1.7.4 Update the all records obtained from users 2,500.00$ 6,600.00$
1.8 Training 78,000.00$ 66,000.00$
1.8.1 Prepared schedule for training program 6,000.00$ 6,600.00$
1.8.2 update the all record for training 60,000.00$ 6,600.00$
1.8.3 conduct training session program 6,000.00$ 2,750.00$
1.8.4 report submit to project management 6,000.00$ 3,520.00$
1.9 Go live support 2,500.00$ 3,520.00$
1.9.1 Go live of project management system 2,500.00$ 3,520.00$
1.10 project review 16,000.00$ 3,520.00$
1.10.1 conduct project monitoring and controlling process 3,200.00$ 3,520.00$
1.10.2 Record all report obtained from the system 3,200.00$
1.10.3 Analysis the data with project objective plan 3,200.00$
1.10.4 Submit the all record to manager 3,200.00$
1.10.5 project closure 3,200.00$
Management reserve(5%) 873.00$ -$ 1,386.00$ 5,170.00$ -$ 5,720.00$ -$ 2,365.00$ -$ 1,925.00$ 5,527.50$ 137.50$ 880.00$
costs baseline 17,460.00$ -$ 27,720.00$ 103,400.00$ -$ 114,400.00$ -$ 47,300.00$ -$ 38,500.00$ 110,550.00$ 2,750.00$ 17,600.00$
accumulative total 18,333.00$ 18,333.00$ 47,439.00$ 156,009.00$ 156,009.00$ 276,129.00$ 276,129.00$ 325,794.00$ 325,794.00$ 366,219.00$ 482,296.50$ 485,184.00$ 503,664.00$

4. Stakeholder Management Plan
The main stakeholders of the project are the organisational management, the staffs of the
organisation (the system users), the project manager, the system designers and the system
testers. There needs to be thorough and continuous communication and interaction between
all the project stakeholders for ensuring smooth project implementation without any hassles
(Freeman, 2010). The project stakeholders need to meet on a daily basis and all the progress
made in the project needs to be thoroughly discussed and explained. The project management
team needs to continuously update the project sponsors about the challenges encountered
during the project execution phase and what project milestones have been successfully
accomplished. This would really help in ensuring that the interest of all the project
stakeholders is satisfied at the time of project implementation (Carroll & Buchholtz, 2014).
5. Work Breakdown Structure
Project Aim The aim of undertaken project is to successfully implement the project
management system within the organization.
Level 1 Level 2 Level 3
To implement a
project
management
system
1.1 project
mangement
system
requirements and
gathering
process
1.1.1 Evaluation of the project mangement system
1.1.2 Human resource evaluation and analysis
1.1.3 Conduct the research study
1.1.4 Evaluation of appropriate solution
1.1.5 project submit

1.2 Server and
server software
installation
1.2.1 planning sever installation process
1.2.2 Selection of the server for business
1.2.3 Recruitment of hardware engineer
1.2.4 Established the connection of servers
1.2.5 Installation of server operating system
1.2.6 Test the connectivity and server operating
system performance
1.3
Establishment of
customer PC
setup with
Windows 10
1.3.1Purcase PCs for system
1.3.2 Evaluation of PC performance
1.3.3 Install the Windows 10 operating system in
PCs
1.3.4 Analysis of OS and PCs performance
1.3.5 Prepared a report for manager
1.4 Client
Project
mangement
software in each
PCs
1.4.1 Configure the solution in computers
1.4.2 Installed client software in each PCs
1.4.3 Configuration of the software into PCs
1.5 Test the PCs 1.5.1 Evaluation of testing approach
1.5.2 Implement unit testing performance in each
PCs
1.5.3 Update the record of testing process

1.6 Parse and
data import
1.6.1 Analysis of the data and information
1.6.2 Recruitment of data engineers
1.6.3 Data integration into the system
1.6.4 Data import through XML
1.7 User
acceptance
testing
1.7.1 Selection of the user for user acceptance
testing
1.7.2 Conduct user acceptance testing
1.7.3 Collect the feedback and information from
user about system
1.7.4 Update the all records obtained from users
1.8 Training 1.8.1 Prepared schedule for training program
1.8.2 update the all record for training
1.8.3 conduct training session program
1.8.4 report submit to project management
1.9 Go live
support
1.9.1 Go live of project management system
1.10 project
review
1.10.1 conduct project monitoring and controlling
process
1.10.2 Record all report obtained from the system
1.10.3 Analysis the data with project objective plan
1.10.4 Submit the all record to manager
1.10.5 project closure

6. Communication Plan
The communication plan is a crucial component of any project and this project is not an
exception. The project management team and the project sponsors need to utilise a wide
variety of communication channels such as emails, telephones and formal face-to-face
meetings to communicate and discuss about all the progress and development made in the
project (Papke-Shields, Beise & Quan, 2010). This would help in keeping all the project
stakeholders thoroughly abreast about all the technicalities associated with the project. The
project management team must ensure that there is a strong communication channel within
the organisation which would allow them to continuously communicate and coordinate their
activities by consulting with the project sponsors and this would eventually help them to
implement the project in a timely and successful manner within the stipulated budget (Zulch,
2014).
7. Risk Analysis
The risk analysis plays a vital role in ensuring an effective risk management and risk
mitigation process that would allow the project management team to tackle and mitigate any
risks before they arise in the project and compromise the project implementation (Vose,
2008). There are various risks that are associated with this existing project and these could be
categorised into three types based on their criticality – high risk, moderate risk and low risk.
The high risks associated with this project are systems failure, lack of proper planning and
strategising, lack of project resources. The moderate risks associated with this project are lack
of skilled manpower availability, lack of communication and coordination among the
members of the project management team. The low risks associated with this project are
conflict of interest among the project management team which might arise during the project
implementation (Cagliano, Grimaldi & Rafele, 2015).
Level
of
impac
Very High
systems
failure
High lack of
proper
planning
lack of
project
resource
s

t
Moderate
skilled
manpower
availabilit
y
Low
conflict of
interest
among the
project
manageme
nt team
lack of
communicatio
n
Very Low
Likehood Rare
Occasion
al
Somewhat
Frequent Frequent
Very
Frequen
t
Likelihood of occurrence
8. Procurement Plan
The project procurement planning would be undertaken through an e-bidding process where
the project vendors providing the lowest bid would be selected for working on the proposed
project. This would help the organisational management to minimise their cost expenses
while at the same time ensure greater long term value creation from the project implantation
(De Araújo, Alencar & de Miranda Mota, 2017).

8. Gantt Chart
9. Critical Path
Activity priority duration (Weeks) dependencies
Project management system implementation plan A 3 ….
Establishment of product deliverables B 2 A
Assign project team C 2 A
Analysis server and PCs performance D 5 B
development of WBS E 2 C
Creation of budget plan F 4 B
Selection of stakeholders G 1 D
Analysis of business process H 14 G,L
conducting risks analysis I 14 D
Purchasing hardware and software J 20 I
Data integration K 7 D
Testing system L 2 G
managing communication M 5 I,K
review the plan N 2 M
Product delivery O 10 H,L
Documentation planning P 7 O
Project closeout Q 3 P

Duration 24 44
Float 0 J 20
Critical path# 24 44
10 24 24 29 44 46
15 I 14 15 M 5 0 N 2
25 39 39 44 44 46
5 10 10 17
22 D 5 22 K 7
3 5 27 32 32 39
22 B 2 11 23 23 33 46 53 53 56
25 27 5 9 10 11 10 H 14 13 O 10 0 P 7 0 Q 3
10 F 4 8 G 1 21 33 33 46 46 53 53 56
0 3 15 19 18 19
22 A 3
0 25
3 5
12 C 2
15 17
11 13
8 L 2
19 21
5 7
12 E 2
17 19
Network Diagram - Critical Path Analysis
10. Critical Chain

11. Cost Baseline
COST BASE LINE
DATE ACIVITY
DURATION(d
ays)
STARTDA
TE
END
DATE
COST(AU
D$)
9.30.201
9 Requirements Gathering 19 9.30.19
10.24.201
9 5000
10.25.20
19 Server Installation 18 10.25.2019
11.19.201
9 25000
11.20.20
19 Installation of server software 8 11.20.2019
11.29.201
9 31500
12.2.201
9
Client project software installed in
each PC 18 12.2.2019
12.25.201
9 40005
12.26.20
19 Test of Each PC 27 12.26.2019 1.31.2019 51206

2.3.2019 Parse and import data 18 2.3.2019 2.26.2019 64008
2.27.201
9
Use acceptance testing of the
application 13 2.27.2019 3.16.2019 80010
3.17.201
9 Training 14 3.17.2019 4.3.2019 84011
4.6.2019 Go live support 2 4.6.2019 4.7.2019 85691
4.8.2019 Project Review 13 4.8.2019 4.24.2019 86548
Total 150 552978
9.30.2019
10.25.2019
11.20.2019
12.2.2019
12.26.2019
2.3.2019
2.27.2019
3.17.2019
4.6.2019
4.8.2019
0
10000
20000
30000
40000
50000
60000
70000
80000
90000
100000
Cost baseline-Scurve

References
Bourne, L., & Walker, D. H. (2008). Project relationship management and the Stakeholder
Circle™. International Journal of Managing Projects in Business, 1(1), 125-130.
Cagliano, A. C., Grimaldi, S., & Rafele, C. (2015). Choosing project risk management
techniques. A theoretical framework. Journal of Risk Research, 18(2), 232-248.
Carroll, A. B., & Buchholtz, A. K. (2014). Business and society: Ethics, sustainability, and
stakeholder management. Nelson Education.
De Araújo, M. C. B., Alencar, L. H., & de Miranda Mota, C. M. (2017). Project procurement
management: A structured literature review. International Journal of Project
Management, 35(3), 353-377.
Freeman, R. E. (2010). Strategic management: A stakeholder approach. Cambridge
university press.
Papke-Shields, K. E., Beise, C., & Quan, J. (2010). Do project managers practice what they
preach, and does it matter to project success?. International journal of project
management, 28(7), 650-662.
Vose, D. (2008). Risk analysis: a quantitative guide. John Wiley & Sons.
Zulch, B. G. (2014). Communication: The foundation of project management. Procedia
Technology, 16, 1000-1009.