ICT Project Management Assessment-3 Charter

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

Student Name: Student ID:
Table of Contents
Introduction.................................................................................................................................................3
PART-1 MOV (Measurable Organisational Value).....................................................................................3
Stakeholders............................................................................................................................................4
Timeframe for measurable organisational value......................................................................................6
Summary of MOV...................................................................................................................................6
PART-2 Scope Management Plan...............................................................................................................7
Functional Requirements.........................................................................................................................7
Non-functional requirements...................................................................................................................8
Features and functionalities that can be added.........................................................................................8
Deliverables of the project.......................................................................................................................9
Acceptance Criteria.................................................................................................................................9
List of Resources.....................................................................................................................................9
PART-3 MS Project..................................................................................................................................11
High-level work breakdown structure....................................................................................................11
Gantt chart.............................................................................................................................................12
PART-4 Project Risk Analysis and Plan....................................................................................................13
Risk Analysis.........................................................................................................................................14
Allocation of Risks................................................................................................................................16
PART-5 Quality Management Plan...........................................................................................................17
Project verification activities.................................................................................................................17
Project validation activities....................................................................................................................18
PART-6 Closure and Evaluation-Researching for the closure checklist and project evaluation................19
Closure Checklist...................................................................................................................................20
Project Evaluation.................................................................................................................................21
Performance of project team members..................................................................................................21
1

Student Name: Student ID:
Reviews from Globex corporation.........................................................................................................21
Project Outline.......................................................................................................................................22
References.................................................................................................................................................23
List of Figures
Figure 1- Break Down structure................................................................................................................11
Figure 2- Gantt Chart.................................................................................................................................12
List of Tables
Table 1: Targets and expectations of stakeholders.......................................................................................5
Table 2: Risk allocation to project team members.....................................................................................16
Table 3: Functional Testing methods.........................................................................................................18
Table 4- Performance of project team members........................................................................................21
2

Student Name: Student ID:
Introduction
This assessment will be going to deal with the project management strategies and techniques for
the IT companies named Globex and Virtucon. I as an IT Project manager consultant will be
going to design an online booking system for the RALS committee. This will help in replacing
their current manual system. The online booking system will provide ease of access to the users.
Users can be able to login to the system. Users can access the services provided by the RALS
committee effectively.
PART-1 MOV (Measurable Organisational Value)
There are various project management techniques that are used to evaluate measurable
organizational value to the company. Companies face various issues in implementing appropriate
strategies. Organizational value can be achieved by managing the business activities that are
performed in an organization (Viana & Mota, 2016).
Organisational value is measured according to the different functional areas-
 Strategy- There will be different marketing strategies applied to the GLOBEX to attain an
economic value in the market. Strategy has been put up on the highest priority in order to
increase sales and reach out to more number of customers.
 Financial- it has been proposed that each customer will be allowed an ID through which
entry will be allowed in RALS. This has been put up next to strategy as after investments
for the project has to be calculated for the applied marketing strategy.
 Operational- the cost of system installation will be less. Also, the company will gain
operational benefits as the system is designed using advanced technology. There will be
an upgraded software installation system so that users will not have to spend much on
maintenance cost.
 Customer- the target audience for GLOBEX is their customers. The customers will be
targeted according to the current market demands. Customers are a priority as they can
add better organizational value for the development of company. The system will provide
ease of access to the customers. Customers will be able to access the services provided by
the company.
3

Student Name: Student ID:
 Social- Following better marketing strategy, the company will be able to reach out to
more number of customers. Marketing mix will be used to enhance the product value.
This has been put up on the least priority because interaction with clientele is a long
process.
For our client GLOBEX, the two values that will be suitable are-
Better- our aim is to provide a better quality system to the client. It is because most
numbers of customers are not attracted by price but the quality of the system. If we will
improve performance and reliability of the system, then the customers will be going to
approach the proposed business strategies. Customers will be able to easily make a
purchase of the services available to them. The system is of 4GB RAM which will
provide better response time to access. Customers will also be able to access other details
like to provide reviews about the services, view latest updates, collect payment invoices
of each purchase and to view history.
Do more- GLOBEX wants to have continuous development in their business growth.
Therefore, do more value has been chosen. This will be beneficial for the company to
look forward to accomplishing long-term goals of the company. Currently, company
wants to assure that the applied strategies are beneficial. According to the profit received,
company will plan to change or modify the current marketing strategy that has been
applied. Hence, do more value is required by the client.
Stakeholders
These are individual or group or individuals who are focused on contributing success for any
project of the company. Stakeholders for this project are:
 Customers
 Members of GLOBEX
 Staff members of RALS
 Consultant
 Experts
 Software developer
 Investors
4

Student Name: Student ID:
 Project team
 Project Manager
 Supervisor
