RALS Project Implementation and Evaluation

This assignment focuses on the implementation and evaluation of a Real-time Application Lifecycle System (RALS) project. It presents a checklist to guide project execution, highlighting key aspects like plan development, resource allocation, system design, testing, and documentation closure. The assignment also defines evaluation criteria based on the project plan, resource allocation, documentation, system design, and test results. A thorough understanding of RALS principles and project management methodologies is essential for successful completion.

Running head: ICT PROJECT MANAGEMENT
ICT Project Management
RALS Roistering project

2
ICT PROJECT MANAGEMENT
Table of Contents
Part One: MOV- Measurable Organizational Value..................................................................3
Part Two: Define Scope and produce a Scope Management Plan.............................................5
Part Three: Project Plan...........................................................................................................11
Part Four: Risk Analysis and Management Plan for RALS.....................................................16
Part 5: Quality Management Plan............................................................................................19
Part 6: Project Closure.............................................................................................................19
a. Annotated Bibliography...................................................................................................19
b. Checklist for RALS project..............................................................................................20
C. Evaluation Criteria...........................................................................................................20
Bibliography.............................................................................................................................22

3
ICT PROJECT MANAGEMENT
Part One: MOV- Measurable Organizational Value
The customer, strategies, operational and financial and social is the desired areas of
impact occur for RALS ticketing system developmental project. All these factors are
mainly discussed below:
Areas of Impact Occurs Description Ranking
Financial The money related
framework are needed to
be clarified because of
operations of procedures
for doing the
improvements are mainly
co-ordinating with the
advancements of
operations and also taking
action based suggestions
mentioned.
1st
Customer The customer need to be
realized because the
framework range need to
be raised based on various
sorts of questions that
mainly brought b y general
population in relation to
the task created and
2nd

4
ICT PROJECT MANAGEMENT
framework of RALS.
Operational All operational procedures
are mainly referred based
on security all functional
operations and the
reconciliation of
procedures based on the
adjustment of all types of
procedures.
3rd
Strategy The strategies are needed
to be characterized to
affect all the operations of
RALS by creating various
successful and enhanced
operations.
4th
Social The operational procedures
are needed to be suggested
to build up the security of
operations along with the
combinations of
procedures.
5th
Better- the RALS venture are mainly seen for doing the advancement of other
framework to expand the work proficiency with the help of data administration.

5
ICT PROJECT MANAGEMENT
Faster- the RALS undertaking mainly helps to incorporate all the venture operations
by making advancement of operational expanded speed.
Cheaper- the RALS task mainly helped to deal with the data of solitary database and
needed to diminish all general costs of data framework administration.
Do more- the framework usage of RALS is needed to incorporate all data and
information of the project that helps to build up more intelligent techniques of
association.
Rank Impact Metrics Timeframe
1 Financial Revenue and Money Profit age 6 months
2 Customer Clients are returning to association for doing the
administrations
2 months
3 Operational Very minimal consumptions of time needed to finish all
different hierarchical operations
2 months
4 Strategy The volunteers get followed due to the utilization of
framework that are created by RALS
1 month

6
ICT PROJECT MANAGEMENT
5 Social Volunteers maintained the capacity for doing proper
association with clients.
3 months
Part Two: Define Scope and produce a Scope Management Plan
Scope Definition: The responsibility of RALS Ticketing System advancement helps to build
up all the operational changes of Globex for all the volunteer’s and client’s data with the
assistance of created framework.
Requirements: The project requirements are mainly included for all materials and project
team required to develop all project operations. All the needed requirements of project are
mentioned below:
Resource Name Type
Budgeter Work
Computer Devices Material
Documenter Work
IT Engineer Work
Network Components Material
Planner Work
Project Manager Work
Storage Material
System Analyst Work

