ITC505 ICT Project Management: Project Charter Value - Assessment

This ITC505 ICT Project Management assessment outlines the development of an automatic ticket generation system for RALS (presumably an organization). The project charter value is assessed across customer, social, financial, operational, and strategic impact areas. Stakeholder expectations are defined, and quantitative targets for profitability, expenditure reduction, sign-in efficiency, and instructor value are established. The project scope includes mobile, desktop, printers, barcode readers, and database integration, while excluding NFC readers. The project risk analysis identifies potential risks related to project management, technology, timelines, resources, and communication. A quality management plan and project closure and evaluation steps are also discussed. The student solution is available on Desklib, a platform offering a wide array of study resources, including past papers and solved assignments.

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

Student Name: Student ID:
Contents
Part One: MOV..........................................................................................................................3
Part Two: Scope.........................................................................................................................6
Part Three: MS project Implementation.....................................................................................7
Part Four: Project Risk Analysis and Plan.................................................................................8
Part Five: Quality Management Plan.......................................................................................12
Part Six: Closure and Evaluation step......................................................................................13
References................................................................................................................................15
List of Figures
Figure 1- Timeframe..................................................................................................................5
List of Tables
Table 1- Area of Impact.............................................................................................................3
Table 2- Expectation of stakeholders.........................................................................................4
Table 3- Scope of Project...........................................................................................................6
Table 4- Stakeholder description...............................................................................................6
Table 5: Project risk...................................................................................................................8
Table 6: Risk assigning............................................................................................................11
Table 7- Review from RALS committee................................................................................14

Student Name: Student ID:
Part One: MOV
Area of impact
Area of impact shown below is categorised by its importance ranking for RALS. While
making this table all the services are kept in mind through which RALS can be benefited.
Table 1- Area of Impact
Customer Social Financial Operational Strategy
Exhibitor can
easily book
their tickets
form the
automatic ticket
generation
system without
standing in a
large queue.
Through this
automatic ticket
generation
system, there is
going to be
growth in the
exhibitors as
they can
purchase the
tickets without
any hassle. This
thing is going to
benefit the
RALS.
Financial
aspects play an
important role
in staying inside
the business.
For that, the
system is going
to be designed
in such a
manner so that
it will help the
RALS in a
positive
manner.
As currently all
the tickets are
sold manually
therefore by
implementing
the automatic
ticket
generation
system the load
from the
committee
members of the
RALS can be
reduced.
As RALS has
no plans to
enter the new
market,
therefore, it has
no focus on the
strategic area of
impact.
Value
Through this automatic ticket generating system following value is going to be delivered to
the RALS which are shown below:
 Better: The committee members of the RALS are going to be relaxed after
implementing this automatic ticket generating system. Through this automatic ticket
generating system, the RALS committee can easily monitor the exhibitor who came to
visit the exhibition. Also, they can easily track the exhibitor mode of payment through
this automatic ticket generating system.
 Faster: Through this automatic ticket generating system the efficiency is going to be
increased. As the system is going to generate the tickets in a digital manner so the
error in printing and allocating the tickets is going to be reduced. As the tickets can be
bought from the online or mobile platform and are going to accept all format of
money transaction, the sales of tickets are going to be increased.
Metric
The main objective of delivering the automatic ticket generating system is that through this
system the overall efficiency of the RALS can be enhanced. Through this automatic ticket
generating system, the reputation of the RALS in the community is going to be increased.
After the implementation of the automatic ticket generating system, the use of paper is going
to be phased out. also, the expenditures of the RALS is going to be decreased and all the
transaction is going to be in the paperless system in an eventual manner. certain metric points
can be achieved which are shown below:

Student Name: Student ID:
 Targets
This automatic ticket generating system is designed for the exhibitors and the
committee members of the RALS. For that the system is going to be furnished with
the barcode reader so that the system can read and verify the tickets easily.
 Expectation of stakeholders