To determine the targets and expectations of the stakeholders, the tabular form is used.
Table 1: Targets and expectations of stakeholders
Targets Expectations
Speed The system should be capable of loading a large amount of information
Accuracy The system’s operations must be exactly as per the instructions provided
Completenes
s
Complete information shall be provided by the system to manage the regular
work
Value The system shall provide suitable economic value
Defects The system should be capable to tolerate errors or technical issues
Cost There should be overall benefits provided by the system for the applied
development cost
Out of the above-discussed targets, the quantitative targets are the cost that will be analysed to
rate the company’s progress. Project benefits will be analysed according to the applied
development cost. Development cost of the project will include costs like operational cost, cost
of maintenance, cost of hiring personnel, cost of resources.
1) The project will be approximately of 45 days
2) The total cost of resources will be approximately 35% of the used development cost
3) Cost of using marketing strategy will be about 25%
4) Benefits are expected to be about 40%
5

Student Name: Student ID:
Timeframe for measurable organisational value
The project schedule will be designed according to the project development requirements. Each
project activity will be completed in a specific time duration which is shown below:
Project Activity Duration
Analysis 2 days
Project initialisation 1 day
Resource Planning 3 days
Design specification 7 days
Development of online booking system 14 days
Prototype 2 days
Working on client feedback 3 days
Testing 7 days
implementation 8 days
Project Documentation 3 days
Project evaluation 5 days
Summary of MOV
Using this online booking system, RALS will be able to manage the workflow on a regular basis.
As the information will be transferred online, communication of the RALS committee will be
effective. This system will be cost effective as there is very less maintenance cost. The system is
flexible that is suitable changes can be made to the system according to the change in demands
of customers. The project will achieve success in terms of increase in sales and productivity. The
different marketing strategies will be useful in reaching out to more number of customers. RALS
will acquire better growth in their business as all the necessary IT asset of the company will be
managed easily. On the other hand, Globex will attain higher customer value in market as
compared to other committees.
6

Student Name: Student ID:
PART-2 Scope Management Plan
Project Scope: Aim of the project is to provide an easy access to the information for the
exhibitors of RALS. This system will allow users to enter the personal details to log in to the
system and to access the services provided to them. The developed system can be extended
according to the user requirements (Simplilearn, 2017).
Requirements: for the scope management plan for the developed system following functional and
non-functional requirements are-
Functional Requirements:
1. Login: existing exhibitors can directly login to the system using valid username and
password
2. Register: this functionality is for the new users of online bookings system. This includes
new members of committee and new exhibitors of RALS. There will be fewer details that
have to be filled by the users in the registration form that is first name, last name, contact
number, address, email address, pin code.
3. View event: users can visit this page of the system to view any event in their nearby
location. Users can create booking according to the event date
4. Book seats: exhibitors can book seats for an event by choosing a specific row of the fixed
price.
5. Payment: each event of RALS will have a fixed price which can be paid by the users
making an online payment. Exhibitors can use their net banking services for debit/credit
card to complete the payment process.
6. Invoice: Once the users are completed with the payment process, users can receive
payment invoices for the booked seats. The automatically generated invoices will contain
bill number, exhibitor’s personal details and booking seat number, price, event name and
event date.
7. Help: users can click on the help button to take guidance about any service provided by
the RALS committee.
7

Student Name: Student ID:
8. Enquiry: By clicking on this options, users will be able to receive information regarding
the current event taking place, offers or discounts available.
9. Social media integration: there will be options for the users to connect on social
networking sites like facebook, twitter and Instagram for latest updates of RALS event
(Chung, 2017).
Non-functional requirements-
1. Accessibility- the system can be effectively accessed by the users. Simple English
language is used which can be easily readable and understandable by the users.
2. Performance- the response time of system is low which will make the application
programs run smoothly. The processor is of good quality which has better fault tolerance
capacity.
3. Scalability- the system can be accessed on any operating system like Windows, Linux.
4. Flexibility- there is an option to upgrade the system that can be used with the increase in
demands of customers. The system is also flexible with the advancement in technology.
5. Accuracy- the system will provide exact information when it is searched in the database.
6. Reliability- the maintenance of the online booking system is low. It is because there are
backup and recovery options (Chung, 2017).
In scope-out scope options: the above mentioned functional and non-functional requirements will
be going to be used in the design and development of online booking system. Using these
requirements, users can manage the operations performed in any event. Benefit in fulfilling these
requirements is that duplication of IT assets will be noticed. Company will have a growth in
business as more number of customers will be increased.
Features and functionalities that can be added-
 Option for forgot password- if the users do not remember their password then ‘forgot
password’ options will be useful to them. Users will be navigated to their accounts to
reset password for continue accessing the system.
 Search options- this option will be added to each page of the system. Users can write a
