What Is Project Management? The Ultimate Guide

Running head: PROJECT MANAGEMENT
Information and Communication Technology Project Management
Name of the Student:
Name of the University:

1PROJECT MANAGEMENT
Table of Contents
1. Project Charter....................................................................................................................3
1.1 Background..................................................................................................................3
1.2 Outline business case...................................................................................................3
1.3 Project objectives and scope........................................................................................4
1.3.1 Project objectives.................................................................................................4
1.3.2 Project scope........................................................................................................4
1.4 Project plan..................................................................................................................5
1.4a. Project approach........................................................................................................5
1.4b. Project work packages...............................................................................................6
1.4c. Resource requirements..............................................................................................9
1.4d. Project budget..........................................................................................................10
1.4e. Project tolerances....................................................................................................11
1.5 Acceptance criteria....................................................................................................11
1.6 Organization- roles and responsibilities....................................................................12
1.7 Project quality............................................................................................................14
1.8 Project controls..........................................................................................................15
1.9 Risk management......................................................................................................15
1.10 Security considerations..............................................................................................17
2. Gantt chart........................................................................................................................18
3. Risk Management Plan....................................................................................................19
a. Risk management strategy and analysis........................................................................19

2PROJECT MANAGEMENT
b. Risk management framework.......................................................................................20
c. Risk analysis and management.....................................................................................22
d. Categories of risks.........................................................................................................24
e. Risk log.........................................................................................................................25
4. Project Progress Reporting Strategy................................................................................27
References................................................................................................................................29

3PROJECT MANAGEMENT
1. Project Charter
1.1 Background
The purpose of this project is to develop ICT strategy for school for next five years.
The school works with young people, even it has lack of ICT infrastructure. The school has
also lack of credibility when it has archaic ICT infrastructure. The current situation of the
school is such that it is not making full use of information that it stores as well as supports
commuting applications to enhance their curriculum. In order to replace its current manual
system, the school decides to implement data communication network as well as hardware
infrastructure to enhance usage of the modern technology like IM, Web2 applications,
information system and others.
1.2 Outline business case
The proposed solution for the primary school is implementing data communication
network as well as hardware infrastructure to support school as business as well as
curriculum. The school is also required a website for attracting new pupils and extending
appeal to the international boarders. The benefits of data communication network is
providing platform to run the business support application and provide core functionality
needed to provide information to organizational staffs (Blaskovics 2016). ICT solution in the
school helps to improve engagement, improve knowledge retention and encourages in
collaboration among the staffs.

4PROJECT MANAGEMENT
1.3 Project objectives and scope
1.3.1 Project objectives
The objective of the primary school is providing state of ICT solutions with cost
effective data communication network infrastructure and meet with the timeline of the
hardware design for the school. This project plan will require to meet with following
objectives:
 Improved over the network capability of the primary school
 Improved over the hardware infrastructure for high speed chances in running
business
 Implement data communication network to improve business performance and
productivity
 Design for expectation of business growth
 Completion of the project in 4 months timeline with an estimated budget
1.3.2 Project scope
The scope of this project plan includes as well as excludes following items:
In-scope: The scope of this plan is setting up hardware infrastructure and data
communication network for the primary school. It also provides with storage solution for
easier data access back to the school. There is modernize of hardware and software solutions
to enhance usage of the modern technology like IM, Web2 applications, information system.
It ensures sufficient capability of system.
Out-of-scope: There is removal of obsolete IT equipment as well as software from the
business and training of the IT staffs to maintain new implemented network.

