ITC505

This document outlines the Charter for Assessment-3 of the ICT Project Management course. It covers areas such as the MOV, Scope, Work Breakdown Structure, Project Risk Analysis and Plan, Quality Management Plan, and Closure and Evaluation steps.

ITC505
ICT Project Management
Assessment-3
Charter
Student Name:
Student ID:

Contents
Part one: MOV.................................................................................................................................3
Part Two: Scope...............................................................................................................................6
Part Three: Work Breakdown Structure........................................................................................10
Part Four: Project Risk Analysis and Plan.....................................................................................12
Part Five: Quality Management Plan.............................................................................................17
Part Six: Closure and Evaluation step...........................................................................................19
References......................................................................................................................................22
List of Figures
Figure 1- WBS...............................................................................................................................10
Figure 2: Gantt Chart.....................................................................................................................11
List of Tables
Table 1- Area of Impact...................................................................................................................3
Table 2- Stakeholders Expectation..................................................................................................4
Table 3- Timeframe developed for MOV........................................................................................5
Table 4- Out scope items.................................................................................................................6
Table 5- In scope items....................................................................................................................6
Table 6- Description of participant work.........................................................................................8
Table 7-Project Risks.....................................................................................................................12
Table 8- Risk assigned to members...............................................................................................16
Table 9- Evaluation of project.......................................................................................................20
Table 10- Reviews of managers of Globex...................................................................................21

Part one: MOV
Area of impact
According to their ranking area of impact is been displayed.
Table 1- Area of Impact
Financial Customer Strategy Social Operational
This system
restricts people
from entering
RALS if they
don’t have the
tickets with
them.
This system
allows the
customers or
users to easily
and quickly
book tickets
from anywhere
in the world.
As RALS and
Globex will not
be shifting
towards a new
market making
strategic field of
least priority.
This system is
very attractive
and gathers
user’s attention
which increases
its social
impression.
Chances of
occurring error
are less as this
system is
completely
automatic. This
system also
helps in
managing
crowd easily.
Types of values:
 Faster: RALS is presently facing issues in dealing with crowds. They desire a system
which can help easily in managing and dealing with the crowd. This system provides
online ticket generation through which users can book tickets online by sitting anywhere
and eliminating those big queues. This process is much faster and quicker and is less
hectic.
 Better: Due to this system of booking tickets online, it makes the process automatic that
helps in managing the whole crowd and can easily operate them. The system provides the
opportunity to book tickets directly from sitting anywhere in the world.
 Cheaper: This system helps in reducing the cost of labors or employees involved as this
is completed computer-based system.
Appropriate metric:
Targets
To implement the online booking system for tickets few things are commonly targeted which are
listed as:

 Tickets are equipped with a barcode.
 Tickets are purchased through online systems.
 Categorization of tickets on a day basis.
 Details like outlet, offline/online purchase and gate number are described in tickets.
Stakeholders Expectation
Table 2- Stakeholders Expectation
List of Stakeholders Stakeholders Expectation
System analyst Issues faced must be presented in detail manner.
Project manager Coordination between Globex and RALS organisation must be
positive.
Web developer Resources must be made available when needed.
Computer technician RALS committee corporates properly.
System architect Resources are available in given time.
Business analyst They need to properly communicate with Globex organisation and
RALS committee.
Globex corporation They can also access the generated revenue.
Visitors They buy tickets from an online system of booking.
RALS committee During the peak time also crowd can be managed (Crump, 2015).
Target that is quantitative
 They expect 83% of the increase in profit earned within 6 months.
 The expectation of customer retention increment by 90%.
 They can easily control 90% of the coming crowd.
 It can maximize the interest return up to 8.9% within 5 months.

Timeframe developed for MOV
Table 3- Timeframe developed for MOV
S. No. Task Name Task
Duration
1 Conceptualization and Initialization of online booking
system of tickets.
6 days
2 RALS presentation 2 days
3 Control and executes plans for generation system of
online booking system.
5 days
4 Online booking system of tickets is implemented. 11 days
5 Online booking system for tickets is installed. 5 days
6 Training of RALS staff regarding the online ticket
booking system.
1 day
7 Project closure 1 day
8 Online ticket booking system evaluation 1 day
9 Total 32 days
MOV Summary
The system of online booking of tickets used to help Globex organization and RALS committee.
From this system, customers can purchase tickets online providing them with a platform for
easily booking tickets. This system can be accessed through user handy devices like mobile,
tablets and notebooks. Tickets can be printed by visitors that have a barcode on it.
This system allows the RALS committee to track the whole crowd so as to manage them. This
system reduces the threat of cheats as through this only that person can access inside which holds
proper tickets. It even allows Globex track easily the revenue record created by the crowd
(Fisher, 2018).