keyword to find relevant information.
8

Student Name: Student ID:
9

Student Name: Student ID:
Deliverables of the project
 Resource plan
 Work break down structure to list the activities
 Project schedule
 Cost-benefit analysis
 Scope management plan
 System requirement specification
 Project documentation
Acceptance Criteria:
 The system should be responsive to be accessed on different devices like tablets, laptops
or smartphones
 The system should work on online services
 System should provide consistency to the information stored in the database
List of Resources
People- individuals that will be going to support the project are listed below. It is essential to
have skilled personnel to design and develop the project. The skilled person can use effective
project management techniques to evaluate risks and lead to project success.
 Customers- customers will specify their needs for the online booking system. Customers
will provide their valuable feedback for the prototype that will be created.
 Members of GLOBEX- members will state the overall budget of the project.
 Consultant- the design for the development of online booking system will be approved by
the design consultant of the project.
 Experts- experts will identify risks in the project if any.
 Software developer- for the designed layout, software developer will develop online
booking system using a feasible technology.
 Project Manager- from the analysis of project till the project documentation, project
manager will monitor the team members to perform activities. Project manager will be
10

Student Name: Student ID:
responsible to guide the team members to include all the functional and non-functional
requirements specified by the client.
Technology-
 Hardware- computer system, scanner, printer, credit/debit card machine
 Network- local area network will be connected
 Software- 32-bit operating system, 4GB RAM
Facilities-
For the project team members, workstation will be designed so that they can conveniently.
Resources such as hardware, software requirements will be fulfilled. Information regarding
project briefing will be provided to the users so that team members can analyse needs of client.
Other-
Project team members will be provided with the regular expenses that include conveyance
charges, accommodation charges, and to fulfil other necessities. The skilled project team
members will be provided with the necessary software tools required whereas training will be
provided to the members to access the equipment that will be going to be used in the
development of online booking system.
11

Student Name: Student ID:
PART-3 MS Project
This is a type of software application that is used to schedule the project activities in order to
calculate the duration of tasks, start date, end date and the milestones that will be achieved
during the development of project.
High-level work breakdown structure-
12