5PROJECT MANAGEMENT
Assumptions: It is assumed that the project timeline as well as budget are meet with
its planned time and cost, therefore there is no schedule in addition cost overruns. It is also
assumed that all IT equipment are of best quality and helped the school to meet with its
requirements (Ahmad, Arshad and Aris 2018).
Constraints: There is delay in the project due to initial hardware and software
upgrades. It causes schedule constraints. Due to delay in the initial configuration of data
communication network, there is an increase in project cost, causes budget constraint
(Lyngso 2017). Proper maintenance of the system is not done properly, therefore it causes
quality constraint.
Project dependencies: The budget is dependent on approval for budget from the
company owner and meet with the project timeline is dependent on meeting with business
needs.
1.4 Project plan
1.4a. Project approach
This project plan is based on PRINCE2 project approach where it is focused to control
the entire project plan from its starting to completion. The project work is planned before
kick off as well as each of the project stages are structured properly (Fustik and Macedonia
2018). Based on this project approach, the stages which are followed in product delivery are:
 Initiation phase
 Planning phase
 Installation phase
 Implement hardware and software infrastructure
 Testing phase

6PROJECT MANAGEMENT
 Finalize phase

7PROJECT MANAGEMENT
1.4b. Project work packages
Work Package
Responsible Team Target Completion
Date
Estimated
Resource in
Days Effort
Develop a project charter Project Manager Wed 11-03-20 16 hrs
Submission of the
project charter
Project Manager Tue 17-03-20 32 hrs
Charter review Project Sponsor Fri 20-03-20 24 hrs
Approval of the charter Project Sponsor Fri 27-03-20 40 hrs
In-scope statement Project Manager Fri 20-03-20 56 hrs
Out of scope statement Project Manager Mon 16-03-20 24 hrs
Project team meeting
Communication ,Infrastructu
re planning ,Project
Manager, Project Sponsor
Wed 25-03-20 96 hrs
Plan the project
timeline
Project Manager Mon 30-03-20 24 hrs
Estimate the project
budget
Project Sponsor Tue 07-04-20 48 hrs
Risk management
Network Analyst, Project
Manager, Server
support ,Web development
Fri 17-04-20 256 hrs
Submission of project
plan
Project Manager Wed 29-04-20 64 hrs
Approval of project plan Project Manager Thu 30-04-20 8 hrs

8PROJECT MANAGEMENT
Installation Phase Thu 21-05-20 408 hrs
Planning of the data
communication network
installation
Application development
manager ,DBA
analysts ,Network Analyst,
Network Developer
Mon 04-05-20 64 hrs
Installation of IT system
Business services Project
services ,Desktop
support ,Server
support ,System
programmers
Tue 12-05-20 192 hrs
Installation of hardware
infrastructure
Application development
manager ,Business services
Project services ,Desktop
support ,SAP basis
analysts ,System
programmers
Fri 15-05-20 120 hrs
Testing all the
installation process
Tester Thu 21-05-20 32 hrs
Hardware requirements
Infrastructure Planning,
Network Analyst
Thu 21-05-20 64 hrs
Software requirements
ICT MIS Development, SAP
basis analysts and Web
development
Thu 28-05-20
120 hrs
User interface design SAP basis analysts ,SAP Fri 05-06-20 192 hrs

9PROJECT MANAGEMENT
Team A ,SAP Team
B ,System programmers
Page layout
Desktop support ,Web
development Thu 18-06-20 144 hrs
Wireframe creation GIS ,ICT MIS Development Wed 10-06-20 48 hrs
Review and launch of
the website
Network Developer, Project
Manager, Web development Thu 18-06-20 144 hrs
Monitoring and regular
update
Media operator ,Network
Analyst, Project Manager Thu 02-07-20 240 hrs
Testing the hardware and
software infrastructure
Server support ,System
programmers ,Tester, Web
development
Tue 02-06-20 96 hrs
User acceptance testing
Network Analyst, SAP basis
analysts ,Server
support ,Tester
Fri 10-07-20 192 hrs
Update the project
records
Communication ,DBA
analysts Wed 15-07-20 48 hrs
User training SAP Team A ,SAP Team B Thu 16-07-20 160 hrs
Document the lessons
learned
Infrastructure
planning ,Network Analyst,
Project Manager
Wed 29-07-20 216 hrs
Audit the procurement Infrastructure planning Tue 04-08-20 32 hrs
Formal acceptance
Project Manager, Project
Sponsor Thu 13-08-20 112 hrs