Part Two: Scope
Scope
RALS community is presently facing issues in controlling the crowd. Most of the crowd is
getting away from the gate of the entrance as the revenue result is not properly generated and
because of this RALS gates are dealing with delays. As a result of this, the process of sale has a
slowdown in RALS due to long and waiting queue. To overcome such issues RALS decided to
come up with a new and user-friendly platform for booking tickets.
The system generated provides few functions as well as features that are listed below:
 This system generates tickets along with QR codes or barcodes printed on them and they
are quickly and easily generated.
 Visitors can online register tickets making it user-friendly.
 Through the internet, visitors can easily purchase the tickets from anywhere in the world.
 This system is developed in a way that it can be easily accessed through any devices like
mobiles or tablets.
Out scope and In scope items
Out scope items
Table 4- Out scope items
S. No. Name of Item
1 NFC enabled
cards
2 Database
3 NFC reader
In scope items
Table 5- In scope items
Deliverables
Things which RALS will deliver are listed below:
 Cases developed for business
S. No. Name of
Item
1 QR code
reader
2 Barcode
reader
3 Mobiles
4 Printers
5 Computers
6 Laptops

 Plan developed for budget
 Plans for management of project
 Work breakdown structure
 Project schedules
 Project milestones
 Responsibilities and roles
 Plans created for development of system
 System user documentation
 Test plans (Parvez, 2013).
Criteria for acceptance
Some criteria need to be fulfilled by Globex and RALS organization to accept this system of
generating or booking tickets online. Some acceptance criterion is described below:
 The system must able to be accessed by user-friendly devices like mobiles, notebooks,
and tablets.
 The system should be easily operated online.
 This system must help the user to generate and book tickets online in an easy and simple
way.
 Revenue must be accessed easily by both Globex as well as RALS committee.
Resources List
Resources which are required to make applications for booking online tickets are given below:
 Peoples or participants involved: To develop the system of booking tickets online some
qualified persons are required which will help in developing the system at lower cost and
taking less time or within provided time. To complete or finish the project successfully
some persons like system analyst, business analyst, computer technicians and project
managers are needed for the creation of the project. The list of such peoples are provided
below:
Table 6- Description of participant work
S. No. Participants Description of their work
1 Web They are programmers who build an application for this

Developer system and through them, visitors can directly access
system very easily and they even create accessibility of
system with portable devices like tablets, mobiles, and
notebook.
2 System
Analyst
They help in providing or utilising the technology
efficiently and effectively. By performing cost analysis
system can be made incorporated into any organisation.
3 Project
Manager
They play a very crucial role from planning to execution
as they are simply responding to lead and guide the
project. They perform various steps that comprise of
planning, managing, and execution in a proper way.
4 Business
Analyst
Their responsibility is to analyse business domain for the
betterment of organisation. They even integrate different
business model having new technologies just by
accessing it.
5 Computer
Technician
They maintain and control all computers and servers
installed and provided by Virtucon and they even
configure newly placed hardware and update some
software packages.
6 System
Architecture
They develop or create a system for an organisation so
that all requirements of an organisation can be easily
fulfilled. The design system after dividing it into several
small pieces (Sun, 2018).
 Technology: Various tools and technologies are used while developing the system. These
techniques can help build a system of online booking tickets which simplifies the life of
visitors of RALS. Tools used for creating the system efficiently and on time are
computers, notepad++, printers, mobiles, tablets and Studio Cloud Software.
 Facilities: Many facilities need to be provided by online booking system of tickets and to
make it run smoothly they must have better linking between all software and hardware.
Some hardware parts are installed in RALS premises.
 Other: Resources like training is needed to be provided by Virtucon to staff members.
Some computer technicians are hired to train RALS staff members regarding the working
of the new system. This training helps the staff members to effectively operate the whole
system and eliminates the cause of developing human errors.

Part Three: Work Breakdown Structure
Figure 1- WBS