Student Name: Student ID:
ID Task
Mode
Task Name Duration Start Finish Predecessors Resource Names Cost
0 Automated
Booking System
81 days Sat
12/2/17
Mon
3/26/18
$25,088.00
1 1 Project Scope 6 days Mon 12/4/17Mon 12/11/17 $1,968.00
2 1.1
Determine
scope of
3 days Mon
12/4/17
Wed
12/6/17
Project
Manager
$1,008.00
3 1.2 Meeting
with senior
executive
3 days Thu
12/7/17
Mon
12/11/17
2 System Analyst $960.00
4 2 Milestone:
Scope
completed
0 days Mon
12/11/17
Mon
12/11/17
3 $0.00
5 3 Planning 17 days Tue 12/12/17Wed 1/3/18 $5,552.00
6 3.1 Project
constraint
identification
2 days Tue
12/12/17
Wed
12/13/17
3 Experts $608.00
7 3.2 Gather
requirements
4 days Thu
12/14/17
Tue
12/19/17
6 System Analyst $1,280.00
8 3.3 Interview
with
stakeholders
5 days Wed
12/20/17
Tue
12/26/17
7 Project
Manager
$1,680.00
9 3.4 User
requirement
documentation
3 days Wed
12/27/17
Fri
12/29/17
8 Project
Manager
$1,008.00
10 3.5 Discussion
with
stakeholders
1 day Mon 1/1/18 Mon 1/1/18 9 Project
Manager
$336.00
11 3.6 Define goals2 days Tue 1/2/18 Wed 1/3/1810 System Analyst $640.00
12 4 Milestone:
Requirements
Documentation
Completed
0 days Sat 12/2/17 Sat 12/2/17 $0.00
13 5 Analysis 6 days Thu 1/4/18 Thu 1/11/18 $1,888.00
14 5.1 Assess
requirements
2 days Thu 1/4/18 Fri 1/5/18 11 System Analyst $640.00
15 5.2 Budget 2 days Mon 1/8/18 Tue 1/9/18 14 Experts $608.00
16 5.3 Resource
Analysis
2 days Wed
1/10/18
Thu
1/11/18
15 System Analyst $640.00
17 6 Milestone:
Analysis done
0 days Thu
1/11/18
Thu
1/11/18
16 $0.00
18 7 Cost Estimation9 days Fri 1/12/18 Wed 1/24/18 $2,592.00
19 7.1
Development
cost
3 days Fri 1/12/18 Tue
1/16/18
16 System Analyst $960.00
20 7.2
Operational
cost
3 days Wed
1/17/18
Fri 1/19/18 19 Design
Consultant
$624.00
21 7.3 Cost of
hiring
personnel
3 days Mon
1/22/18
Wed
1/24/18
20 Project
Manager
$1,008.00
22 8 Miletstone:
Cost estimation
done
0 days Wed
1/24/18
Wed
1/24/18
21 $0.00
23 9 Design 22 days Thu 1/25/18Fri 2/23/18 $6,328.00
24 9.1
Preliminary
software
specification
1 day Thu
1/25/18
Thu
1/25/18
21 Design
Consultant
$208.00
25 9.2 Functional
Specification
3 days Fri 1/26/18 Tue
1/30/18
24 Project
Manager
$1,008.00
26 9.3 Design Layout2 days Wed 1/31/18Thu 2/1/18 25 Software Engineer $400.00
27 9.4 UML diagrams4 days Fri 2/2/18 Wed 2/7/1826 Database Designer $1,120.00
28 9.5 Design
Consulting
2 days Thu 2/8/18 Fri 2/9/18 27 System Analyst $640.00
29 9.6 Expert Feedback1 day Mon 2/12/18Mon 2/12/1828 Project Manager $336.00
30 9.7
Stakeholders
Expectation
2 days Tue
2/13/18
Wed
2/14/18
29 Project
Manager
$672.00
31 9.8 User
Preferences
3 days Thu
2/15/18
Mon
2/19/18
30 Software
Engineer
$600.00
32 9.9
Communication
with team
members
4 days Tue
2/20/18
Fri 2/23/18 31 Project
Manager
$1,344.00
33 9.10
Milestone:
Designing
completed
0 days Fri 2/23/18 Fri 2/23/18 32 $0.00
34 10 Development 12 days Mon 2/26/18Tue 3/13/18 $2,416.00
35 10.1 Templates3 days Mon 2/26/18Wed 2/28/1832 Software Engineer $600.00
36 10.2
Integrated
Development
environment
2 days Thu 3/1/18 Fri 3/2/18 35 Design
Consultant
$416.00
37 10.3
Programming
languages
7 days Mon 3/5/18 Tue
3/13/18
36 Software
Engineer
$1,400.00
38 10.4
Milestone:
Development
Completed
0 days Tue
3/13/18
Tue
3/13/18
37 $0.00
39 11 Testing 81 days Mon 12/4/17Mon 3/26/18 $2,344.00
40 11.1 Security Testing4 days Wed 3/14/18Mon 3/19/1837 Project Manager $1,344.00
41 11.2
Performance
Testing
5 days Tue
3/20/18
Mon
3/26/18
40 Software
Engineer
$1,000.00
42 11.3
Milestone:
Testing
performed
1 day Mon
12/4/17
Mon
12/4/17
$0.00
43 12 Maintenance 10 days Tue 12/5/17Mon 12/18/17 $2,000.00
44 12.1 Software
Upgrade
5 days Tue
12/5/17
Mon
12/11/17
42 Software
Engineer
$1,000.00
45 12.2
Hardawre
Upgrade
5 days Tue
12/12/17
Mon
12/18/17
44 Software
Engineer
$1,000.00
46 12.3
Milestone:
Maintenance
done
0 days Mon
12/18/17
Mon
12/18/17
45 $0.00
Dec 10, '17
Figure 1- Break Down structure
Gantt chart-
13

