Critical Success Factors of ICT Projects

This assignment analyzes the critical success factors (CSFs) for Information and Communications Technology (ICT) project success. It examines relevant research papers, including those by bin Ahlan, Joseph & Marnewick, and Too & Weaver, to identify key CSFs. The analysis highlights the importance of various factors such as alignment with organizational goals, clear communication, effective risk management, and strong leadership. It also discusses how these factors contribute to achieving project success based on established definitions and frameworks.

ICT Project Management
RALS Roistering system

Table of Contents
Project overview.........................................................................................................................3
Part One: MOV - Measurable Organizational Value.............................................................3
1.1 Desired area of Impact.....................................................................................................3
1.2 Value of the project plan......................................................................................................4
Part Two: Define Scope and produce a Scope Management Plan.........................................5
2.1 Detailed scope of the project............................................................................................5
Part 3: Project schedule and WBS.............................................................................................7
Part 4: Project risk analysis and plan.......................................................................................13
Part 5: Quality Management Plan...........................................................................................15
Part 6: Project Closure............................................................................................................15
a. Annotated Bibliography...................................................................................................15
Bibliography.............................................................................................................................18

Project overview
The paper mainly analyzed the show of Riverina agricultural in addition to its life style that is
mainly conducted to exhibit various types of events related to agricultural, the products life
style and different local businesses. Moreover, it is identified that the show become well-
known and the organization also required large figure of volunteers to supervise the show. It
is identified that various types of manual procedures are being utilized by business
organization to control the information of volunteers is not appropriate; hence the business is
mostly associated with the Globex demonstrate that expand the roistering system.
In this particular report, information related to the project budget, calendar plan, managerial
plan and used funds are mostly discussed. Apart from that it is also recognized that this paper
discusses concerning the risk as well as issues that project faces during the development the
roistering system.
Part One: MOV - Measurable Organizational Value
1.1 Desired area of Impact
Customer:-It is recognized that the created system is become helpful to lessen different types
of queries that are being raised by the client.
Strategy: - This is being identified that the proposed system becomes advantageous to track
different types of details of the volunteers.
Social:-The developed system becomes advantageous in order to make the proper
communication with client in more effective manner.

Operational:-The deployment of this roistering system helps to store various significant
details of employees in the system that mainly helps to make all types of related operations
easier.
Financial:-It is recognized that the roistering system developed which is being by Globex
become cooperative to offer with large quantity of return money that spend into the business.
1.2 Value of the project plan
The values of project plan are mainly discussed below:-
Better:-It is being recognized that the new system of expansion assists to provide better
facilities to both volunteers and clients.
Cheaper:-The operational price of business mainly lessens by the use of recently develop
roistering system.
Faster:-The reply time for both volunteers as well as consumers gets decreased by using the
roistering system.
Appropriate timeframe and matrices:-
Rank Impact Metrics Timeframe
1. Operational The business functions becomes less time
consuming because of the use of developed
roistering system.
2 months
2. Strategy All important details of customers and
volunteers are mainly track with the help of the
system.
1 month
3. Customer The response time get minimized because of 2 months

the uses of this roistering system.
4. Social The relations between customers and
volunteers are getting improved with the
proper utilization of roistering system.
3 months
5. Financial The operational costs are get reduced by doing
the proper utilization of system
5 months
Part Two: Define Scope and produce a Scope Management Plan
2.1 Detailed scope of the project
Requirements: it is acknowledged that the Roistering system is mainly required to enter
different significant details of volunteers who are primarily concerned about the RALS show.
Moreover, it is recognized that the developed RALS system is became competent to track all
volunteers with the assist of offered details.
In-scope and Out-scope statement:
In-scope statement includes:
o Creation of this Roistering system for the Globex business pruposes
o Facilities to incorporates various volunteers particulars that consists of personal
information, qualifications information and dissimilar other additional details
o Closure of this project in the time period of total of 244 days
Out-scope statement includes:
 Different types of maintenance issues related to proposed system correlated with
both data security and service quality are not inter-related.
 Proper training is not offered to the Globex workers

Deliverables: Some of the project deliverables are listed below:
 To conduct of appropriate testing of system, a suitable testing plan is prepared
 Proper documentation of entire developmental phase is prepared
 Proper documentation of budget plan is established
 Preparation of training manual
 Different verification methods for the project scope
 Offering with proper report based on the requirements of system