Figure 2: Gantt Chart

Part Four: Project Risk Analysis and Plan
Assumptions regarding the project
During the construction of project different assumptions are made which are listed below:
 The information gathered from Globex need to be right or correct.
 RALS staff members must have the knowledge of basic computers which will help them
operate the online booking system in an easier way.
 At testing time, minimum 2 stakeholders need to be present just to verify that the
requirements of RALS organization are fulfilled or met properly.
Project Risks
Risks can be classified in five possible ways:
Table 7-Project Risks
Ranks of
Risk
Name of Risk Risk Description
1 Schedule Risk This risk occurs when project task is not addressed
properly, leading to the risk of schedule slipping.
Schedule slipping affects Globex organisations
economy and it might even lead to project failure.
2 Requirement Related
Risk
This risk occurs due to the continuous change taking
place in the project. If requirements are not properly
defined it may lead to many issues related to project or
its failure.
3 Risk of Project
management
This risk occurs commonly because of priority change
in the present system. Sometimes same resources are
required in the given project and such things are
capable enough to stop project progress.
4 Technology Related Risk This risk occurs commonly due to functionality and
performance of project but this risk only affects if
project implementation goes hard.
5 Customer Related Risk The customer always comes up with demands of new
and updated things with which they can make their life
easy and this is the reason their decision cycle is slow
enough. They even don’t accept the system until all
their needs are being fulfilled.

Risk Analysis
 No: R44
Rank: 1
Risk: Scheduling is not proper
Details: Task schedule is completely disturbed because of no knowledge regarding newly
added functionality continuously in online ticket booking system.
Classification: Schedule
Root Cause: No access to proper information regarding the newly developed functions
required in the system of online booking tickets.
Effects: If the generated schedule is not updated when the project may result in slip from its
predictable dates.
Responses to Risk: To reduce the task overlapping business analyst have to schedule some
task and they must be updated regularly.
Owner of Risk: Project Manager
Probability and Impact: High
Status of Risk: Every week project manager needs to conduct meeting with its members.
 No: R45
Rank: 2
Risk: Requirement of Resources
Details: Due to lack of resources present, online booking of tickets can lead to delay in time
and will not be completed on time.
Classification: Risk related to requirements
Root Cause: The same type of resources is used by many organisations leading to decreases
in its availability.
Effects: According to the system architecture analysis shortage of resources directly affects
the project processes.

Responses to Risk: System Analyst plans all project related requirement in a systematic way.
It presented all resource requirements at the time of project completion.
Owner of Risk: System Analyst
Probability and Impact: High
Status of Risk: Meeting needs to be conducted with the whole team and project manager.
 No: R46
Rank: 3
Risk: Priority gets change regularly
Details: The priorities are getting changed regularly as the functionality of the online booking
tickets system is continuously increasing.
Classification: Risk relates to Project Management
Root Cause: These sudden occurring changes in the priority can lead to disturbance of the
project management.
Effects: Business analyst encounters that the project management is not going in a better way
and the priorities are getting changed very fast.
Responses to Risk: To acknowledge the project related processes and all recent updates
included in projects business analyst need to organize a various meeting of members so as to
ensure project completion within the allotted time. It also manages the hurdles faced by the
member at the time of completion.
Owner of Risk: Project Manager
Probability and Impact: Medium
Status of Risk: The changes which occurred in the system are finalized by the project
manager.
 No: R47
Rank: 4
Risk: Technology selection
Details: Due to continuously increase in functionality of online booking of tickets system this
hinders the system completely.

Classification: Risk of technology
Root Cause: Fulfillment of demands of users cannot be done by these provided technologies
as they are not enough to satisfy their needs related to the online booking system.
Effects: System analyst and architect encounter the risk occurring in performing the task on
given technology.
Responses of Risk: Some modifications need to be done by system analyst and architect in
the current technologies to complete the given project in required time.
Owner of Risk: System Architect
Probability and Impact: High
Status of Risk: A meeting will be conducted by System Architect with project manager
regarding the modification made in the technology used in online booking system of tickets.
 No: R48