Student Name: Student ID:
ID Task
Mode
Task Name Duration Start Finish Predecessors Resource Names Cost
0 Automated
Booking System
81 days Sat
12/2/17
Mon
3/26/18
$25,088.00
1 1 Project Scope 6 days Mon 12/4/17Mon 12/11/17 $1,968.00
2 1.1
Determine
scope of
3 days Mon
12/4/17
Wed
12/6/17
Project
Manager
$1,008.00
3 1.2 Meeting
with senior
executive
3 days Thu
12/7/17
Mon
12/11/17
2 System Analyst $960.00
4 2 Milestone:
Scope
completed
0 days Mon
12/11/17
Mon
12/11/17
3 $0.00
5 3 Planning 17 days Tue 12/12/17Wed 1/3/18 $5,552.00
6 3.1 Project
constraint
identification
2 days Tue
12/12/17
Wed
12/13/17
3 Experts $608.00
7 3.2 Gather
requirements
4 days Thu
12/14/17
Tue
12/19/17
6 System Analyst $1,280.00
8 3.3 Interview
with
stakeholders
5 days Wed
12/20/17
Tue
12/26/17
7 Project
Manager
$1,680.00
9 3.4 User
requirement
documentation
3 days Wed
12/27/17
Fri
12/29/17
8 Project
Manager
$1,008.00
10 3.5 Discussion
with
stakeholders
1 day Mon 1/1/18 Mon 1/1/18 9 Project
Manager
$336.00
11 3.6 Define goals2 days Tue 1/2/18 Wed 1/3/1810 System Analyst $640.00
12 4 Milestone:
Requirements
Documentation
Completed
0 days Sat 12/2/17 Sat 12/2/17 $0.00
13 5 Analysis 6 days Thu 1/4/18 Thu 1/11/18 $1,888.00
14 5.1 Assess
requirements
2 days Thu 1/4/18 Fri 1/5/18 11 System Analyst $640.00
15 5.2 Budget 2 days Mon 1/8/18 Tue 1/9/18 14 Experts $608.00
16 5.3 Resource
Analysis
2 days Wed
1/10/18
Thu
1/11/18
15 System Analyst $640.00
17 6 Milestone:
Analysis done
0 days Thu
1/11/18
Thu
1/11/18
16 $0.00
18 7 Cost Estimation9 days Fri 1/12/18 Wed 1/24/18 $2,592.00
19 7.1
Development
cost
3 days Fri 1/12/18 Tue
1/16/18
16 System Analyst $960.00
20 7.2
Operational
cost
3 days Wed
1/17/18
Fri 1/19/18 19 Design
Consultant
$624.00
21 7.3 Cost of
hiring
personnel
3 days Mon
1/22/18
Wed
1/24/18
20 Project
Manager
$1,008.00
22 8 Miletstone:
Cost estimation
done
0 days Wed
1/24/18
Wed
1/24/18
21 $0.00
23 9 Design 22 days Thu 1/25/18Fri 2/23/18 $6,328.00
24 9.1
Preliminary
software
specification
1 day Thu
1/25/18
Thu
1/25/18
21 Design
Consultant
$208.00
25 9.2 Functional
Specification
3 days Fri 1/26/18 Tue
1/30/18
24 Project
Manager
$1,008.00
26 9.3 Design Layout2 days Wed 1/31/18Thu 2/1/18 25 Software Engineer $400.00
27 9.4 UML diagrams4 days Fri 2/2/18 Wed 2/7/1826 Database Designer $1,120.00
28 9.5 Design
Consulting
2 days Thu 2/8/18 Fri 2/9/18 27 System Analyst $640.00
29 9.6 Expert Feedback1 day Mon 2/12/18Mon 2/12/1828 Project Manager $336.00
30 9.7
Stakeholders
Expectation
2 days Tue
2/13/18
Wed
2/14/18
29 Project
Manager
$672.00
31 9.8 User
Preferences
3 days Thu
2/15/18
Mon
2/19/18
30 Software
Engineer
$600.00
32 9.9
Communication
with team
members
4 days Tue
2/20/18
Fri 2/23/18 31 Project
Manager
$1,344.00
33 9.10
Milestone:
Designing
completed
0 days Fri 2/23/18 Fri 2/23/18 32 $0.00
34 10 Development 12 days Mon 2/26/18Tue 3/13/18 $2,416.00
35 10.1 Templates3 days Mon 2/26/18Wed 2/28/1832 Software Engineer $600.00
36 10.2
Integrated
Development
environment
2 days Thu 3/1/18 Fri 3/2/18 35 Design
Consultant
$416.00
37 10.3
Programming
languages
7 days Mon 3/5/18 Tue
3/13/18
36 Software
Engineer
$1,400.00
38 10.4
Milestone:
Development
Completed
0 days Tue
3/13/18
Tue
3/13/18
37 $0.00
39 11 Testing 81 days Mon 12/4/17Mon 3/26/18 $2,344.00
40 11.1 Security Testing4 days Wed 3/14/18Mon 3/19/1837 Project Manager $1,344.00
41 11.2
Performance
Testing
5 days Tue
3/20/18
Mon
3/26/18
40 Software
Engineer
$1,000.00
42 11.3
Milestone:
Testing
performed
1 day Mon
12/4/17
Mon
12/4/17
$0.00
43 12 Maintenance 10 days Tue 12/5/17Mon 12/18/17 $2,000.00
44 12.1 Software
Upgrade
5 days Tue
12/5/17
Mon
12/11/17
42 Software
Engineer
$1,000.00
45 12.2
Hardawre
Upgrade
5 days Tue
12/12/17
Mon
12/18/17
44 Software
Engineer
$1,000.00
46 12.3
Milestone:
Maintenance
done
0 days Mon
12/18/17
Mon
12/18/17
45 $0.00
Project Manager
System Analyst
12/11
Experts
System Analyst
Project Manager
Project Manager
Project Manager
System Analyst
12/2
System Analyst
Experts
System Analyst
1/ 11
System Analyst
Design Consultant
Project Manager
1/ 24
Design Consultant
Project Manager
Software Engineer
Database Designer
System Analyst
Project Manager
Project Manager
Software Engineer
Project Manager
2/ 23
Software Engineer
Design Consultant
Software Engineer
3/ 13
Project Manager
Software Engineer
Software Engineer
Software Engineer
12/18
M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T
Dec 10, '17 Dec 17, '17 Dec 24, '17 Dec 31, '17 Jan 7, '18 Jan 14, '18 Jan 21, '18 Jan 28, '18 Feb 4, '18 Feb 11, '18 Feb 18, '18 Feb 25, '18 Mar 4, '18 Mar 11, '18 Mar 18, '18 Mar 25, '18
Figure 2- Gantt Chart
14