Scope Verification procedures: The acceptance criteria of this system are become
cooperative to meet different types of needs as well as requirements of the clients. It also
helps to minimize the reply time in order to provide with better resolution of all types of
queries.
List of resources:
Resource
Name
Type
Materia
l Label
Initial
s
Grou
p
Max.
Unit
s
Std.
Rate
Ovt.
Rate
Cost/
Use
Accrue
At
Base
Calenda
r
Developer
Wor
k
D
100
%
$80.00/
hr
$0.00/
hr
$0.00
Prorate
d
Standard
System
analyst
Wor
k
S
100
%
$90.00/
hr
$0.00/
hr
$0.00
Prorate
d
Standard
Accountant
Wor
k
A
100
%
$85.00/
hr
$0.00/
hr
$0.00
Prorate
d
Standard
Project
manager
Wor
k
P
100
%
$90.00/
hr
$0.00/
hr
$0.00
Prorate
d
Standard

Tester
Wor
k
T
100
%
$70.00/
hr
$0.00/
hr
$0.00
Prorate
d
Standard
Executive
sponsor
Wor
k
E
100
%
$75.00/
hr
$0.00/
hr
$0.00
Prorate
d
Standard
Requiremen
t analyst
Wor
k
R
100
%
$65.00/
hr
$0.00/
hr
$0.00
Prorate
d
Standard
Risk
manager
Wor
k
R
100
%
$70.00/
hr
$0.00/
hr
$0.00
Prorate
d
Standard
Part 3: Project schedule and WBS
3.1 Project schedule
Task Name Duration Start Finish Resource Names
RAILS Rostering System 244 days
Mon
9/25/17
Thu 8/30/18
Specification determination 23 days
Mon
9/25/17
Wed 10/25/17
Undertaking feasibility study
for the different manual system
6 days Mon 9/25/17 Mon 10/2/17
Project manager,
Requirement
analyst
Business needs identification 6 days Tue 10/3/17 Tue 10/10/17
Requirement
analyst
Creation of SRS document 7 days Wed
10/11/17
Thu 10/19/17 Project manager,
Requirement

analyst
Meeting arrangement 4 days Fri 10/20/17 Wed 10/25/17 Project manager
Milestone: completion of
specification determination
0 days
Wed
10/25/17
Wed 10/25/17
Development team selection 38 days
Thu
10/26/17
Mon 12/18/17
Development of vendor
selection
11 days
Thu
10/26/17
Thu 11/9/17
Accountant,
Project manager
Checking development
history of the vendors
12 days Fri 11/10/17 Mon 11/27/17
Executive
sponsor, Project
manager
Development task scheduling 7 days
Tue
11/28/17
Wed 12/6/17
Developer,
Project manager
Budget planning for
development
8 days Thu 12/7/17 Mon 12/18/17
Accountant,
Executive
sponsor, Project
manager
Milestone: completion of
team selection
0 days
Mon
12/18/17
Mon 12/18/17
Designing phase 69 days
Tue
12/19/17
Fri 3/23/18
Module improvement for
volunteer management
21 days
Tue
12/19/17
Tue 1/16/18
Developer,
Project manager
First prototype development 17 days Wed 1/17/18 Thu 2/8/18 Developer

Improvement within new
system installation
15 days Fri 2/9/18 Thu 3/1/18
Developer,
Project manager
Determining the needs of the
system
16 days Fri 3/2/18 Fri 3/23/18
Project manager,
System analyst
Milestone: Completion of
design phase
0 days Fri 3/23/18 Fri 3/23/18
System implementation
system
33 days
Mon
3/26/18
Wed 5/9/18
Different business objectives
development
13 days Mon 3/26/18 Wed 4/11/18
Developer,
Requirement
analyst
Amendments within the part
of the system that is implemented
12 days Thu 4/12/18 Fri 4/27/18
Developer,
Project manager
Using compatible software
and hardware
8 days Mon 4/30/18 Wed 5/9/18
Accountant,
Project manager,
System analyst
Milestone: Completion of
system implementation system
0 days Wed 5/9/18 Wed 5/9/18
Testing phase 26 days Thu 5/10/18 Thu 6/14/18
Identifying test cases as well
as test plan
7 days Thu 5/10/18 Fri 5/18/18 Tester
Testing the developed system 8 days Mon 5/21/18 Wed 5/30/18
Project manager,
Tester
Information system analysis 9 days Thu 5/31/18 Tue 6/12/18 Executive