7
ICT PROJECT MANAGEMENT
Tester Work
Wireless routers Material
In-Scope and Out-Scope of project: the in-scope things of RALS venture mainly include for
doing the operations of different improvements, undertaking of RALS Ticketing System that
mainly helps to do the increase the effectiveness of administrative data of volunteers and also
helps to do different operational advancements.
The out-scope thing of RALS venture discussed about the up-keeping of exercises,
transportation of materials as well as the preparation of labourers worked at Globex.
Deliverables of the project: different deliverables of this RALS venture includes:
 Resource Allocation Plan and Project Plan
 Project documentation including Charter and Initiation Documentation
 Scope Verification Plan
 System Designing and Implementation plan
 Test results
Acceptance Criteria:
Checklist Item Checked
Progression of Project Plan 
Enhanced Resource Allocation Plan 
Closing down of all project documents 

8
ICT PROJECT MANAGEMENT
Feasible System Design 
Synchronized usage design 
Expected Test Results 
List of resources:
Resource Name Tasks
Budgeter Proper analysis of client’s requirements
Developed exact budget of the project
Outsourcing of required project materials
Computer Devices Installation of different hardware components
Documenter Preparing Initiation documents
Charter documentation
Preparing final documentation
assess of documents
IT Engineer Development of storage place
Data transformation

9
ICT PROJECT MANAGEMENT
Design analysis of ticketing system
Development of User interface
Coding and programming is done
Integration of ticketing system with storage
Installation of different hardware components
Network Components Installing hardware components
Planner Selection of project teams
Selection of proper methodology
Plan outline is developed
Project Manager Analysis of the project feasibility
Requirement Analysis
Project Meetings are held
Signing off the documents
Review of the plan
Signing off the documents
Storage Storage is developed
System Analyst Design Platform is selected
Outline for the design is developed

10
ICT PROJECT MANAGEMENT
Prototype is developed
Review of the prototype
Simulation of the completed design
Tester Black box testing
UX testing
Operations and tested
white box testing
Wireless routers Installation of hardware components
Resource Name Type Initials Std. Rate
Budgeter Work B $60.00/hr
Computer Devices Material C $1,740.00
Documenter Work D $60.00/hr
IT Engineer Work I $95.00/hr
Network Components Material N $970.00
Planner Work P $60.00/hr
Project Manager Work PM $100.00/hr

11
ICT PROJECT MANAGEMENT
Storage Material S $2,320.00
System Analyst Work SA $90.00/hr
Tester Work T $85.00/hr
Wireless routers Material W $870.00
Part Three: Project Plan
WBS Task Name Duration Start Finish Predecessors Resource Names Cost
0
Developing
Ticketing
System for
RALS
140
days
Mon
10/2/17
Fri
4/13/18 $99,980.00
1 Initial Phase 17 days Mon
10/2/17
Tue
10/24/17 $11,360.00
1.1
Analysis of
the project
feasibility
3 days Mon
10/2/17
Wed
10/4/17 Project Manager $2,400.00
1.2 Requirement
Analysis 5 days Thu
10/5/17
Wed
10/11/17 2 Project Manager $4,000.00
1.3
Making
Initiation
documents
4 days Thu
10/12/17
Tue
10/17/17 3 Documenter $1,920.00
1.4 Charter
documentation 3 days Wed
10/18/17
Fri
10/20/17 4 Documenter $1,440.00
1.5
Project
Meetings are
held
1 day Mon
10/23/17
Mon
10/23/17 5 Project Manager $800.00
1.6 Signing off
the documents 1 day Tue
10/24/17
Tue
10/24/17 6 Project Manager $800.00