Student Name: Student ID:
PART-4 Project Risk Analysis and Plan
In this part of project, I will be going to analyse risks for the project. I will document
assumptions that will be taken for the project. Thereafter, I will be going to identify project risks
and write down the risk mitigation strategies. Project risks are identified according to the
probability of something that might goes wrong or the negative consequences of project
strategies (Mindtools, 2017).
Assumptions
a) It has been assumed that the online booking system will utilize internet services
b) The project shall have specific time schedule
c) Appropriate project management techniques shall be used for the project success
d) The system shall be responsive to devices like smartphones, tablets
e) Navigation feature shall provide ease of access to the users. Users shall be able to move
on the different pages to access the services
f) Annual benefits of the system will be approximately $30,000
g) The project shall be completed within 45 days
h) Skilled personnel shall be hired for the better accomplishment of project activities
As per the phases of risk framework methodology, following five risks can be listed for the
development of an online booking system.
1. Human- risks of a loss to an individual in terms of injuries during the project
development. This can include health issues while project development process.
2. Operational- if there will be a loss of IT assets during the project development, it will be
a risk.
3. Procedural- control and monitor of the project activities if are not proper then the project
scheduling will be affected
4. Project- if the project budget increases due to some consequences or the service quality
lack then the project completion process will be going to delayed.
5. Financial- this includes business analysis for a project. Stock market value has to be
analysed timely in order to apply suitable marketing strategies for the project success
15

Student Name: Student ID:
6. Technical- technical failure such as software system, it will be a project risk (Mindtools,
2017).
Risk Analysis
According to the risks that are identified for the project, each project team member will be
assigned a risk. These risks can be resolved by implementing the appropriate action plan.
Number R35
Rank 1
Risk Human
Description The project development process often leads injuries or health issues to the hired
personnel. Human is risk to the project as safety of hired personnel is important
Category risk of human resources
Root cause work pressure affects the health of an individual
Triggers from among the listed activities, might be sometimes personnel receive a higher
load of work
Risk
responses
it is the duty of project manager to manage the workflow. He has to analyse the
allocation of project activities according to the capabilities of personnel
Risk Owner Project manager
Probability less
16

Student Name: Student ID:
Number R36
Rank 2
Risk Operational
Description IT assets are the most important factor in project development process. Loss to
information can affect the project success
Category risk to IT assets
Root cause Improper documentation
Triggers Manual records can be lost during the accomplishment of project activities
Risk
responses
Project team members have to take care of the information that is shared by the
stakeholders
Risk Owner Project team members
Probability high
Number R38
Rank 3
Risk Procedural
Description The project activities need to be monitored to avoid risks such as delayed in any
task, or inappropriate quality product is delivered to client
Category risk to project scheduling
Root cause Inadequate use of project management tools
Triggers This can decrease the regular workflow of project activities
Risk
responses
This risk can affect the cost that has been applied by the investors for the project.
Risk Owner Project team members
Probability Medium
17

Student Name: Student ID:
Number R40
Rank 4
Risk Technical Risk
Description These type of risks are associated with the issues that may occur in a computer
system. This includes memory, software upgrade, system vulnerabilities and so
on.
Category Risk to the system
Root cause Hardware and software specifications has to be done properly
Triggers This can affect overall performance of computer system
Risk
responses
This can lead to delays in the day to day activities that are performed
Risk Owner Software Engineer
Probability High
Allocation of Risks
Table 2: Risk allocation to project team members
Risk Team Member
Human Member-1
Operational Member-2
Procedural Member-1
Technical Member-3
18

Student Name: Student ID:
PART-5 Quality Management Plan
Quality of a project is generally determined by the customer in terms of project deliverables and
project activities that take place during the development of a system (Doit, 2017). This project is
based on the design and development of an online booking system for the exhibitors of RALS
committee.
There are various quality management activities that will be initialized for assuring quality of the
development of online booking system-
 The project meets all the necessary requirements specified by the client
 Project development processes are documented so that project manager can analyse the