from the data
sponsor, Project
manager
Results documentation 2 days Wed 6/13/18 Thu 6/14/18 Project manager
Milestone: acceptance of the
test results by client
0 days Thu 6/14/18 Thu 6/14/18
Risk management phase 30 days Fri 6/15/18 Thu 7/26/18
Assessment as well as risk
identification
11 days Fri 6/15/18 Fri 6/29/18
Project manager,
Risk manager
Presenting risks impact 7 days Mon 7/2/18 Tue 7/10/18 Risk manager
Risks mitigation 8 days Wed 7/11/18 Fri 7/20/18
Project manager,
System analyst
Impact of the risk registering 4 days Mon 7/23/18 Thu 7/26/18
Project manager,
Risk manager
Milestone: Acceptance of the
risk document by the client
0 days Thu 7/26/18 Thu 7/26/18
Closure of the project 25 days Fri 7/27/18 Thu 8/30/18
Evaluating rostering system
functions
13 days Fri 7/27/18 Tue 8/14/18
Executive
sponsor, Project
manager
Final developed product roll
out
12 days Wed 8/15/18 Thu 8/30/18 Project manager
Milestone: Completion of
closure phase of the project
0 days Thu 8/30/18 Thu 8/30/18

Figure 1: Gantt chart
(Source: Created by author)

3.2 WBS
RAILS Rostering System
Specification
determination
Undertaking
feasiability study for
the different manual
system
Business needs
identification
Creation of SRS
document
Meeting
arrangement
Milestone:
completion of
specification
determination
Development team
selection
Development of
vendor selection
Checking
development history
of the vendors
Development task
schedulling
Budget planning for
development
Milestone:
completion of team
selection
Designining phase
Module
improvement for
volunteer
management
First prototype
development
Improvement within
new system
installation
Determining thw
needs of the system
Milestone:
Completion of
design phase
System implementation
system
Different business
objectives
development
Ammendments within
the part of the system
that is implemented
Using compatible
software and
hardw are
Milestone:
Completion of
system
implemenatation
system
Testing phase
Identifying test cases
as w ell as test plan
Testing the
developed system
Information system
analysis from the
data
Results
documentation
Milestone:
acceptance of the
test results by client
Risk management phase
Assesment as w ell as
risk identification
Presennting risks
imapct
Risks mitigation
Impcat of the risk
registering
Milestone:
Accepetance of the
risk document by the
client
Closure of the project
Evaluating rostering
system functions
Final developed
product roll out
Milestone: Completion
of closure phase of
the project
Figure 2: Work Breakdown Structure
(Source: Created by author)
3.3 Milestone of the Project plan
WBS Task Name Expected Date
0 RALS Roistering System Fri 9/23/16
1 Completion of the project specification Wed 10/25/17
2 Completion of selection of team members Mon 12/18/17
3 Completion of the designing phase Fri 3/23/18
4 Completion of implementation of the system Wed 5/9/18
5 Acceptance of the identified risks into the project by Thu 7/26/18

the project client
6 Completion of the project closure phase Thu 8/30/18
Part 4: Project risk analysis and plan
No. REF001 REF003 REF03 REF004 REF005
Rank 1st 2nd 3rd 4th 5th
Risk System
Failure
Over
budgeting
Improper
scheduling
Management
Issue
Resources
Description The system is
not installed
in proper
manner within
the business
created
various risks
and
challenges
The budget
estimation of
the project was
not done
accurately.
The project
manager does
not understand
the project
objectives and
goals properly
Improper
management of
the project
activities
creates number
of challenges
Category Technical Financial Project Operational Resource
Triggers The
installation of
system is not
done perfectly
that exactly
needed
They assumed
that the budget
calculation is
not done
accurately.
Improper
understanding
of project
creates
scheduling
risk
It mainly
occurs due to
improper
experience of
managers
Improper use
of project
resources
Potential
Responses
The system
was required
Proper
estimation can
The project
manager must
The project
managers must
Improper use
of resources