Rank: 5
Risk: Visitors
Details: The system can’t satisfy the users of online booking ticket system as it creates
difficulties for them to understand system’s user interface.
Classification: Risk related to Customer
Root Cause: The requirements and needs of the user are not clearly achieved including the
basic knowledge of this system.
Effects: Proper information is not provided to the visitors regarding the booking system like
the location where they can book tickets.
Responses of Risk: Project manager knows the whole about the system and manages the
members by coordinating with them, listening to their problems and resolving them.
Owner of Risk: Project Manager
Probability: Low
Impact: High
Status: Issues are discussed by project managers with system analyst to resolve the task
easily (Watt, 2018).

Risk is assigned to different members
Table 8- Risk assigned to members
S.
No.
Risk name Member Name
1 Schedule Risk Member 3
2 Risk Related Requirement Member 1
3 Risk related to Project
management
Member 4
4 Technology related risk Member 2
5 Customer-related Risk Member 3

Part Five: Quality Management Plan
Statement for Team’s objective
The aim of my team is to establish a quality based system to meet all requirements of RALS
organization in a systematic way. For achieving this all members of team coordinated very well
with both Virtucon and Globex organization. To smoothen the work it is distributed between
various members of the team so that the work gets completed in minimum time and lesser
efforts.
During the creation of this system for RALS organization various meeting are organized between
Globex and RALS staff members. In such meeting, problems are discussed regarding the
managing of the crowd by RALS committee. After these discussions related to problems, some
MOV and action plans are generated. Later these things are presented and demonstrated among
RALS committee and once it gets approval the work related to the project gets started. Cost of all
resources are taken and also demanded for approval. The system is developed with Virtucon
having proper coordination with them. When the creation is completed the system is tested so
satisfy RALS or Globex Committee. When the system is tested properly it finally gets
implemented within the Globex premises by taking their permission. Finally, the online booking
of tickets system is created and it fulfills all the needs of the organisation.
Validations
It majorly includes the methods of controlling the quality of the system. Validation includes the
activities that are project associated. This helps to ensure whether the developed system is
fulfilling the requirements or needs of the client or not. Online booking of ticket system is
examined on the basis of workers reliability, compatibility and capacity of the user. Few steps
involved in rules of validation:
 Unit testing: In this test, the online booking of ticket system is checked whether it is working
properly or not and if they are meeting all the needs of RALS committee.
 Integration testing: In this test online booking of ticket system is checked whether the system
is working, in the same way, it is required to work or within the guidelines, it needs to work.

 System Acceptance: In this phase, a checklist is made consisting all approved and completed
validations and it assures that the system is working with its best potential. If it clears the
test, it gets accepted by both RALS and Globex organisation.
 User approval: In this test online booking of ticket system is checked whether the system is
meeting the requirements or needs of users or not. It only gets confirmed when all needs of
users are met or fulfilled (Softwaretestinghelp, 2017).
Verifications
Various activities are performed and some out of them need organisation verification. The whole
verification process must confirm the acceptance of the organisation regarding the following
project. By proper discussions and meetings all project related things are completed. When
completion takes place the process finally goes for verification which includes three major steps:
 Technical review: In this phase, all technical parts of an online booking of ticket system are
verified. It assures that all requirements of the organisation are met or fulfilled within the
allotted time and met the organisation standards.
 Business reviews: After verification is performed depending on functionality and scope of
the project, testing of the project takes place mainly for the purpose it is intended. This step
ensures the project will meet some business reviews also.
 Managerial reviews: They met all requirements of managers of RALS and Globex
organisation. All manager related needs are met by this system (software testing class, 2013).

Part Six: Closure and Evaluation step
Annotated Bibliography
Bibliography 1
Law, R., & Leung, R. (2000). A study of airlines’ online reservation services on the Internet.
Journal of Travel Research, 39(2), 202-211.
In this journal, author discusses online reservation services and factors affecting the time for
using online reservation services. The author explains the additional benefits it provides to the
users and the efficiency of evaluating attributes. It explains the methodologies are chosen and
findings. The author explains the extra benefits granted to users of internet and information of
ordering online. It also explains the factors that affect the time and additional facilities provided
on web sites. It provides the discussion and future research.
Bibliography 2
Maymounkov, P., & Mazieres, D. (2002, March). Kademlia: A peer-to-peer information system
based on the xor metric. In International Workshop on Peer-to-Peer Systems (pp. 53-65).
Springer, Berlin, Heidelberg.
In this journal, author discusses about the outsourcing and offshoring of risks and the investment
of imitation and international experiences of risk management. It also explains the data, research
methods and findings and even variables that are dependent and explanatory along with control
variables. It later discusses implications, limitations and future research of risks.
Bibliography 3
Slovic, P., Finucane, M. L., Peters, E., & Macgregor, D. G. Risk as analysis and risk as feelings:
some thoughts about affect, reason, risk, and rationality. Risk Anal 2004; 24: 311–22.
In this journal, author discusses the risk analysis and risk as feelings. They explain the important
effects of system and compares experiential and analytic systems. The author explains the
benefits and risks of judgments. It explains the probability and its insensitivity and judgments. It
provides with experiential system failures and how risks can be managed. It explains how risk
analysis can benefit experiential thinkings and the threats caused by risks.