10PROJECT MANAGEMENT
Project go live
Application development
manager ,Desktop
support ,Infrastructure
planning ,Network
Developer, Web
development
Mon 24-08-20 280 hrs
1.4c. Resource requirements
Team Resource in Days of Effort
March April May June July Aug
Business
services
Project services

GIS 
ICT MIS
Development
 
Application
development
manager

SAP Team A  
SAP Team B  
Web
development
   
Desktop   

11PROJECT MANAGEMENT
support
Server support    
System
programmers
 
SAP basis
analysts
  
DBA analysts  
Media operator 
Communicatio
n
 
Infrastructure
planning
  
1.4d. Project budget
Initial Estimate Margin of
Confidence %
Ongoing costs
Internal charges
Staff $30,000 100% $30,000
Other $26,900 95% $27,900
External costs
Hardware $25,000 95% $26,000
Software $40,000 99% $40,100
Other SCC resources $5,000 99% $6,000

12PROJECT MANAGEMENT
Other $19,000 95% $20,000
Total: $145,900 $150,000
1.4e. Project tolerances
Time tolerance: In this project plan, the time tolerance is 1 week, therefore the project
is to be delivered 1week earlier or 1 week later without having any impact on the project
success (Redwood et al. 2017). If the project is completed too earlier, then it will be a
problem for other project otherwise too late, it will miss the scheduled deadline for the
project.
Cost tolerance: As the project plan is CAD$150,000 project, therefore with a
tolerance of 10%, the project can spend up to CAD$160,000 before approval for its project
spending.
Quality tolerance: This software product has a response time of between 0 as well as
1.0 seconds when the user clicks on the webpage (Solar et al. 2017).
1.5 Acceptance criteria
Following are list of the acceptance criteria for this specific project plan as:
i. There is 25% increase in profitability and growth of the school due to
implementing data communication network in the school.
ii. There is 30% increase in the customer satisfaction as more pupils are attracted
towards the school.
iii. There is 10% increase in international pupils due to development of website
for the school.

13PROJECT MANAGEMENT
iv. There is 10% increase in the project cost and the project meets with its
timeline to complete the project 7 days earlier.

14PROJECT MANAGEMENT
1.6 Organization- roles and responsibilities
Roles Responsibilities
Project Manager  Planning of resources
 Leading the project team
 Time management and budget estimation
 Monitoring project progress
 Project reporting and documentation
Project Sponsor  Negotiate the project funding
 Monitoring the project budget
 Review the project scope changes
 Identify success factors if the project and approval of project
deliverables (Johnson-Cramer, Berman and Post 2017)
Network
Developer
 Design as well as implementation of communication network
 Perform network modelling
 Perform network planning
 Monitoring of network and systems
Network Analyst  Maintenance of the network components in the business
 Installation and layout of the data communication network
(Oppong, Chan and Dansoh 2017).
 Configure of the organizational network and computer systems
Tester  Review of the software needs and prepare test scenarios
 Execution of the system and network testing
 Analysing the outcomes of test on database impact
Business services  Compliance for the range of project clients

15PROJECT MANAGEMENT
Project services  Providing of taxation support to the business
ICT MIS
Development
 Managing of data and information
 Helping the business to take IT decisions (Epstein et al. 2017).
Application
development
manager
 Monitor and design the software applications
 Maintain and support the upgrade of existing system
SAP Team A  Taking responsibility of data center, network infrastructure,
databases and SAB services (Huemann, Eskerod and
Ringhofer 2016).
SAP Team B  Creating of SAP modules
 Planning and coding for SAP services
Web developer  Design and coding of websites as per client’s requirements
 Create visual appeal of sites that will feature user friendly