to be installed
in corrected
way.
be done after
doing the
effective
market
analysis
analyze as
well as
determine the
requirements
of the project
manage the
project by
following
proper
strategist as
well as methods
due to proper
experience
Risk Owner IT Engineer Budgeter Designer Project
Manager
Planner
Probability Likely Possible Likely Possible Almost
certain
Impact Critical Medium Medium Medium Low
Probability of
occurrence
Impact of occurrence
Very low Low Medium High Very high
Rare
Unlikely
Possible Management
Issue
Over budgeting
Likely Absence of
Design
Methodology
System Failure
Almost Certain Delay in
completion

Part 5: Quality Management Plan
Steps of the quality management plan are mentioned below:
Step 1: Classification of dissimilar quality issues
Step 2: Examination of all types of quality issues are the effects happened into the business
Step 3: Creation of different mitigation techniques
Step 4: Screening of dissimilar actualized techniques
Step 5: Arrangement re-examining
Part 6: Project Closure
a. Annotated Bibliography
Article 1: “Joseph, N. & Marnewick, C. (2014). Structured equation modeling for
determing ICT project success factors. Paper presented at Project Management Institute
Research and Education Conference, Phoenix, AZ. Newtown Square, PA: Project
Management Institute”.
In this article, it fundamentally talked about the tasks independent of industry, sorts are
essentially started to offer esteems to the association. Joseph and Marnewick (2014) talked
about that ICT ventures end up noticeably one the fundamental part for any association. In
this article, scientist distinguished diverse issues identified with ICT ventures don't have
legitimate following records; thusly it comes up short quantities of time and furthermore not
add appropriate esteems to the association. Notwithstanding that, Braglia and Frosolini,
(2014) primarily centers of two unique viewpoints: right off the bat, the examination of
different contributing elements to the venture achievement and besides, commitment of these
elements in to the ICT venture achievement. In this task, a quantative approach is primarily

taken after where all overview respondents are ordered the ICT venture whether it is
effective, tested or fizzled. The model likewise connected by venture chief to guarantee
enhanced undertaking achievement rate.
Article 2: “bin Ahlan, A. R. (2013, November). A coherent framework for understanding
critical success factors of ICT project environment. In Research and Innovation in
Information Systems (ICRIIS), 2013 International Conference on (pp. 342-347). IEEE”.
With regards to ICT venture achievement, there are different gaps recognized around the
field. However, to have the comprehension about the venture it likewise guarantees the
achievement level of the task that for the most part kept up in both hypothetical and useful
way. bin Ahlan, (2013) examined that fundamental point of this undertaking is to build up an
appropriate basic achievement factors (CSFs) structure to help the ICT manager for managing
a wide range of complexities of task measurements that get impacted with the venture
achievement forming. Aside from that, bin Ahlan, (2013) likewise talked about that there are
four thought focuses in light of this system improvement are said underneath: to begin with,
relies upon extensive achievement criteria to quantify the correct association between both
CSFs level and achievement basis level; second, joining of four undertaking measurements to
empower the high substance approval; third, change of basic association between CSFs
assurance and venture achievement definition.
Article 3: “Too, E. G., & Weaver, P. (2014). The management of project management: A
conceptual framework for project governance. International Journal of Project
Management, 32(8), 1382-1394”.
Too and Weaver (2014) suggests affiliations that have an auxiliary set up for changing the
errand desires to their definitive targets will be better set to comprehend their enthusiasm for
wanders, and finish the regard described by their business procedures. This paper dissects

existing investigation; considerations and thoughts of undertaking organization and attempt
wander organization, and offer a structure to develop current speculation headway and
practice. Incorporating existing composition of errand/program organization, organization
and portfolio organization, this paper proposes four key segments to improve the execution of
endeavors and along these lines make a motivating force for affiliations. These four segments
are (1) portfolio organization: focused on picking the right assignments and activities to help
the affiliation's strategy, and completion ones that never again add to the business
achievement of the affiliation; (2) wander sponsorship: giving the prompt association
between the authority and the undertaking or program head, focused on the whole wander
lifecycle; (3) Project Management Office (PMO): giving oversight and essential itemizing
limits; (4) errands and program reinforce: the capable help and organization of endeavors and
tasks are the measures of a feasible organization structure. The inspiration driving the
structure depicted in this paper is to provide guidance to relationship in the progression of
convincing endeavor organization to improve the organization of exercises.