Closure checklist
 The procedure of closure begins when it is ensured that all stakeholder requirements are
met completely.
 To validate and verify the project process with proper meetings with stakeholders.
 All documentation and deliverables are acquired in a proper way.
 The RALS committee handles all system related technical documentation.
 After system implementation, it needs to be regularly maintained at a regular time
interval of time.
Evaluation of project
Analysis of performances of each member of team
Table 9- Evaluation of project
S. No. Member of
Team
Rating or Reviews
1 Member 1 Management- Good
Contribution- Moderate
Performance- Excellent
Coordination- Good
2 Member 2 Management- Good
Contribution- Moderate
Performance- Excellent
Coordination- Good
3 Member 3 Management- Good
Contribution- Moderate
Performance- Excellent
Coordination- Good
4 Member 4 Management- Good
Contribution- Moderate
Performance- Excellent
Coordination- Good

Reviews of managers of Globex
Table 10- Reviews of managers of Globex
S. No. Factors
Involved
Ratings (out of 10)
1 Schedule 8
2 Delivery 7.5
3 Objectives 9
4 Cost 8
Evaluation of success of project- MOV
Initially, MOV of the project is defined to generate results after 3, 9 and 16 months after the
system is installed in Globex premises. After few months this system of online booking of tickets
will gain the user’s attention and will attract a crowd. After 16 months of implementation, user
receives returns. After project completion, Globex and RALS organisation managers test the
system and judge that the needs are accomplished or not. These systems are accepted only when
requirements are met.

References
 Crump, K. (2015). How to Manage Stakeholder Expectations. Retrieved from
https://www.liquidplanner.com/blog/project-management-challenge-series-manage-
stakeholder-expectations/
 Fisher, T., (2018). What's an MOV File and How Do You Open One. Retrieved from
https://www.lifewire.com/what-is-an-mov-file-2622779
 Law, R., & Leung, R. (2000). A study of airlines’ online reservation services on the Internet.
Journal of Travel Research, 39(2), 202-211.
 Maymounkov, P., & Mazieres, D. (2002, March). Kademlia: A peer-to-peer information
system based on the xor metric. In International Workshop on Peer-to-Peer Systems (pp. 53-
65). Springer, Berlin, Heidelberg.
 Parvez. (2013). Scope Definition of Online Ticketing System. Retrieved from
https://www.slideshare.net/ShahriarPrince/scope-definition-of-online-ticketing-system
 Sites, (2018). Chapter 2- Objective of the Project - Bus Ticket booking system - ONLINE
BUS TICKET BOOKING SYSTEM PROJECT SYNOPSIS AND FINAL REPORT.
Retrieved from https://sites.google.com/site/onlineticketbookingmcabca/objective-of-the-
project
 Slovic, P., Finucane, M. L., Peters, E., & Macgregor, D. G. Risk as analysis and risk as
feelings: some thoughts about affect, reason, risk, and rationality. Risk Anal 2004; 24: 311–
22.
 Software Testing Class. (2013) Difference between Verification and Validation. Retrieved
from http://www.softwaretestingclass.com/difference-between-verification-and-validation/
 Softwaretestinghelp. (2017). What is Verification and Validation? Retrieved from
http://www.softwaretestinghelp.com/what-is-verification-and-validation/
 Sun, L., (2018). The Role of Stakeholders in Your Business. Retrieved from
http://www.businessdictionary.com/article/601/the-role-of-stakeholders-in-your-business/
 Watt, A., (2018). Risk Management Planning Project Management. Opentextbc. Retrieved
from https://opentextbc.ca/projectmanagement/chapter/chapter-16-risk-management-
planning-project-management