12
ICT PROJECT MANAGEMENT
M1 Initial Phase
is completed 0 days Tue
10/24/17
Tue
10/24/17 7 $0.00
2 Resource
Accumulation 19 days Wed
10/25/17
Mon
11/20/17 $9,120.00
2.1
Client's
requirement is
analyzed
5 days Wed
10/25/17
Tue
10/31/17 8 Budgeter $2,400.00
2.2 Project team
is selected 7 days Wed
11/1/17
Thu
11/9/17 10 Planner $3,360.00
2.3
Budget for
the project is
developed
4 days Fri
11/10/17
Wed
11/15/17 11 Budgeter $1,920.00
2.4
Outsourcing
of the project
materials
3 days Thu
11/16/17
Mon
11/20/17 12 Budgeter $1,440.00
M2
Accumulatio
n of the
resources
0 days Mon
11/20/17
Mon
11/20/17 13 $0.00
3 Plan Phase 10 days Tue
11/21/17
Mon
12/4/17 $5,760.00
3.1
Plan
methodology is
selected
2 days Tue
11/21/17
Wed
11/22/17 14 Planner $960.00
3.2
Outline for
the plan is
developed
5 days Thu
11/23/17
Wed
11/29/17 16 Planner $2,400.00
3.3 Review of
the plan 3 days Thu
11/30/17
Mon
12/4/17 17 Project Manager $2,400.00
M3 Plan is
completed 0 days Mon
12/4/17
Mon
12/4/17 18 $0.00
4 Design Phase 16 days Tue
12/5/17
Tue
12/26/17 $11,520.00
4.1
Design
Platform is
selected
1 day Tue
12/5/17
Tue
12/5/17 19 System Analyst $720.00

13
ICT PROJECT MANAGEMENT
4.2
Outline for
the design is
developed
3 days Wed
12/6/17
Fri
12/8/17 21 System Analyst $2,160.00
4.3 Prototype is
developed 7 days Mon
12/11/17
Tue
12/19/17 22 System Analyst $5,040.00
4.4 Review of
the prototype 2 days Wed
12/20/17
Thu
12/21/17 23 System Analyst $1,440.00
4.5
Simulation of
the completed
design
3 days Fri
12/22/17
Tue
12/26/17 24 System Analyst $2,160.00
M4 Complete
design is formed 0 days Tue
12/26/17
Tue
12/26/17 25 $0.00
5 Implementatio
n Phase 52 days Wed
12/27/17
Thu
3/8/18 $45,420.00
5.1 Storage is
developed 10 days Wed
12/27/17
Tue
1/9/18 26 IT Engineer,
Storage[1] $9,920.00
5.2 Transfer of
the data 5 days Wed
1/10/18
Tue
1/16/18 28 IT Engineer $3,800.00
5.3
Design
analysis for the
ticket system
4 days Wed
1/17/18
Mon
1/22/18 29 IT Engineer $3,040.00
5.4 Development
of User interface 6 days Tue
1/23/18
Tue
1/30/18 30 IT Engineer $4,560.00
5.5
Coding and
programming is
done
12 days Wed
1/31/18
Thu
2/15/18 31 IT Engineer $9,120.00
5.6
Integration of
ticket system
with storage
8 days Fri
2/16/18
Tue
2/27/18 32 IT Engineer $6,080.00
5.7
Installing
hardware
components
7 days Wed
2/28/18
Thu
3/8/18 33
IT Engineer,
Computer
Devices[1],
Network
Components[1],
Wireless
routers[1]
$8,900.00

14
ICT PROJECT MANAGEMENT
M5
New System
installed in
Globex
0 days Thu
3/8/18
Thu
3/8/18 34 $0.00
6 Testing Phase 20 days Fri
3/9/18
Thu
4/5/18 $13,600.00
6.1 Black box
testing 5 days Fri
3/9/18
Thu
3/15/18 35 Tester $3,400.00
6.2 UX testing 5 days Fri
3/16/18
Thu
3/22/18 37 Tester $3,400.00
6.3 Operations
and tested 5 days Fri
3/23/18
Thu
3/29/18 38 Tester $3,400.00
6.4 white box
testing 5 days Fri
3/30/18
Thu
4/5/18 39 Tester $3,400.00
M6
Results of
tests are
compiled
0 days Thu
4/5/18
Thu
4/5/18 40 $0.00
7 Documentatio
n Phase 6 days Fri
4/6/18
Fri
4/13/18 $3,200.00
7.1 Making final
documents 3 days Fri
4/6/18
Tue
4/10/18 41 Documenter $1,440.00
7.2 Review of
documents 2 days Wed
4/11/18
Thu
4/12/18 43 Documenter $960.00
7.3 Signing off
the documents 1 day Fri
4/13/18
Fri
4/13/18 44 Project Manager $800.00
M7 Project is
closed 0 days Fri
4/13/18
Fri
4/13/18 45 $0.00