There are diverse stakeholders that are present in this online ticket generation system.
List of the stakeholders are shown below:
Table 2- Expectation of stakeholders
Stakeholder
name
Expectations
Exhibitors They can purchase the tickets from any corner of the world
easily.
Project manager In the meetings conducted by the project manager, there must
be presence of the committee members of RALS.
Product manager All the products from RALS have to be given in proper format.
Software
Engineer
All the software requirements have to be given via proper
channel.
Software tester During the time of testing the committee members of the
RALS has to be present.
Software
Architect
All the prerequisite of the program has to be made available to
the software architect by the RALS committee member.
Solution Architect All the solution of the solution architect has to be approved by
the RALS team in allocated time.
UI designer The design made by the UI designer has to be analysed by the
RALS committee.
 Quantitative targets
o Profitability of the RALS is going to be increased by 80% after installation of this
system.
o All the expenditure that is associated with the resources is going to be reduced by
50%.
o Sign in efficiency is going to increase by 95%.
o Instructors value is going to be reduced by the 59%.
MOV timeframe
Timeframe of the MOV is shown below:

Student Name: Student ID:
Figure 1- Timeframe
Summary of MOV
The decision of the project has to be done on the after the effect of the verifiable measurable
organisation values. Adoption of new features inside the project can be done if the value of
the MOV is going to be increased. Through this, the project can be analysed on the basis of
the business value (Nordmeyer, 2017). Through this project, the exhibitor can easily book the
tickets from anywhere in the world. This will reduce the load of the committee members who
are responsible for booking of tickets. Also through this system, an automated report can be
generated in which the exhibitor information can be displayed easily.

Student Name: Student ID:
Part Two: Scope
Scope
By taking the help of the project scope list of the project deliverable, tasks, functions, costs
and deadline of the automatic ticket generating system can be identified easily. The main goal
of the system is to provide the ease to RALS committee (Gotto, 2013). This can be done by
creating the automatic ticket generating system. Through this system, the tickets can be
generated in an automatic and digital manner. Also, the system has to be designed in such a
manner so that exhibitors can access the system through there mobiles, desktop and laptops.
Also, the system has to be capable enough so that the exhibitor can purchase the tickets from
any corner of the world. All the tickets have to be equipped with the barcode so that it can be
checked against fake tickets.
All the objectives of the project are going to be carried out by different stakeholders of the
project. Management of the project is shown below:
Table 3- Scope of Project
Project
Planning
The planning of the project is going to be done by taking the help of
the project manager.
Scope
definition
The definition of the project scope can be done by taking the help of
project charter.
Project
Validation
Validation of the project is going to be implemented by taking the help of
the RALS committee members.
Project
monitor
Monitoring of the project is going to take place by the software engineer
and software tester.
Project
Control
Controlling of the project is also going to be done by taking the help of the
project manager and product manager (Westland, 2016).
In scope item and out scope items that are needed inside the projects are shown below:
 In scope Items:
o Mobile
o Desktop
o Printers
o Barcode reader
o Database
 Out scope Items:
o NFC reader
The resources that are needed inside the project is shown below:
People
Table 4- Stakeholder description
# Stakeholder
name
Description
1 Project manager Main duty of the project manager is to lead the project from start
to the execution stage. also he is going to manage the scope,
resources and people that are associated with the RALS project
(Alexander, 2017).