overall progress
 For the identifies risks in the project, appropriate risk mitigation strategies are applied
 Quality standards are determined by the customers according to the project deliverables
Statement for quality assurance-
This project is initialized under the guidance of project manager and the necessary issues are
resolved by the design consultants and experts. This project aims to develop an online booking
system for RALS committee. The system will provide consistency and efficiency to the data that
will be going to share among different departments of RALS. For each event, exhibitors will be
able to view the details of an upcoming event. Exhibitors can book their desirable seats online by
making an online payment. Invoices will be automatically generated for each payment made by
the exhibitors.
Project verification activities
It is an internal process which takes place during the development of the project. For the project
verification of the developed online booking system, stakeholders such as experts, consultants,
and project manager have verified whether the user requirements are satisfied or not. Project
scope is verified by using work breakdown structure as shown in part-3. The stakeholders have
analyzed the project deliverables and the activities that were performed. Inspection verification
19

Student Name: Student ID:
technique is used by the stakeholders to analyse the developed system (Project-management-
knowledge, 2017).
Project validation activities
Validation techniques are used for a project to ensure that the accurate features and
functionalities are designed for the online booking system. Validation process assures that the
end-users needs are accomplished using appropriate tools and techniques. To initialize validation
process, I have using different testing methods such as functional testing, performance testing
and security testing methods.
1. Functional Testing
Table 3: Functional Testing methods
Testing Description
Unit testing Unit of code is tested to ensure that the appropriate procedures have been
used in the programming or not.
Integration testing This type of testing is performed to ensure that the flow of information is
appropriate for the developed system
System Testing The behaviour and functionalities of overall system is tested to ensure
speed and performance of the system
Acceptance testing Alpha and beta testing is done to check whether the users are able to
access the system conveniently
20

Student Name: Student ID:
2. Performance Testing
Load time of the system is tested to ensure that the developed system is reliable to use. The
success rate of the system is analyzed using performance testing. This type of testing is
performed by increasing load on a particular application to check the robustness.
3. Security Testing
Error handling techniques are used to check the unprotected channels of the online booking
system. Since the data is accessed using internet services there is a higher risk of privacy and
security to the system.
21

Student Name: Student ID:
PART-6 Closure and Evaluation-Researching for the closure checklist and
project evaluation
Research for this project has been done by taking four different bibliographies
Annotated Bibliography-1
Orso, A., & Rothermel, G. (2014, May). Software testing: a research travelogue (2000–
2014). In Proceedings of the on Future of Software Engineering (pp. 117-132). ACM.
In this research paper, the author discusses the importance of software testing techniques. Types
of software testing, the importance of these techniques and how these are effective for the
development of a software system. The author states that software testing is the most widely used
approaches for ensuring efficient coding of the system. Author has also discussed automated
testing methods that are used by the software testers. Automated testing consumes less time but
is costly as compared to the manual testing method. Manual testing can be performed by the
skilled professionals to test the functionality of the developed system. Research paper has also
discussed the testing strategies for improving procedures for the testing methods.
Annotated Bibliography-2
Al-Neaimi, A., Qatawneh, S., & Saiyd, N. A. (2012). Conducting Verification And
Validation Of Multi-Agent Systems. arXiv preprint arXiv:1210.3640.
To understand the complexities of a software system, verification and validation techniques are
used by the software developers as described by the author in this journal. These techniques are
used to improve the quality of the software system. Author describes verification process as the
process in which consistency for the fulfilment of user requirements are specified whereas
validation process is concerned in providing security to the clients all the specific features and
functionalities are included in the final design of the project. Author describes how the
verification and validation processes are beneficial for the multi-agent systems. Lifecycle of
verification and validation processes is discussed in this research paper along with the techniques
using for V&V processes.
Annotated Bibliography-3
22

Student Name: Student ID:
Hans, R. T. (2013). Work Breakdown Structure: A Tool for Software Project Scope
Verification. arXiv preprint arXiv:1308.2876.
The author has described the scope management and how it is beneficial for determining success
of a project. Tool for Software Project Scope Verification is generally used to deliver the
requirements of users and to minimize the changes that have to be done after the feedback
received from the client. The author has described the project management tool that can be used
to define the scope of the project. In this paper, author provides information regarding the
development of software system and how work breakdown structure can be used to analyze
completion of project deliverables. Author describes about the constraints that contributes for the
project success. These are time, cost, project goals and objectives. Author describes the
importance of scope verification using work breakdown structure that can be used to measure the
project success.
Annotated Bibliography-4
Silvius, A. G., & Schipper, R. P. (2014). Sustainability in project management
competencies: analyzing the competence gap of project managers. Journal of Human
Resource and Sustainability Studies, 2(02), 40.
In this journal, the author has described the sustainability of the project. How it is beneficial for
the project and what implications does it have on the project deliverables and milestones.
Authors have described the role of project managers in providing guidance to the team members
to maintain sustainability. The different methodologies have been described by the author about
sustainability competencies that have to be matched with project management techniques.
Author describes the sustainability of the project as the process of continuous modifications of
business processes takes place for a project. This journal is used to gather information regarding
the sustainability of a project.
Closure Checklist
This type of checklists is used in the project to determine the individual contribution of each
team member. This is used to draw conclusions after the project completion.
23