15
ICT PROJECT MANAGEMENT
ID Task
Mode
WBS Task Name Duration Start Finish Predecess ors Resource Names Cost
0 0 Developing Ticketing
System for RALS
140 days Mon 10/2/17 Fri 4/13/18 $99,980.00
1 1 Initial Phase 17 days Mon 10/2/17 Tue 10/24/17 $11,360.00
2 1.1 Analysis of the project
feasibility
3 days Mon 10/2/17 Wed 10/4/17 Project
Manager
$2,400.00
3 1.2 Requirement Analysis 5 days Thu 10/5/17 Wed 10/11/17 2 Project Manager $4,000.00
4 1.3 Making Initiation documents4 days Thu 10/12/17 Tue 10/17/17 3 Documenter $1,920.00
5 1.4 Charter documentation 3 days Wed 10/18/17 Fri 10/20/17 4 Documenter $1,440.00
6 1.5 Project Meetings are held1 day Mon 10/23/17 Mon 10/23/17 5 Project Manager $800.00
7 1.6 Signing off the documents1 day Tue 10/24/17 Tue 10/24/17 6 Project Manager $800.00
8 M1 Initial Phase is completed0 days Tue 10/24/17 Tue 10/24/17 7 $0.00
9 2 Resource Accumulation 19 days Wed 10/25/17 Mon 11/20/17 $9,120.00
10 2.1 Client's requirement is
analyzed
5 days Wed 10/25/17 Tue 10/31/17 8 Budgeter $2,400.00
11 2.2 Project team is selected 7 days Wed 11/1/17 Thu 11/9/17 10 Planner $3,360.00
12 2.3 Budget for the project
is developed
4 days Fri 11/10/17 Wed 11/15/17 11 Budgeter $1,920.00
13 2.4 Outsourcing of the
project materials
3 days Thu 11/16/17 Mon 11/20/17 12 Budgeter $1,440.00
14 M2 Accumulation of the resources0 days Mon 11/20/17 Mon 11/20/17 13 $0.00
15 3 Plan Phase 10 days Tue 11/21/17 Mon 12/4/17 $5,760.00
16 3.1 Plan methodology is selected2 days Tue 11/21/17 Wed 11/22/17 14 Planner $960.00
17 3.2 Outline for the plan is
developed
5 days Thu 11/23/17 Wed 11/29/17 16 Planner $2,400.00
18 3.3 Review of the plan 3 days Thu 11/30/17 Mon 12/4/17 17 Project Manager $2,400.00
19 M3 Plan is completed 0 days Mon 12/4/17 Mon 12/4/17 18 $0.00
20 4 Design Phase 16 days Tue 12/5/17 Tue 12/26/17 $11,520.00
21 4.1 Design Platform is selected1 day Tue 12/5/17 Tue 12/5/17 19 System Analyst $720.00
22 4.2 Outline for the design
is developed
3 days Wed 12/6/17 Fri 12/8/17 21 System Analyst $2,160.00
23 4.3 Prototype is developed 7 days Mon 12/11/17 Tue 12/19/17 22 System Analyst $5,040.00
24 4.4 Review of the prototype2 days Wed 12/20/17 Thu 12/21/17 23 System Analyst $1,440.00
25 4.5 Simulation of the
completed design
3 days Fri 12/22/17 Tue 12/26/17 24 System Analyst $2,160.00
26 M4 Complete design is formed0 days Tue 12/26/17 Tue 12/26/17 25 $0.00
27 5 Implementation Phase 52 days Wed 12/27/17 Thu 3/8/18 $45,420.00
28 5.1 Storage is developed 10 days Wed 12/27/17 Tue 1/9/18 26 IT Engineer,Storage[1] $9,920.00
29 5.2 Transfer of the data 5 days Wed 1/10/18 Tue 1/16/18 28 IT Engineer $3,800.00
30 5.3 Design analysis for the
ticket system
4 days Wed 1/17/18 Mon 1/22/18 29 IT Engineer $3,040.00
31 5.4 Development of User
interface
6 days Tue 1/23/18 Tue 1/30/18 30 IT Engineer $4,560.00
32 5.5 Coding and
programming is done
12 days Wed 1/31/18 Thu 2/15/18 31 IT Engineer $9,120.00
33 5.6 Integration of ticket
system with storage
8 days Fri 2/16/18 Tue 2/27/18 32 IT Engineer $6,080.00
34 5.7 Installing hardware
components
7 days Wed 2/28/18 Thu 3/8/18 33 IT
Engineer,Computer
Devices[1],Network
$8,900.00
35 M5 New System installed
in Globex
0 days Thu 3/8/18 Thu 3/8/18 34 $0.00
36 6 Testing Phase 20 days Fri 3/9/18 Thu 4/5/18 $13,600.00
37 6.1 Black box testing 5 days Fri 3/9/18 Thu 3/15/18 35 Tester $3,400.00
38 6.2 UX testing 5 days Fri 3/16/18 Thu 3/22/18 37 Tester $3,400.00
39 6.3 Operations and tested 5 days Fri 3/23/18 Thu 3/29/18 38 Tester $3,400.00
40 6.4 white box testing 5 days Fri 3/30/18 Thu 4/5/18 39 Tester $3,400.00
41 M6 Results of tests are compiled0 days Thu 4/5/18 Thu 4/5/18 40 $0.00
42 7 Documentation Phase 6 days Fri 4/6/18 Fri 4/13/18 $3,200.00
43 7.1 Making final documents3 days Fri 4/6/18 Tue 4/10/18 41 Documenter $1,440.00
44 7.2 Review of documents 2 days Wed 4/11/18 Thu 4/12/18 43 Documenter $960.00
45 7.3 Signing off the documents1 day Fri 4/13/18 Fri 4/13/18 44 Project Manager $800.00
46 M7 Project is closed 0 days Fri 4/13/18 Fri 4/13/18 45 $0.00
Project Manager
Project Manager
Documenter
Documenter
Project Manager
Project Manager
10/24
Budgeter
Planner
Budgeter
Budgeter
11/20
Planner
Planner
Project Manager
12/4
System Analyst
System Analyst
System Analyst
System Analyst
System Analyst
12/26
IT Engineer,Storage[1]
IT Engineer
IT Engineer
IT Engineer
IT Engineer
IT Engineer
IT Engineer,Computer Devices[1],Network Comp
3/8
Tester
Tester
Tester
Tester
4/5
Documenter
Documenter
Project Manager
4/13
S T T S M W F
Aug 20, '17 Nov 19, '17 Feb 18, '18 May 20, '18
The Work Breakdown Structure is shown below:

16
ICT PROJECT MANAGEMENT
0
Developing Ticketing
System for RALS
1
Initial Phase
1.1
Analysis of the project
feasibility
1.2
Requirement Analysis
1.3
Making Initiation
documents
1.4
Charter documentation
1.5
Project Meetings are
held
1.6
Signing off the
documents
M1
Initial Phase is
completed
2
Resource Accumulation
2.1
Client's requirement is
analyzed
2.2
Project team is
selected
2.3
Budget for the project
is developed
2.4
Outsourcing of the
project materials
M2
Accumulation of the
resources
3
Plan Phase
3.1
Plan methodology is
selected
3.2
Outline for the plan is
developed
3.3
Review of the plan
M3
Plan is completed
4
Design Phase
4.1
Design Platform is
selected
4.2
Outline for the design
is developed
4.3
Prototype is developed
4.4
Review of the
prototype
4.5
Simulation of the
completed design
M4
Complete design is
formed
5
Implementation Phase
5.1
Storage is developed
5.2
Transfer of the data
5.3
Design analysis for the
ticket system
5.4
Development of User
interface
5.5
Coding and
programming is done
5.6
Integration of ticket
system with storage
5.7
Installing hardware
components
M5
New System installed
in Globex
6
Testing Phase
6.1
Black box testing
6.2
UX testing
6.3
Operations and tested
6.4
white box testing
M6
Results of tests are
compiled
7
Documentation Phase
7.1
Making final
documents
7.2
Review of documents
7.3
Signing off the
documents
M7
Project is closed
0
1
2345678
9
1011121314
15
16171819
20
212223242526
27
2829303132333435
36
3738394041
42
43444546
140 days 0%
10/2/17 4/13/18
17 days 0%
10/2/17 10/24/17
3 days 0%
10/2/17 10/4/17
5 days 0%
10/5/17 10/11/17
4 days 0%
10/12/17 10/17/17
3 days 0%
10/18/17 10/20/17
1 day 0%
10/23/17 10/23/17
1 day 0%
10/24/17 10/24/17
0 days 0%
10/24/17 10/24/17
19 days 0%
10/25/17 11/20/17
5 days 0%
10/25/17 10/31/17
7 days 0%
11/1/17 11/9/17
4 days 0%
11/10/17 11/15/17
3 days 0%
11/16/17 11/20/17
0 days 0%
11/20/17 11/20/17
10 days 0%
11/21/17 12/4/17
2 days 0%
11/21/17 11/22/17
5 days 0%
11/23/17 11/29/17
3 days 0%
11/30/17 12/4/17
0 days 0%
12/4/17 12/4/17
16 days 0%
12/5/17 12/26/17
1 day 0%
12/5/17 12/5/17
3 days 0%
12/6/17 12/8/17
7 days 0%
12/11/17 12/19/17
2 days 0%
12/20/17 12/21/17
3 days 0%
12/22/17 12/26/17
0 days 0%
12/26/17 12/26/17
52 days 0%
12/27/17 3/8/18
10 days 0%
12/27/17 1/9/18
5 days 0%
1/10/18 1/16/18
4 days 0%
1/17/18 1/22/18
6 days 0%
1/23/18 1/30/18
12 days 0%
1/31/18 2/15/18
8 days 0%
2/16/18 2/27/18
7 days 0%
2/28/18 3/8/18
0 days 0%
3/8/18 3/8/18
20 days 0%
3/9/18 4/5/18
5 days 0%
3/9/18 3/15/18
5 days 0%
3/16/18 3/22/18
5 days 0%
3/23/18 3/29/18
5 days 0%
3/30/18 4/5/18
0 days 0%
4/5/18 4/5/18
6 days 0%
4/6/18 4/13/18
3 days 0%
4/6/18 4/10/18
2 days 0%
4/11/18 4/12/18
1 day 0%
4/13/18 4/13/18
0 days 0%
4/13/18 4/13/18
Part Four: Risk Analysis and Management Plan for RALS
No. REF001 REF003 REF03 REF004 REF005
Rank 1st 2nd 3rd 4th 5th
Risk System Failure Over Design flaws Management Delay in