design
Desktop support  Assisting the project client with hardware as well as software
problems
 Set up the IT systems
 Install of the software
Server support  Implement and maintain of IT systems
 Resolve issues of server
 Support the IT systems for the end users (Holloway 2016).
System
programmers
 Prepare for installation of software
 Install the software by loading of software in computer
SAP basis
analysts
 Maintenance of buffer pools
 Configuration of the system

16PROJECT MANAGEMENT
 Problem analysis and monitoring of system
DBA analysts  Writing of the scripts
 Keeping database run for 24 * 7
 Back up of the database
Media operator  Provide operational support and media preparation
Communication
Manager
 Perform internal as well as external communication of business
 Engagement of the project stakeholders
Infrastructure
planning
 Facilitating preparation of the service plan
 Procurement of the project
 Facilitating of design as well as development of hardware and
software infrastructure (Oppong, Chan and Dansoh 2017).
1.7 Project quality
ISO 9000 quality standard is used helping the business to document a quality system
required to maintain the quality of ICT system. It will help the project in increasing business
efficiency, productivity as well as improving customer retention (Kiran 2016).
Quality review Person responsible
All hardware as well as software are adhere to the guidelines
and codes.
Quality Analyst
Monitoring of quality work for the plan Quality Analyst
Quality assurance of the plan Quality Analyst
Checking for quality of the hardware and software equipment Quality Analyst

17PROJECT MANAGEMENT
Change control process is help the project manager to take approval of the project
changes and evaluate and reject changes as required for the project.
1.8 Project controls
In order to control the project cost as well as project schedule, the quality project team
is responsible to conduct following project reviews:
Initial project plan review: It is conducted after completion of the project initiation
phase and conducted once.
Progress review: It is conducted after completion of each project stages and
performed as required.
Completion review: After closure of the project plan, it is conducted at once
(Endrullat et al. 2016).
Project board review: It is conducted to review and prioritize the project work
presented for application review, system development and software and hardware installation.
Management reporting: This report contains performance data as well as analysis on
the implemented data communication network and hardware infrastructure for measuring
project success rate (O’Neill, Sohal and Teng 2016).
1.9 Risk management
ID Description of risk Probability Impact Action Target
completion
1 There is rise in the
user domain causes
problems in
Moderate Major There is required to
have data scanner
to detect the threats
06-05-2020

18PROJECT MANAGEMENT
network. before impact on
development work.
2 There is overrun of
the project budget
due to delay in
project activities.
Likely Major There should
require to estimate
the budget using
project
management
software.
10-06-2020
3 The client has
suddenly changed
the project scope
causes scope creep.
Likely Moderate Prior approval of
the project stages
should be taken
from the project
client.
15-07-2020
4 Little experience of
staffs to manage
new technologies
Moderate Major Training should be
provided to the
staffs involved in
the work.
27-07-2020
5 ICT policies are not
reviewed recently.
Unlikely Minor There should be
strict review of
ICT policies while
working in the
implementation
work.
18-08-2020

19PROJECT MANAGEMENT
1.10 Security considerations
Security area Requirements Comments Responsibility
Backup/recovery Restore the system in
operational stage after
system failure
Restore of data from
backup
Network Analyst
Disaster
recovery
It will help the company to
reduce unexpected
problems (Iriondo et al.
2019).
It has ability to
relocate the system
where it is safe.
ICT Developer
Access control Restrict of access of
unauthorized person
Assign to unique ID
those have authorized
to access data
Web Developer
System
administration
Ensure that the system is
running effectively
Configuration of the
computer system
properly
Analyst
Legislative
requirements
Ensure of efficient
bookkeeping practices
Strict policies as well
as procedures of the
organization to take
correct decisions
(Turner and Ledwith
2018).
Project Manager

20PROJECT MANAGEMENT
2. Gantt chart
Figure 1: Gantt chart
(Source: Created by author using Ms Project)

