Project Plan: Implementation of Project Management System - MAN6925

Verified

Added on  2022/10/17

|20
|2660
|469
Project
AI Summary
This project details the implementation of a project management system (PMS), encompassing scope definition, stakeholder management, communication, procurement, and costing modules. The system, acquired from a third party, involves data import via comma-delimited files or XML, necessitating data preparation and parsing. The project includes purchasing a server and configuring 20 client PCs with Windows 10, adding them to an existing network. Key activities include requirements gathering, server installation, software setup, PC configuration, testing, data import, user acceptance testing, training, go-live support, and a project review. The plan addresses limitations, acceptance criteria, cost estimation techniques (analogous, parametric, bottom-up), stakeholder analysis and engagement, a work breakdown structure (WBS), project scheduling with a critical path and Gantt chart, a communication management plan, a cost management plan, a risk management plan, and a procurement plan, including hardware and software requirements. The project also covers resource allocation and ethical considerations.
tabler-icon-diamond-filled.svg

Contribute Materials

Your contribution can guide someone’s learning journey. Share your documents today.
Document Page
Assignment Cover Sheet
Student Details
Student
Number
Family Name Given Name
Unit Details
Unit Code MAN6925 Unit Title PROJECT MANAGEMENT
Name of Lecturer STEVE BYERS Due Date 2/05/2019
Topic of Assignment COMMUNICATION
MANAGEMENT
Group or Tutorial (if applicable)
Course MANAGEMENT INFORMATION SYSTEMS Campus JOOND
ALUPI certify that the attached assignment is my own work and that any material drawn from other sources has been
acknowledged. This work has not previously been submitted for assessment in any other unit or course.
Copyright in assignments remains my property. I grant permission to the University to make copies of
assignments for assessment, review and/or record keeping purposes. I note that the University reserves the
right to check my assignment for plagiarism. Should the reproduction of all or part of an assignment be required
by the University for any purpose other than those mentioned above, appropriate authorisation will be sought
from me on the relevant form.
Manual Submission
If handing in an assignment in a paper or other physical form, sign here to indicate that you have read this form,
filled it in completely and that you certify as above.
Signature Date O
f
f
i
c
e
U
s
e
Electronic Submission
OR, if submitting this paper electronically as per instructions for the unit, place an X in the box below to indicate that
you have read this form and filled it in completely and that you certify as above. Please include this page with your
submission. Any responses to this submission will be sent to your ECU email address.
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
2IMPLEMENT A PROJECT MANAGEMENT SYSTEM
Agreement select check box Date
For procedures and penalties on late assignments please refer to the University Ad m issi on, En ro lm ent and Academic
Progress
Rules - rule 24, and the ECU Course and Unit Delivery and Assessment Policy
Document Page
3IMPLEMENT A PROJECT MANAGEMENT SYSTEM
Table of Contents
2.7 Limitations of the project.................................................................................................4
2.8 Acceptance criteria of the project....................................................................................4
3. Estimates................................................................................................................................4
4. Stakeholder management plan...............................................................................................5
4.1 Stakeholder analysis.........................................................................................................5
4.2 Stakeholder engagement..................................................................................................5
5. Project Work Breakdown Structure (WBS)...........................................................................7
6. Project scheduling and network: Critical Path.......................................................................8
6.1 Gantt chart........................................................................................................................9
7. Communication Management plan......................................................................................11
7.1 Communication and meeting guidelines........................................................................11
7.2 Ethical and professional codes.......................................................................................11
8. Project costing- Cost Management plan..............................................................................12
9. Risk management plan.........................................................................................................13
10. Procurement plan...............................................................................................................16
10.1 Procurement requirements...........................................................................................16
11. Project resourcing...............................................................................................................18
12. References..........................................................................................................................19
Document Page
4IMPLEMENT A PROJECT MANAGEMENT SYSTEM
2.7 Limitations of the project
The needs and expectations of the clients of the project management system keep on
changing every moment. Also there will be third party who will be involved in the
proceedings of the new project management system (PMS) thus; there are issues in terms of
maintaining the security of the data which will be accessed from the PMS.
2.8 Acceptance criteria of the project
The project must be completed within the estimated time frame and budget. The
documentation file must be shared among each of the stakeholders of this project so that the
quality of the end product is maintained and the purpose of the project is met (Binder, 2016).
Review of each phase of the software development must be shared with the developers who
in this project.
3. Estimates
Estimation of the cost is very much required in order to complete this project within a
scheduled timeframe (Badiru & Osisanya, 2016). There are different cost estimation
techniques which can be very much beneficial in this project which is described below.
Analogues testing: The similar previous projects are considered in this cost
estimation techniques, thus the development of the older PMS by other business entities can
be considered in order to make a cost management plan in this project.
Parametric estimation technique: The desire of the investors of this project is
considered in the calculation of the total cost of this project (Badewi, 2016). There are
different categories of variables associated with this project in terms of the dependent
variable and the independent variables, each of these variables have to be considered during
the management of the cost associated with this project.
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
5IMPLEMENT A PROJECT MANAGEMENT SYSTEM
Bottom up estimation technique: Accuracy of this cost estimation technique is very
much on the higher side (Meredith, Mantel & Shafer, 2017). Each activities of this project
must be broken into smaller fragments so that the cost associated with each of the cost
estimation techniques.
4. Stakeholder management plan
There are different categories of stakeholders involved in this project which can be
categorized into internal and external stakeholders.
4.1 Stakeholder analysis
Name of stakeholder Type Level of interest Level of influence Level of contribution
Investors of the
project
Internal High Medium Medium
Sub-contractors External High High High
Supplier Groups External Medium High Medium
Consumers of PMS External High Low Low
Steering committee Internal High Medium Medium
Table 1: Stakeholder analysis
(Source: Created by author)
4.2 Stakeholder engagement
Name of stakeholder Role in the project Contract details Information to be
shared
Medium
Investors of the
project
Funds the project Contact
information of
the stakeholder
Status of each phase of
the project. Detailed
documentation of the
role of each of the other
resources of this project
(Marchewka, 2016).
Emails.
Subcontractor Managing each of
the activities
associated with this
project (Fewings &
Henjewele, 2019).
Contact
information of
the stakeholder
Funds required in each
phase of the project.
Getting the feed from
each of the workers
involved in this project
(Kerzner, 2018).
Emails.
Supplier groups Supply of the
software and
hardware in terms
Contact
information of
the stakeholder
The cost and working
methodology must be
shared among each of
SharePoi
nt
Document Page
6IMPLEMENT A PROJECT MANAGEMENT SYSTEM
of the windows
based computer
systems (Ogunde
et al., 2017).
Setting up the
server is the other
role of the supplier
group of this
project.
the stakeholders by the
supplier group
(Kerzner, 2017).).
Consumer of the
PMS
They are supposed
to provide
feedback based
after the system is
completely ready
(leming &
Koppelman, 2016).
Contact
information of
the stakeholder
Project deliverables and
status of the project in
each phase are the
information which must
be shared with the
consumers of this PMS.
Email
Steering committee Dealing with any
sort of conflicts are
the prime intention
of this stakeholder
(Harrison & Lock,
2017).
Contact
information of
the stakeholder
Data of final release of
the product, project
status are the two
essential information
which has to be shared
with this stakeholder
(Ingason, 2015).
Email
Table 2: Engagement of the stakeholders
(Source: Created by author)
Document Page
7IMPLEMENT A PROJECT MANAGEMENT SYSTEM
5. Project Work Breakdown Structure (WBS)
Figure 1: WBS of the project
(Source: Created by the author)
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
8IMPLEMENT A PROJECT MANAGEMENT SYSTEM
6. Project scheduling and network: Critical Path
ID Task
Mode
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
Business Analyst
Project Manager
Finance Expert ,Project Manager,Business Analyst
Project Manager
Project Manager
31-10
Business Analyst
Project Manager
Project Manager,Finance Expert
Project Manager
Project Manager
Project Manager
02-12
Finance Expert ,Project Manager
System Designer
System Developer
System Developer
System Developer
System Developer
12-02
System Tester
System Tester
Project Manager
Implementation Resource
23-03
System Tester
Project Manager
Trainer
Technical Writer
Technical Writer
09-04
30 04 08 12 16 20 24 28 01 05 09 13 17 21 25 29 03 07 11 15 19 23 27 31 04 08 12 16 20 24 28 01 05 09 13 17 21 25 29 04 08 12 16 20 24
22 Sep '19 06 Oct '19 20 Oct '19 03 Nov '19 17 Nov '19 01 Dec '19 15 Dec '19 29 Dec '19 12 Jan '20 26 Jan '20 09 Feb '20 23 Feb '20 08 Mar '20 22 Mar '20
Figure 2: Critical path of the project
(Source: Created by the author)
Document Page
9IMPLEMENT A PROJECT MANAGEMENT SYSTEM
6.1 Gantt chart
ID Task
Mode
Task Name Duration Start Finish PredecessorsResource Names Cost
0 Creation of a project management
system
167 days Tue 10/1/19 Wed 5/20/20 $98,080.00
1 Sprint 1 167 days Tue 10/1/19 Wed 5/20/20 $98,080.00
2 Business Case Analysis of project
management system
10 days Tue 10/1/19 Mon 10/14/19 Business
Analyst
$8,000.00
3 Meeting with the investors of
this project
3 days Tue 10/15/19 Thu 10/17/19 2 Project
Manager
$1,800.00
4 Examine the feasibility of the
project management system
5 days Fri 10/18/19 Thu 10/24/19 3 Finance Expert
,Project
Manager,Business
$9,400.00
5 Briefing of the proposed project
management system
4 days Fri 10/25/19 Wed 10/30/19 4 Project
Manager
$2,400.00
6 Submitting the proposal to the
sponsor
1 day Thu 10/31/19 Thu 10/31/19 5 Project
Manager
$600.00
7 Milestone 1: System Brief 0 days Thu 10/31/19 Thu 10/31/19 6 $0.00
8 Sprint 2 36 days Thu 10/31/19 Thu 12/19/19 $17,920.00
9 Data gathering about the
project management system
8 days Thu 10/31/19 Mon 11/11/19 5 Business
Analyst
$6,400.00
10 Identification of the scope of
the project management
system
4 days Tue 11/12/19 Fri 11/15/19 9 Project
Manager
$2,400.00
11 Identification of the different
categories of cost
4 days Fri 11/15/19 Tue 11/26/19 10 Project
Manager,Finance
Expert
$1,920.00
12 Identification of resources and
risks of this project
4 days Tue 12/10/19 Fri 12/13/19 11 Project
Manager
$2,400.00
13 Setting the quality standard
for the new system
4 days Mon 11/18/19 Thu 11/21/19 10 Project
Manager
$2,400.00
14 Procurement Planning 4 days Mon 12/16/19 Thu 12/19/19 12,13 Project Manager $2,400.00
15 Milestone 2: Project Plan 0 days Thu 12/19/19 Thu 12/19/19 14 $0.00
16 Sprint 3, 4 68 days Fri 12/20/19 Tue 3/24/20 $39,880.00
17 Procurement of server and
networking devices
5 days Fri 12/20/19 Thu 12/26/19 15 Finance Expert
,Project
Manager
$5,400.00
18 Designing of the HCI 10 days Fri 12/27/19 Thu 1/9/20 17 System
Designer
$4,800.00
19 Creation of the database 5 days Fri 1/10/20 Thu 1/16/20 18 System Developer $2,800.00
20 Networking options 5 days Fri 1/17/20 Thu 1/23/20 19 System Developer $2,800.00
21 Development of the
application using
programming language
40 days Fri 1/24/20 Thu 3/19/20 20 System
Developer
$22,400.00
22 White box and black box
testing
3 days Fri 3/20/20 Tue 3/24/20 21 System
Developer
$1,680.00
23 Milestone 3: Testing
procedures
0 days Tue 3/24/20 Tue 3/24/20 22 $0.00
24 Sprint 5 28 days Wed 3/25/20 Fri 5/1/20 $11,800.00
25 Testing of the newly created
system
4 days Wed 3/25/20 Mon 3/30/20 23 System Tester $1,600.00
26 Addressing the issues
detected during the testing
procedure
6 days Tue 3/31/20 Tue 4/7/20 25 System Tester $2,400.00
27 Review the documentation 3 days Wed 4/8/20 Fri 4/10/20 26 Project Manager $1,800.00
28 Implementation of the new
system
15 days Mon 4/13/20 Fri 5/1/20 27 Implementation
Resource
$6,000.00
29 Milestone 4: Understanding
the usability
0 days Fri 5/1/20 Fri 5/1/20 28 $0.00
30 Sprint 6 13 days Mon 5/4/20 Wed 5/20/20 $6,280.00
31 White box Testing by System
Users
3 days Mon 5/4/20 Wed 5/6/20 28 System Tester $1,200.00
32 Sign-offs on deliverables 3 days Thu 5/7/20 Mon 5/11/20 31 Project Manager $1,800.00
33 Orientation training 5 days Thu 5/7/20 Wed 5/13/20 31 Trainer $1,600.00
34 System Documentation 4 days Tue 5/12/20 Fri 5/15/20 32 Technical Writer $960.00
35 Closure development 3 days Mon 5/18/20 Wed 5/20/20 34 Technical Writer $720.00
36 Milestone 5: Closure Report 0 days Wed 5/20/20 Wed 5/20/20 35 $0.00
Business Analyst
Project Manager
Finance Expert ,Project Manager,Business Analyst
Project Manager
Project Manager
10/31
Business Analyst
Project Manager
Project Manager,Finance Expert
Project Manager
Project Manager
Project Manager
12/19
Finance Expert ,Project Manager
System Designer
System Developer
System Developer
System Developer
System Developer
3/ 24
System Tester
System Tester
Project Manager
Implementation Resource
5/ 1
System Tester
Project Manager
Trainer
Technical Writer
Technical Writer
5/ 20
24 12 30 17 5 23 10 28 15 4 22 9
Aug 25, '19 Oct 6, '19 Nov 17, '19 Dec 29, '19 Feb 9, '20 Mar 22, '20
Figure 3: Scheduling of the project
(Created by author using MS Project)
Document Page
10IMPLEMENT A PROJECT MANAGEMENT SYSTEM
6.2 Critical Chain
Figure 4: Critical Chain Activities
(Created by author using MS Project)
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
11IMPLEMENT A PROJECT MANAGEMENT SYSTEM
7. Communication Management plan
7.1 Communication and meeting guidelines
Scheduling of each of the stakeholders involved in this project is very much desired in
order to complete the project according to the expectation of the stakeholders. Professional
communication procedure must be followed in each phase of this project (Schwalbe, 2015).
There are different forms of communication which can be adopted in this project in terms of
instant messages, Email, SharePoint and face to face communication (Kerzner, 2019).
7.2 Ethical and professional codes
Honesty and complacency of each of the stakeholders involved in this project must be
kept so that the reliability of the PMS in maintained (Walker, 2015). Primacy of public
interest and professionalism is expected from each of the stakeholders involved in this
project.
Document Page
12IMPLEMENT A PROJECT MANAGEMENT SYSTEM
8. Project costing- Cost Management plan
ID Task
Mode
WBS Task Name Cost
0 0 Creation of a project management
system
$98,080.00
1 1 Sprint 1 $98,080.00
2 1.1 Business Case Analysis of project
management system
$8,000.00
3 1.2 Meeting with the investors of
this project
$1,800.00
4 1.3 Examine the feasibility of the
project management system
$9,400.00
5 1.4 Briefing of the proposed project
management system
$2,400.00
6 1.5 Submitting the proposal to the
sponsor
$600.00
7 1.6 Milestone 1: System Brief $0.00
8 1.7 Sprint 2 $17,920.00
9 1.7.1 Data gathering about the
project management system
$6,400.00
10 1.7.2 Identification of the scope of
the project management
system
$2,400.00
11 1.7.3 Identification of the different
categories of cost
$1,920.00
12 1.7.4 Identification of resources and
risks of this project
$2,400.00
13 1.7.5 Setting the quality standard
for the new system
$2,400.00
14 1.7.6 Procurement Planning $2,400.00
15 1.7.7 Milestone 2: Project Plan $0.00
16 1.8 Sprint 3, 4 $39,880.00
17 1.8.1 Procurement of server and
networking devices
$5,400.00
18 1.8.2 Designing of the HCI $4,800.00
19 1.8.3 Creation of the database $2,800.00
20 1.8.4 Networking options $2,800.00
21 1.8.5 Development of the
application using
programming language
$22,400.00
22 1.8.6 White box and black box
testing
$1,680.00
23 1.8.7 Milestone 3: Testing
procedures
$0.00
24 1.9 Sprint 5 $11,800.00
25 1.9.1 Testing of the newly created
system
$1,600.00
26 1.9.2 Addressing the issues
detected during the testing
procedure
$2,400.00
27 1.9.3 Review the documentation $1,800.00
28 1.9.4 Implementation of the new
system
$6,000.00
29 1.9.5 Milestone 4: Understanding
the usability
$0.00
30 1.10 Sprint 6 $6,280.00
31 1.10.1 White box Testing by System
Users
$1,200.00
32 1.10.2 Sign-offs on deliverables $1,800.00
33 1.10.3 Orientation training $1,600.00
34 1.10.4 System Documentation $960.00
35 1.10.5 Closure development $720.00
36 1.10.6 Milestone 5: Closure Report $0.00
Business Analyst
Project Manager
Finance Expert ,Project Manager,Business Analyst
Project Manager
Project Manager
10/31
Business Analyst
Project Manager
Project Manager,Finance Expert
Project Manager
Project Manager
Project Manager
12/19
Finance Expert ,Project Manager
System Designer
System Developer
System Developer
System Developer
System Developer
3/24
System Tester
System Tester
Project Manager
Implementation Resource
5/1
System Tester
Project Manager
Trainer
Technical Writer
Technical Writer
5/20
5/12 7/14 9/15 11/17 1/19 3/22 5/24 7/26 9/27 11/29 1/31 4/4
January 11 May 21 October 1 February 11 June 21 November 1 March 11
Figure 4: Project Costing
(Created by the author)
Document Page
13IMPLEMENT A PROJECT MANAGEMENT SYSTEM
9. Risk management plan
ID Name of the risk Description Probability Impact Score Treatment strategy
1 Technical risks Malfunctioning
of the server
2 3 6 Involvement of the third
party must be controlled
and monitored in the first
place.
2 Communication
risks
Communicatio
n gap between
each of the
stakeholders
4 2 8 Risks of the PMS must be
addressed during the
planning phase.
3 Project
management risk
Deadlines
issues in each
phase of the
project
3 3 9 Project management plan
is very much useful to
address the deadline
issues of the project.
4 Operational risk Mis utilization
of resources
4 4 16 Resource management
plan can be very much
useful to manage each of
the resources involved in
5 Change in scope Changes in the
functional and
non-functional
requirements.
2 3 6 Documentation must be
shared among each of the
stakeholders and it must
be changed in the first
place (Khameneh, Taheri
& Ershadi, 2016).
6 Security Attacks Data security 2 2 4 The network which
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
14IMPLEMENT A PROJECT MANAGEMENT SYSTEM
issues can have
a huge impact
on the
productivity of
the PMS.
where this PMS is going
to be installed has to
secured from data
security threats like
phishing emails.
7 Ethical risks Principles of
software
engineering
procedures
must be
followed in
each phase of
the project.
2 4 8 The ethical issues
associated in both the
design phase and the
development phase can
be mitigated using ethical
frameworks like the duty
based approach.
8 Quality Risks Quality risks
lies in each
phase of the
project starting
from the
documentation
phase to the
documentation
phase.
2 4 8 This issue can be
addressed if a separate
team is there as the white
box testers of the PMS.
9 Resource risks Availability of
each of the
resources
2 3 6 Incorporation of a
resource management
plan can be very much
Document Page
15IMPLEMENT A PROJECT MANAGEMENT SYSTEM
required in this
project is very
much in order
to complete this
project within
the scheduled
time. However,
unavailability
can cause huge
issues in this
project.
useful to deal with each
of the resources involved
in this project such as the
designer, developers, and
testers.
10 Legal risks The software
engineering
norms is also
considered as a
norms in this
project
4 3 12 This risk can be
successfully avoided if a
project manager is
recruited on the basis of
both qualification as well
as experience.
Table 3: Risk management plan
(Source: Created by author)
10. Procurement plan
10.1 Procurement requirements
Requirements Quantity Reason Requirements Discharge from the project
Servers 1 PMS should
be uploaded
System
implementation
Never
Document Page
16IMPLEMENT A PROJECT MANAGEMENT SYSTEM
in a live
server
procedure must
be practised
(Laudon, &
Laudon, 2016).
Computer
systems
25 PMS shall be
installed in
each of those
computer
systems.
System
implementation
procedure must
be practised.
Not applicable.
SQL
database
1 MySQL
database is
required in
this project.
Development of
the source code.
Not applicable.
Design and
development
tool
2 Development
of the PMS
These tools are
required in the
execution phase
of this project.
After the new PMS is
uploaded in the live server.
PM tools 2 To deal with
the PM
issues.
Tracking each of
the activities of
this project
After the new PMS is
uploaded in the live server.
Testing tools 1 The quality
of service
provided by
PMS is very
much
The
functionality of
each of the
sections of the
PMS can be
The testing phase of this
project shall be marking the
necessity of the testing
tools.
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
17IMPLEMENT A PROJECT MANAGEMENT SYSTEM
depended on
the
deployment
of the testing
tools.
evaluated using
the testing tools.
The evaluation
of each of the
stakeholders
involved in this
project is the
other reason
behind the need
of the software
testing tools
such as the Test
Studio and
Webload.
Table 4: Procurement requirements
(Source: Created by author)
Document Page
18IMPLEMENT A PROJECT MANAGEMENT SYSTEM
11. Project resourcing
ID Resource Name Type Std. Rate
1 Business Analyst Work $100.00/hr
2 Project Manager Work $75.00/hr
3 Finance Expert Work $60.00/hr
4 System Designer Work $60.00/hr
5 System Developer Work $70.00/hr
6 System Tester Work $50.00/hr
7 Implementation
Resource
Work $50.00/hr
8 Trainer Work $40.00/hr
9 Technical Writer Work $30.00/hr
Figure 5: Rate of each of the resources
(Created by the author)
Name Remaining Work
Business Analyst 184 hrs
Project Manager 320 hrs
Finance Expert 112 hrs
System Designer 80 hrs
System
Developer
424 hrs
System Tester 104 hrs
Implementation
Resource
120 hrs
Trainer 40 hrs
Technical Writer 56 hrs
Figure 6: Hours of work of each of the resources
(Created by the author)
Document Page
19IMPLEMENT A PROJECT MANAGEMENT SYSTEM
12. References
Badewi, A. (2016). The impact of project management (PM) and benefits management (BM)
practices on project success: Towards developing a project benefits governance
framework. International Journal of Project Management, 34(4), 761-778.
Badiru, A. B., & Osisanya, S. O. (2016). Project management for the oil and gas industry: a
world system approach. CRC Press.
Binder, J. (2016). Global project management: communication, collaboration and
management across borders. Routledge.
Fewings, P., & Henjewele, C. (2019). Construction project management: an integrated
approach. Routledge.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management.
Project Management Institute.
Harrison, F., & Lock, D. (2017). Advanced project management: a structured approach.
Routledge.
Ingason, H. T. (2015). Best project management practices in the implementation of an ISO
9001 quality management system. Procedia-Social and Behavioral Sciences, 194,
192-200.
Kerzner, H. (2017). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Kerzner, H. (2018). Project management best practices: Achieving global excellence. John
Wiley & Sons.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
20IMPLEMENT A PROJECT MANAGEMENT SYSTEM
Kerzner, H. (2019). Using the project management maturity model: strategic planning for
project management. Wiley.
Khameneh, A. H., Taheri, A., & Ershadi, M. (2016). Offering a framework for evaluating the
performance of project risk management system. Procedia-Social and Behavioral
Sciences, 226, 82-90.
Laudon, K. C., & Laudon, J. P. (2016). Management information system. Pearson Education
India.
Marchewka, J. T. (2016). Information technology project management: Providing
measurable organizational value. John Wiley & Sons.
Meredith, J. R., Mantel Jr, S. J., & Shafer, S. M. (2017). Project management: a managerial
approach. John Wiley & Sons.
Ogunde, A., Olaolu, O., Afolabi, A. O., Owolabi, J., & Ojelabi, R. A. (2017). Challenges
confronting construction project management system for sustainable construction in
developing countries: Professionals perspectives (a case study of Nigeria). Journal of
Building Performance, 8(1), 1-11.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Walker, A. (2015). Project management in construction. John Wiley & Sons.
chevron_up_icon
1 out of 20
circle_padding
hide_on_mobile
zoom_out_icon
logo.png

Your All-in-One AI-Powered Toolkit for Academic Success.

Available 24*7 on WhatsApp / Email

[object Object]