17
ICT PROJECT MANAGEMENT
budgeting Issue completion
Description Framework
disappointments
may occur
when the
ticketing
arrangement of
RALS neglects
to prepare the
forceful
handling of data
sources to build
up all types of
changing
factors.
The exercise
of venture may
leads to trick
the reason of
over
abundance use
of various
undertaking
assets that may
prompt the
improper
planning of all
tasks.
The issues of
plan that
mainly
created to
prepare the
ticket
framework
become
notable
hazard factors
that mainly
help to
shaping the
defeats of the
project.
Choosing of
proper plan
procedures of
venture
The
administrative
issues are
taken
consideration
for doing the
improvements
of all created
obstacles to
finish the
undertaking
project
Category Technical Financial Technical Operational Performance
Triggers Flaws in system Lack age of
ample
Resources
Non-
existence of
Design
Methodology
Lack age of
Management
Approach
The project
mainly tends
to form
different
developmental
issues for
doing the
successful
completion of
different

18
ICT PROJECT MANAGEMENT
project
operations.
Potential
Responses
Proper testing
of framework
before doing the
execution
Advancement
of temporary
spending plan
for the task
Choosing of
proper plan
and
procedures
required for
the venture
Up-gradation
of different
obstacles to
finish the
undertaking
project.
Proper
utilization of
different
undertaking
administration
standards as
well as
operational
techniques
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