Student Name: Student ID:
2 Product manager The main duty of the product manager is to define the roadmap,
strategy and feature of the product (Tworetzky, 2016).
3 Software Engineer The main objective of this person is to maintain, design, testing
and evaluation of the software in an easy manner (Harper, 2011).
4 Software tester The main objective of the software tester is to find the bugs that
are present in the software. The testing of the bug is going to be
an iterative process (Lindros, 2017).
5 Software Architect The main role of this person is to define the technical standards
which include the coding standards, platforms and tools (Orin,
2015).
6 Solution Architect The main objective of this person is to translate the requirements
that are created by the functional analyst (Hahladakis, 2011).
7 UI designer The main objective of the User Interface is to design the interface
of the online ticket generating system (Norman, 2014).
8 UX designer The main role of this person is to improve the accessibility,
usability and pleasure of the application of the automatic ticket
generating system (Ming, 2014).
9 Technical Writer The main role of this person is to create the journal articles and
prepare instruction manual for the automatic ticket generating
system (DuPuis, 2017).
Technology
In making the system for the RALS I am going to take the help of the SQL for creating the
database. This database is going to be on the backend server. All the GUI of the system is
going to be implemented by taking the help of the Java Development Kit. As there is the need
for the system that is going to be run on the mobile platform, therefore, the system is built on
Android SDK and Xcode. The website of the automatic ticket generation system is going to
be built on the CSS. For that, the code is going to be written on the notepad++.
Facilities
Different types of facilities that are going to be provided to the users are as follow:
 All the linking of the hardware and software has to be done in proper manner.
 The tickets are going to be made available in the pdf format so that consumption of
the paper can be reduced.
Other
Training to the committee member is going to be done after the installation of the automatic
ticket generation system. All these training services are going to be done by taking the help
of the Virtucon (Bambao, 2016).
Part Three: MS project Implementation

Student Name: Student ID:
Part Four: Project Risk Analysis and Plan
Assumptions made inside the project
While creating the automatic ticket generation system different assumptions are made so that
the project can be completed in a proper manner. Different assumptions that I made the
project is shown below:
 All the case history of the RALS that their committee member handover to the
Virtucon has to be true.
 The operator of the system must have basic knowledge of operating and the
application inside the computer system.
 There must be presence of at least one RALS committee member during the testing of
the system.
 There must be complete presence of RALS member when training to them is given.
Project risk
In making of this automatic ticket generating system, there is going to be presence of five
risks which is described by taking the help of the table.
Table 5: Project risk
Ran
k
Name of the
Risk
Description
1 Risk associated
with project
management
Designing of the system includes different type of resources.
And all these resources have to be set according to the
priorities that are needed inside the system.
2 Risk associated
with technology
As this project is built to perform several functionalities to help
the exhibitors and the committee members of the RALS. But
due to some problems, there may be a chance that the
performance of the system may be reduced (Rawi, 2013).
3 Risk associated
with timeline
If the allocation of the job is not done in an appropriate
manner, then there may be a chance of the slippage of the
timeline. This will result in the delay of the project.
4 Risk associated
with requirement
As inside the project, there is the continuous need for
improvements. Therefore, the requirements are going to change
from day to day. So there is the need of synchronisation in
maintaining the requirement.
5 Risk associated
with customer
As the technology is evolving on daily basis, therefore, the
need of the customers regarding the technology is going to be
increased. So to meet the requirement of the customer there is
the need for continuous evolution of the project
(Softwaretestinghelp, 2017).
Risk analysis
 No.: AT15
Rank: 1
Risk: Improper timeline

Student Name: Student ID:
Description: This type of project requires different functionalities to complete the task.
Through these functionalities, all the requirement of the RALS can be completed easily.
Category: Schedule
Root cause: Different technology require some extra days to complete the task.
Triggers: This thing triggers the product manager to manage the timeline.
Risk responses: Product manager has to schedule the tasks by allocating some extra time.
Through this, in case of slippage of task, the timeline can be adjusted.
Risk Owner: Product Manager
Probability: Very High
Impact: High
Status: There is going to be meeting with the team members conducted by product
manager.
 No.: AT23
Rank: 2
Risk: Requirement of resources
Description: Due to unavailability or shortage of resources the project can’t meet the
deadline easily.
Category: Risk requirement
Root cause: As the resources are unavailable at the production end of the project,
therefore, the project can’t be completed easily.
Triggers: Software architect
Risk responses: All the scheduling of the task has to be done in such a manner so that the
starting of that task has to be done after having ample amount of resources.
Risk Owner: Software Architect
Probability: High
Impact: High
Status: Software architect is going to conduct conference with the software engineer.
 No.: AT38
Rank: 3
Risk: Priorities
Description: As there are limited amount of resources are available therefore the work is
going to be hindered.
Category: Project management Risk