21PROJECT MANAGEMENT
3. Risk Management Plan
a. Risk management strategy and analysis
The identified risks in the ICT project are:
i. There is rise in the user domain causes problems in network.
ii. There is overrun of the project budget due to delay in project activities.
iii. The client has suddenly changed the project scope causes scope creep.
iv. Little experience of staffs to manage new technologies
v. ICT policies are not reviewed recently.
The impact of the risks on the project is shown as:
Type of risk Impact of project risk
There is rise in the user
domain causes problems in
network.
The possible impact of this risk provides effect on entire
infrastructure of the data communication network and
hardware (Hopkin 2018).
There is overrun of the
project budget due to delay
in project activities.
The impact of financial risk will lead to loss of money of the
business.
The client has suddenly
changed the project scope
causes scope creep.
It leads to failed business decisions as change in scope can
cause change in entire project plan.
Little experience of staffs to
manage new technologies
Risks of human factor causes reduction of human
performance and non-availability of experienced staffs for the
project (Hubbard 2020).
ICT policies are not Change in regulations as well as law of ICT can affect the

22PROJECT MANAGEMENT
reviewed recently. business as there is a significant change in organizational
framework (Aven 2016).
The project manager is responsible for managing the risk management activities. The
financial project risk provides high impact on the project objectives and success while other
risks are provided medium impact on the project success. In order to manage the program
risks, the project manager is required to manage time, cost, quality, stakeholders and project
benefits. The ICT project is consisted of definite end time, therefore it is required to manage
budgeted time as per schedule (Almeida, Hankins and Williams 2017). The project consumes
resources, therefore it is required to manage investment with understanding of creating
business value (benefits exceed with amount spending in the project). This ICT project is
involved with specific project deliverables and work products, therefore the deliverables are
required to meet with objectives. Managing of quality involves with quality assurance in
addition quality controlling (Rampini, Viswanathan and Vuillemey 2019). Each of the project
impacts people and managing of stakeholders means identification of project stakeholders,
interest level, influence in project and managing stakeholder relationships.
b. Risk management framework
The risk management standards, policies and legislations used for managing the
project risks in this project plan are as follows:
ISO 31000:2009 risk management: This international risk management standard
stated success of the risk management by assisting to manage risk throughout application of
process in managing risks. It ensures to provide information about project risks as basis to
make decisions at all organizational levels (Sadgrove 2016). It creates and protects value of
the business with be an essential portion of administrative processes. It is a principle for

23PROJECT MANAGEMENT
implementation of the project plan. This standard is suitable for strategic analysis of risks.
This standard includes risk management tools and techniques as brainstorming session,
judgement based on data gathered and risk checklists used to identify project risks
(Wiengarten et al. 2016). The scale of risk is categorized based on its consequences and
probability.
ISO/IEC 31010:2009 risk management: It is a standard for providing guidance to
select and application of risk management processes to manage risks in this project. It
provides evidences to make knowledgeable decisions on how to treat project risks and
mitigate them. This standard includes some of the tools and techniques for risk identification
such ad checklists, flow chart and scenario analysis. This standard is suitable for strategic
analysis of risks (Tupa, Simota and Steiner 2017). The identified project risks are evaluated
based on its impact and likelihood of occurrence in the business,
The stakeholders those views are of primary importance in managing project risks such as
customers, suppliers, employees and project sponsor.

24PROJECT MANAGEMENT
c. Risk analysis and management
Risk Identification Risk Estimation Risk Evaluation Risk Treatment
Duration Intensity/
Magnitude
Potential
consequences
Probability Impact
There is rise in the user
domain causes problems in
network.
1 month Medium Failure to identify and
manage system
failures lead to
technical risks.
Moderate Major Prevention
There is overrun of the
project budget due to delay
in project activities.
1 month Very high Change in the market
rate of interest leads to
financial risks.
Likely Major Reduction
The client has suddenly
changed the project scope
causes scope creep.
15 days High This risk affects the
ability of the
organization to
execute their IT
Likely Moderate Contingency