19
ICT PROJECT MANAGEMENT
Likely Absence of
Design
Methodology
System
Failure
Almost Certain Delay in
completion
Part 5: Quality Management Plan
The quality management plan of RALS Roistering project mainly includes the below
mentioned stages:
Stage 1: Identification of different quality issues
Stage 2: Analysis of different quality issues and their impacts
Stage 3: Development of different improvement techniques
Stage 4: Monitoring of different actualized techniques
Stage 5: Review of arrangements
Part 6: Project Closure
a. Annotated Bibliography
Various researchers Amrollahi, Ghapanchi and Talaei-Khoei (2014) discussed about the task
administration process that mainly produced with the help of different vital administrative
strategies. Different procedures and techniques are mainly created for doing the task

20
ICT PROJECT MANAGEMENT
administration that become useful to co-ordinate advancement of different enhanced
techniques and processes in the association.
Apart from that, other researchers Galliers & Leidner (2014) highlighted about the key
administration to confront different issues to deal with venture in effective manner due to
loose of data handling as well as proper improvements. It mainly required for doing the
advancements of different innovation and various creation to adjust the venture capacities.
Hence, after doing the research Stark (2015) discussed about the item life cycle
administration that are suggested to build up different operations of venture. It becomes
conceivable for the utilization of different administrative standards that helps to cover up the
real effects of framework improvement models.
b. Checklist for RALS project
Checklist Item Checked
Progression of Project Plan 
Enhanced Resource Allocation Plan 
Closing down of all project documents 
Feasible System Design 
Synchronized usage design 
Expected Test Results 
C. Evaluation Criteria
1. Project Plan as well as Resource Allocation Plan

21
ICT PROJECT MANAGEMENT
2. All types of project documentations
3. Scope Verification Plan
4. System Design and Implementation Plan
5. Test Results

22
ICT PROJECT MANAGEMENT
Bibliography
Amrollahi, A., Ghapanchi, A. H., &Talaei-Khoei, A. (2014). Three decades of research on
strategic information system plan development.Communications of the Association
for Information Systems, 34(1), 84.
Braglia, M., &Frosolini, M. (2014).An integrated approach to implement project management
information systems within the extended enterprise.International Journal of Project
Management, 32(1), 18-29.
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management.
Cengage Learning.
Galliers, R. D., &Leidner, D. E. (2014). Strategic information management: challenges and
strategies in managing information systems. Routledge.
Garton, C., & McCulloch, E. (2012). Fundamentals of Technology Project Management. MC
Press, LLC.
Goetsch, D. L., & Davis, S. B. (2014). Quality management for organizational
excellence.pearson.
Hubicki, M. (2014). Risk Management Plan.
Kendrick, T. (2015). Identifying and managing project risk: essential tools for failure-
proofing your project. AMACOM Div American Mgmt Assn.
Nanda, V. (2016). Quality management system handbook for product development
companies.CRC Press.
Pritchard, C. L., & PMP, P. R. (2014). Risk management: concepts and guidance. CRC Press.
Schwalbe, K. (2015). Information technology project management.Cengage Learning.
Stark, J. (2015). Product lifecycle management.In Product Lifecycle Management (pp. 1-
29).Springer International Publishing.
Verburg, R. M., Bosch-Sijtsema, P., &Vartiainen, M. (2013).Getting it done: Critical success
factors for project managers in virtual work settings.International Journal of Project
Management, 31(1), 68-79.