Student Name: Student ID:
Root cause: As the resource allocation is not done in a proper manner, therefore, the
priorities are going to be disturbed.
Triggers: Due to unavailability of the resources the next task can’t be completed. As a
result, the progress of the project may be stopped.
Risk responses: The allocation of the resources has to be done according to the priorities.
Also, all the resource allocation has to be done in such a manner so that all the resources
are made available easily.
Risk Owner: Project Manager
Probability: Moderate
Impact: High
Status: Project manager is going to deportment conference with the product manager and
the system architect.
 No.: AT43
Rank: 4
Risk: Technology selection
Description: To meet the requirement of the RALS proper technology has to be selected.
If work has been started on wrong technology, then it may lead to waste of efforts.
Category: Technology risk
Root cause: As to fulfil the requirement of RALS some technology has to be merged with
each other. If the merging of these technology has not done in a proper manner, then the
system can’t work in proper manner.
Triggers: UX Designer and Software engineer
Risk responses: The work has to be done in a synchronised manner so that different
technology can be embedded inside each other.
Risk Owner: UX Designer and Software engineer
Probability: Medium
Impact: High
Status: UX Designer and Software engineer are going to conduct the meeting.
 No.: AT50
Rank: 5
Risk: New Exhibitors
Description: Some new visitors may have less knowledge regarding the use of the new
application.
Category: Customers risk

Student Name: Student ID:
Root cause: If the survey of the exhibitor knowledge regarding the system knowledge is
not done in proper manner then it may result in a great problem.
Triggers: If the exhibitors are unable to access the system then the prime functionalities
of the project can’t be met in a proper manner.
Risk responses: All the design has to be analysed and implemented in a proper manner so
that exhibitors can access the system in a proper manner.
Risk Owner: UX and UI designer
Probability: Low
Impact: High
Status: UX and UI designer is going to conduct meeting with project manager to
overcome the problem.
Risk assigning
Table 6: Risk assigning
# Risk category Member name
1 Requirement Risk Software Architect
2 Schedule Product Manager
3 Customer Risk UX and UI designer
4 Technology risk UX Designer and
Software engineer
5 Project management Risk Project Manager

Student Name: Student ID:
Part Five: Quality Management Plan
Team philosophy
Development of the automatic ticket generating system is done by taking the help of
appropriate teamwork. For that the coordination in between the Virtucon and Globex.
Different functionality inside the automatic ticket generating system is done by taking the
help of the creative thinking. For that different brainstorming session is conducted by the
members of the Virtucon. All the project managers and product managers play an important
role in managing the task. All the execution of the task is done in proper manner. This project
is going to be helpful in long-term. Different facilities are added inside the automatic ticket
generating system through which future problem can be solved easily (Kraft, 2015).
Set of verification activities
In completion of the automatic ticket generation system, different functionalities of the RALS
are completed. These functionalities are going to be used by the exhibitors and different
committee members of RALS. So for that verification activities are done by taking the help
of reviews which is shown below:
 Managerial review: In this, all the requirements of the committee members of the
RALS are reviewed. Through this review, the functionalities that are going to be used
by the RALS can be analysed easily.
 Technical review: In this, all the technical requirements are analysed by both
committee members and exhibitors of RALS. Through this review, it can be ensured
that all the technical parts of the report are covered in a proper manner.
Set of validation activities
 Unit testing
In this type of testing the whole system is going to be taken as a single unit and all the
functionalities are tested. Through this testing step, it can be ensured that all the
requirements and functionalities of the RALS are satisfied in a proper manner.
 Integration testing
In this, all the integrated services that are inserted into the automatic ticket generation
system are tested.
 System acceptance
In this type of testing all the activities related to the validations are tested and
approved. To test such things, the system is going to be run on the full potential.
 User acceptance
In this type of testing all the requirements of the exhibitors are tested. This test is done
by taking the help of the feedback from user. Through this, it can be ensured that all
the requirements of the users are met in a proper manner.