25PROJECT MANAGEMENT
strategic plan.
Little experience of staffs to
manage new technologies
10 days Medium Non-availability of
experienced staffs for
the project
Moderate Major Acceptance
ICT policies are not
reviewed recently.
7 days Low Change in framework
of the industry and
cost structure
Unlikely Minor Acceptance

26PROJECT MANAGEMENT
d. Categories of risks
Type of risk Risk category
There is rise in the user domain causes problems in
network.
Technical risk
There is overrun of the project budget due to delay in
project activities.
Financial risk
The client has suddenly changed the project scope causes
scope creep.
Strategic risk
Little experience of staffs to manage new technologies Human factor risk
ICT policies are not reviewed recently. Legal and
regulatory risk

27PROJECT MANAGEMENT
e. Risk log
Risk
ID
Risk
Type
Risk owner Date
identified
Date last
updated
Description Cost
(in
CAD$)
Probability Impact Proximity Possible
response action
Target
date
Action owner Closure
date
Risk
status
Risk action
status
R1
Technical
risk
Network
Developer
06-04-2020 16-04-2020 There is rise in the
user domain causes
problems in
network.
16,000 Moderate Major Medium There should
require to
maintain the
network
infrastructure of
data
communication
network so that it
would lessen
causes of system
failures.
02-05-
2020
Application
development
manager
06-05-
2020
Open Prevention
R2
Financial
risk
Project
Manager
10-05-2020 22-05-2020 There is overrun of
the project budget
due to delay in
project activities.
40,000 Likely Major High It is required to
stay cost
efficient for the
project plan by
reviewing the
budget plan in
the project
meetings.
10-06-
2020
Project
Sponsor
10-06-
2020
Open Reduction

28PROJECT MANAGEMENT
R3
Strategic
risk
SAP basis
analysts
30-06-2020 04-06-2020 The client has
suddenly changed
the project scope
causes scope creep.
26,000 Likely Moderate Medium It should require
to everyone
understand the
scope of the
project and take
prior approval on
project scope
statement from
client.
12-07-
2020
Project
Manager
15-07-
2020
Open Contingency
R4
Human
factor risk
Business
services
17-07-2020 23-07-2020 Little experience of
staffs to manage
new technologies
32,000 Moderate Major Medium There should
require to recruit
more resources
for the project
based on
technical
requirements.
25-07-
2020
Project
Manager
27-07-
2020
Open Acceptance
R5
Legal and
regulatory
risk
Infrastructur
e planner
11-08-2020 04-08-2020 ICT policies are
not reviewed
recently.
10,000 Unlikely Minor Low There should
implementation
of ICT policies
and regulations
in the
organization so
that the worker
should familiar
with it.
18-08-
2020
Project
Manager
18-08-
2020
Open Acceptance

29PROJECT MANAGEMENT
4. Project Progress Reporting Strategy
Project objectives: The objectives of this project plan are meet by completing
the project plan on scheduled timeline of 4 months and estimated budget of
CAD$150,000. Due to implementation of data communication network and hardware
infrastructure, there is improvement over network capability of the primary school
along with improvement in running the school. The scope of the project is also
achieved by providing storage solution for easier data access back to the school.
Advanced hardware and software solutions help in increasing usage of the modern
technology in the primary school.
Project performance: The performance of the project is measured by tracking
the project time, cost as well as scope of the project. The time of the plan is meet with
its scheduled time and estimated budget, therefore the project will get success. The
project has meet with its scope to set up hardware infrastructure and data
communication network for the primary school (Ozumba and Shakantu 2018). It helps
to enhance usage of the modern technology in the school with an aim to increase in
business efficiency.
Change management: The project plan is being changed to fit with scope. The
project manager ensured that all project changes are followed as well as approved by
project client. All the project changes are to be communicated with the project team
members (Pollard 2019). The changes in project provides impact on both timeline as
well as monetary values. If there is scope changes in the project, then it provides huge
impact on the project success, therefore the team members should take approval of the
project scope from client before conducting the project work.