Student Name: Student ID:
 Contract closure: project manager has coordinated with the investors before initializing
the project. Request is successfully accepted by the investors to support financially for
the different project activities.
 Financial closure: the project team members will be notified of closing date of the
expenses that have to be applied for the project. Invoices and bills will be generated
according to the resources used for the project.
Project Evaluation
The project is initialized by identifying the stakeholders. Target and stakeholder expectations are
documented for the project. Risks for the project is identified and their corresponding risk
mitigation strategies are proposed. Goals and objectives of the project are identified to design an
effective online seat booking system for the exhibitors of RALS committee. Work breakdown
structure and Gantt chart is used to schedule the project activities.
Performance of project team members
Table 4- Performance of project team members
Project team
member
Individual contribution
Member-1 Accurately documented the user requirements
Member-2 Project scheduling is appropriately done
Member-3 Risk analysis plan was good
Member-4 Perfectly coordinated with team members
Member-5 Quality management plan is excellent
Member-6 Collaboration with other team members is appreciated
Reviews from Globex corporation-
 Project deliverables are received on time
 Quality of the system is excellent
 Cost of the project is appropriate
 All the specific requirements are fulfilled
24

Student Name: Student ID:
Project Outline
The project was initiated according to the requirements made by the client Globex for the RALS
committee. First part of the project has discussed measurable organisational value understand the
factors that could contribute to the project success. Stakeholders were identified as beginning the
project. Following parts of the project contributes in deciding quality management plan, risk
analysis plan, work breakdown structure and Gantt chart. These project activities were performed
under the guidance of project manager. After the deployment of online seat booking system users
of Globex and RALS can provide their valuable feedback. The project success can be counted
only if the clients will accept the project. In order to gain acceptance for the project, requirement
specification has been already satisfied.
25

Student Name: Student ID:
References
 Al-Neaimi, A., Qatawneh, S., & Saiyd, N. A. (2012). Conducting Verification And
Validation Of Multi-Agent Systems. arXiv preprint arXiv:1210.3640.
 Careercentre. (2017). ICT project manager. Retrieved from
http://www.careercentre.dtwd.wa.gov.au/Occupations/Pages/ICT-project-manager.aspx
 Chung, L. (2017). Non-Functional Requirements (pp. 1-5). Texas. Retrieved from
https://www.google.co.in/url?
sa=t&rct=j&q=&esrc=s&source=web&cd=19&cad=rja&uact=8&ved=0ahUKEwiJisq-
lNXYAhUQ5o8KHTeRBMoQFgiSATAS&url=https%3A%2F%2Fwww.utdallas.edu
%2F~chung%2FSYSM6309%2FNFR-18-4-on-
1.pdf&usg=AOvVaw3Ur6oheRPnVMbh7dlegX1V
 Doit. (2017). PMA - 3.Plan - Develop Quality Management Plan. Retrieved from
https://pma.doit.wisc.edu/plan/3-2/what.html
 Hans, R. T. (2013). Work Breakdown Structure: A Tool for Software Project Scope
Verification. arXiv preprint arXiv:1308.2876.
 Mindtools. (2017). Risk Analysis and Risk Management: Evaluating and Managing Risks.
Retrieved from https://www.mindtools.com/pages/article/newTMC_07.htm
 Orso, A., & Rothermel, G. (2014, May). Software testing: a research travelogue (2000–
2014). In Proceedings of the on Future of Software Engineering (pp. 117-132). ACM.
 Project-management-knowledge. (2017). Verification - Project Management Knowledge.
Retrieved from https://project-management-knowledge.com/definitions/v/verification/
 Silvius, A. G., & Schipper, R. P. (2014). Sustainability in project management competencies:
analyzing the competence gap of project managers. Journal of Human Resource and
Sustainability Studies, 2(02), 40.
 Simplilearn. (2017). Project Scope Management: What It is and Why It’s Important.
Retrieved from https://www.simplilearn.com/project-scope-management-importance-rar89-
article
26

Student Name: Student ID:
 Viana, J., & Mota, C. (2016). Enhancing Organizational Project Management Maturity: a
framework based on the value focused thinking model. Production, 26(2), 313-329.
http://dx.doi.org/10.1590/0103-6513.169913
27