30PROJECT MANAGEMENT
Project quality: All the hardware as well as software are adhere to the laws as
well as regulations of the risk management. There is proper monitoring of project
work by the quality analyst on daily basis to stay committed to quality assurance of
project planning (Turner 2016). The purpose of quality plan is addressing quality
assessment and improvement in the project scope and network infrastructure of
primary school.
Post project review: There is review of security policies for providing up-to-
date security plan for the users as well as workstation domains at the network offices.
The security policies should ensure to provide confidentiality and availability of
confidential data included personal information is protected to authorized users
(Ferrada et al. 2016).
Lesson learned: From this ICT project planning, following lessons are learned
as:
i. Avoidance of the mistakes in the project
ii. Reduction of the project risks by using risk mitigation and risk management
framework (Cole, Giné and Vickery 2017).
iii. Seizing of the business opportunities by achieving the project objectives as
well as project scope
iv. Increasing in the quality of the project (McClory, Read and Labib 2017).
v. Informing as well as building of the project team at starting of the project plan
Follow on actions: The staffs are provided with awareness training on the
security policies and risk management frameworks (Pollard 2019).
Benefits: The data communication network and hardware infrastructure is
implemented to protect resources of the organization on network as well as increase in

31PROJECT MANAGEMENT
business efficiency. The users are trained on how to use the computer and new
implemented network which can better protect data from unauthorized person and
data compromise (Duffield and Whitty 2016). This implementation plan will benefit
the primary school to enhance business efficiency and prevent loss of data along with
organizational assets.

32PROJECT MANAGEMENT
References
Ahmad, A., Arshad, N.H. and Aris, S.R.S., 2018. The Relationship between Procurement
Officers, Project Management Success and Procurement Procedure in Ict Public Outsourcing:
a Systematic Literature Review. International Journal of Engineering & Technology, 7(3.20),
pp.66-70.
Almeida, H., Hankins, K.W. and Williams, R., 2017. Risk management with supply
contracts. The Review of Financial Studies, 30(12), pp.4179-4215.
Aven, T., 2016. Risk assessment and risk management: Review of recent advances on their
foundation. European Journal of Operational Research, 253(1), pp.1-13.
Blaskovics, B., 2016. The impact of project manager on project success—The case of ICT
sector. Society and Economy. In Central and Eastern Europe ǀ Journal of the Corvinus
University of Budapest, 38(2), pp.261-281.
Cole, S., Giné, X. and Vickery, J., 2017. How does risk management influence production
decisions? Evidence from a field experiment. The Review of Financial Studies, 30(6),
pp.1935-1970.
Duffield, S. and Whitty, S.J., 2016. How to apply the Systemic Lessons Learned Knowledge
model to wire an organisation for the capability of storytelling. International journal of
project management, 34(3), pp.429-443.
Endrullat, C., Glökler, J., Franke, P. and Frohme, M., 2016. Standardization and quality
management in next-generation sequencing. Applied & translational genomics, 10, pp.2-9.
Epstein, E., Freeman, R.E., Jensen, M.C., Laplume, A.O., Sonpar, K., Litz, R.A., Margolis,
J.D., Walsh, J.P., Verbeke, A. and Tung, V., 2017. The future of stakeholder management
theory: A temporal Perspective. Business Ethics Quarterly, 10(1), pp.i-xiii.

33PROJECT MANAGEMENT
Ferrada, X., Núñez, D., Neyem, A., Serpell, A. and Sepúlveda, M., 2016. A lessons-learned
system for construction project management: a preliminary application. Procedia-Social and
Behavioral Sciences, 226, pp.302-309.
Fustik, V. and Macedonia, R., 2018. Education and practical knowledge for project and risk
management in ICT area. International Journal on Information Technologies & Security, 4.
Holloway, J., 2016. What stakeholder management should learn from sales and
marketing. Further Advances in Project Management: Guided Exploration in Unfamiliar
Landscapes (1st. Ed). New York: Gower Book, p.236.
Hopkin, P., 2018. Fundamentals of risk management: understanding, evaluating and
implementing effective risk management. Kogan Page Publishers.
Hubbard, D.W., 2020. The failure of risk management: Why it's broken and how to fix it.
John Wiley & Sons.
Huemann, M., Eskerod, P. and Ringhofer, C., 2016. Rethink!: Project Stakeholder
Management. Project Management Institute, Incorporated.
Iriondo, I., Montero, J.A., Sevillano, X. and Socoró, J.C., 2019. Developing a videogame for
learning signal processing and project management using project-oriented learning in ICT
engineering degrees. Computers in Human Behavior, 99, pp.381-395.
Johnson-Cramer, M.E., Berman, S.L. and Post, J.E., 2017. Re-examining the concept of
‘stakeholder management’. In Unfolding Stakeholder Thinking 2 (pp. 145-161). Routledge.
Kiran, D.R., 2016. Total quality management: Key concepts and case studies. Butterworth-
Heinemann.
Lyngso, S., 2017. Agile strategy management: techniques for continuous alignment and
improvement. CRC Press.

34PROJECT MANAGEMENT
McClory, S., Read, M. and Labib, A., 2017. Conceptualising the lessons-learned process in
project management: Towards a triple-loop learning framework. International Journal of
Project Management, 35(7), pp.1322-1335.
O’Neill, P., Sohal, A. and Teng, C.W., 2016. Quality management approaches and their
impact on firms׳ financial performance–An Australian study. International Journal of
Production Economics, 171, pp.381-393.
Oppong, G.D., Chan, A.P. and Dansoh, A., 2017. A review of stakeholder management
performance attributes in construction projects. International Journal of Project
Management, 35(6), pp.1037-1051.
Ozumba, A.O.U. and Shakantu, W., 2018. Exploring challenges to ICT utilisation in
construction site management. Construction Innovation.
Pollard, C.E., 2019. Lessons learned from client projects in an undergraduate project
management course. Journal of Information Systems Education, 23(3), p.3.
Rampini, A.A., Viswanathan, S. and Vuillemey, G., 2019. Risk management in financial
institutions. The Journal of Finance.
Redwood, J., Thelning, S., Elmualim, A. and Pullen, S., 2017. The proliferation of ICT and
digital technology systems and their influence on the dynamic capabilities of construction
firms. Procedia engineering, 180, pp.804-811.
Sadgrove, K., 2016. The complete guide to business risk management. Routledge.
Solar, M., Murua, S., Godoy, P. and Yañez, P., 2017, September. Correlation between ICT
investment and technological maturity in public agencies. In International Conference on
Electronic Government (pp. 411-420). Springer, Cham.
Sweeting, P., 2017. Financial enterprise risk management. Cambridge University Press.

35PROJECT MANAGEMENT
Tupa, J., Simota, J. and Steiner, F., 2017. Aspects of risk management implementation for
Industry 4.0. Procedia Manufacturing, 11, pp.1223-1230.
Turner, R. and Ledwith, A., 2018. Project management in small to medium‐sized enterprises:
fitting the practices to the needs of the firm to deliver benefit. Journal of Small Business
Management, 56(3), pp.475-493.
Turner, R., 2016. Gower handbook of project management. Routledge.
Wiengarten, F., Humphreys, P., Gimenez, C. and McIvor, R., 2016. Risk, risk management
practices, and the success of supply chain integration. International Journal of Production
Economics, 171, pp.361-370.