Development of Mobile based application

This project focuses on the development of a mobile based application for the LGBT community. It includes project information, scope statement, assumptions, constraints, approach, requirements, proposed deliverables, project charter, and more.

Running head: PROJECT MANAGEMENT
Project management: Development of Mobile based application
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
Introduction......................................................................................................................................3
1. Project Information......................................................................................................................3
1.1 Scope statement for the project..............................................................................................3
1.2 Assumptions..........................................................................................................................4
1.3 Constraints.............................................................................................................................5
2. Approach......................................................................................................................................5
2.1 Use case scenario for “Ease in Tees”....................................................................................5
2.1 Requirements.........................................................................................................................7
2.3 Proposed deliverables............................................................................................................8
3. Project charter..............................................................................................................................8
4. Governance and reporting..........................................................................................................11
4.1 Governance structure...........................................................................................................11
4.1.1 Work breakdown structure...........................................................................................11
Initiation.....................................................................................................................................12
4.1.2 RACI matrix.................................................................................................................14
4.2 Stakeholder management.....................................................................................................16
4.3 Communication plan............................................................................................................17
5. Project controls..........................................................................................................................18
5.1 Schedule and dependencies management............................................................................18
5.1.1 Schedule of the project.....................................................................................................18
5.1.2 Schedule management..................................................................................................20
5.2 Financial management.........................................................................................................24
5.3 Risk register.........................................................................................................................26
5.4 Quality management............................................................................................................28
5.5 Project monitoring and control............................................................................................29
5.6 Lessons learnt......................................................................................................................31
6. Contribution by the team members............................................................................................31
Bibliography..................................................................................................................................32

2
PROJECT MANAGEMENT
Introduction
The project is based on the development of a mobile based application namely ‘Ease in Tees’ for
the LBGT community which is also referred as one of the gay community who are mainly united
by the common cultural as well as social movements. The organization is focusing on developing
an effective and attractive mobile based application in order to attract a large customer base. For
this purpose, the project involves a thorough analysis of the project scope, assumptions,
constraints and key deliverables. Along with that, the paper presents a project charter for the
concerned project, which in turn also encompasses the main PM modules including the
stakeholder management, schedule management, risk management and project quality control.
1. Project Information
Project name Development of a mobile based application “Ease in Tees” for the
LGBT community.
Project ID <Please fill>
Project Manager <Please fill>
Project Sponsor <Please fill>
Project SharePoint site (link):
1.1 Scope statement for the project
Project Title:
Date:
Project Prepared By :
The project title is to properly develop a mobile
based application “Ease in Tees” for the LGBT
community.
The date of commencement 10-05-2019
The project is prepared by the following people:
 Anurupa
 Nafeez
 Lijan
 Manu
 Aamir
Project Justification
As the customers of the today’s world have
generally moved towards mobile application
platform therefore the development of mobile based
app for the LGBT community is needed. It is found
that because of the mobile apps, the customers can
be capable of assessing all the information related
with the products at their fingertips. They are
generally needed within the business for increasing
the customer base by increasing the visibility as
well as reinforcing the brand of the organization.

3
PROJECT MANAGEMENT
Product Characteristics and Requirement
The characteristics, as well as requirements, are
listed below:
 Well planned browser consistency
 Proper information architecture
 Proper error handling feature.
 Proper formatted content
 Fast load times
 Effective consistency
 Extremely helpful customer support
 Great user interface
Product user Acceptance criteria
The acceptance criteria are mainly listed below:
 Proper user interface navigation
 Real-time notifications to the customers
 Proper performance with very much lower
bandwidth
Project Management Related Deliverables
The project management based deliverables of the
project are listed below:
 Project charter
 Work breakdown structure
 Final project presentation
 Business case
 Team contract
 Final project reports and
 Other needed documents
Product-related Deliverables The product based deliverables mainly include:
 Design document
 Product prototype
 Design document
 Market research
1.2 Assumptions
The project assumptions which are generally made for developing the mobile based
application for the LGBT community are generally listed below:
 More than 10,000 users will be attracted with the help of the newly developed application
 The permit will generally take from the management head of the organization for
undertaking the entire work of the project
 The mobile app development will generally be developed within a $80,768 budget
 The application will work effectively steadily due to proper real-time notification
 The project will generally get accomplished in the time period of 56 days for
accomplishing the project goals as well as objectives.

4
PROJECT MANAGEMENT
1.3 Constraints
The constraints or limitations that are mainly related to the development of the mobile
based application are generally listed below:
 If the team members do not focus on the tracking of the project, then the chances of
slippage within the schedule are quite high that further causes obstruction within the
project
 In-house experts or team members are not sufficient for developing the application as
they are not much experienced and skilled
 The mobile based application launch will be delayed due to the absence of resources
which are during the execution phase of the project
2. Approach
2.1 Use case scenario for “Ease in Tees”
For properly developing the mobile application, the project manager mainly utilizes an
agile project management approach. The main reason for selecting the agile approach is that it
generally adopts various types of changes that generally occur during the entire time span of a
similar kind of application development process.
The main aim of the project is to satisfy the demands of the clients or customers by
providing proper services. The needs of the project are considered to be properly implemented
for achieving the completion of the project objective. The various categories of methods and
procedures, which are mainly used within the project mainly, include use case, work breakdown
structure, RACI matrix as well as a risk register. In order to make the prototype for the entire
application, it is quite necessary to undertake testing in order to check the functionality as well as
operations of the entire system.
 Actors: The main actors who are generally helping in achieving the entire procedure
include the customer, admin as well as the database administrator.
 User: The users are the customers who will generally utilize the services of the
customers. They are the individual who generally register as well as buys clothes with the
help of the application.
 Authentication: Authentication is considered as the back office service that is provided
in order to manage the mobile app properly for avoiding the different types of security
issues as well as challenges.

5
PROJECT MANAGEMENT
Use case explanation
Use case ID -1 Registration
The customers do registration in order to provide their details on the mobile application
so that they can be able to properly get access of the products that are present in order add the
products within the cart for buying them.
Use case ID-2 Login
Both the admin as well as the customers use the login option. It is found that the
customers mainly login in their account by using proper ID as well as password.
Use case ID 3: Add category
The admin manages the option of add category and as per the categories the different
products are generally present which means that the products are mainly differentiated on the
basis of category
Use case ID 4: Add item
Add item option is present so that the admin can add an option within the mobile app for
selling more types of products online.
Use case ID 5: Manage item
Manage item option is generally managed by the admin and they generally take the
responsibility of managing the items that they want to sell online.
Functionality
Actor
User
Authenti
cation

6
PROJECT MANAGEMENT
Use case ID 7: View item
The customers generally view the items that are present on the mobile app of “Ease in
Tees” and select the items in order to add them within the cart.
Use case ID 8: Make Order
If the items that are added within the mobile app are generally ordered by the customers
which are generally got stored within the database of the organization,
Use case ID 9: Make payment
As per the payment option that is present, it quite options to select the best option in order
to make the payment successfully.
2.1 Requirements
System requirements
 User-friendly: The mobile application "Ease in Tees" must be user-friendly for the users
by providing a proper UI interface so that the customers can enjoy the online services of
the organization. It is quite necessary to make sure that the customers do not face any
type of issues as well as challenges while using the mobile application. Additionally, it is
identified that this requirement mainly helps in reflecting that the organization is mainly
working hard for meeting the demands as well as the needs of the customers.
 Mobile application platform: It is found that there are a lot of mobile app builders are
generally available that will generally set up the mobile app so that they can strongly
recommend by utilizing self-hosted Word press on the platform of the mobile app.
 Mobile application speed: It is quite necessary that the mobile application must be able
to load quickly as it is one of the most significant requirements that is generally needed
for designing as well as developing the application quite effectively. In order to make
sure that the mobile application downloads within 15 second are one of the important
criteria.
 SSL security: It is announced by Google that going HTTPS by adding the SSL 2048-bit
key will be helpful in generally adding security within the mobile app. Therefore, the
organization must take all the initiative in order to maintain the security of the entire
system quite effectively.
 SEO friendly: One of the important aspects of SEO is that it general assists in making the
mobile application much easier for both the users as well as search engine robots for
properly understand.
Other requirements
 Real-time notification: Real-time notification system must be provided in order to update
the customers about the new requirements as well as products or offers that are generally
provided by the customers.
 Data storage: The personal data of the clients should be stored within the cloud in order
to secure them quite effectively by properly keeping the entire backup system such that
the data can be properly recovered even if the data get a lot due to technical issues.
 Backup system: It is found that due to some problem like a technical issue as well as hard
drive failure a number of challenges or issues occur due to data loss and therefore the

7
PROJECT MANAGEMENT
proper backup system is very much necessary. With the help of the backup system, the
data can be recovered quite easily so that both the users as well as staff can continue their
activities successfully.
2.3 Proposed deliverables
The proposed project deliverables are generally considered as the indicators of the
project that generally need success. The deliverables of the project will generally be redirected
with the help of the use case that is generally reflected below:
Figure 1: Use case
(Source: Created by Author)
3. Project charter
A project charter is generally utilized for determining the main project objectives. The
charter generally mainly incorporates the mission as well as the vision that are linked with the
project. The project charter can mainly help the mobile app in setting proper objectives.

8
PROJECT MANAGEMENT
Project Name: Developing a mobile based application "Ease in Tees" for LGBT group
Project Description: The mobile application is mainly developed so that the organization
can give tough competition to its competitors by attracting the customers by tracking the
visibility of the customers and giving them easy access. With the help of the mobile
application, excellent service is mainly provided to the customers.
Group No:
MIP7
Future ideas
. The mobile app is used for
selling clothes online.
Team Leader:
Project Sponsor:
Project start
date:05-03-19
Project end date:
20-05-19
Team Members Goals & Objectives
Name Roles The project goal is to undertake a project of
developing a mobile based application for the
organization for providing excellent service
to the customers
The objectives are:
 To develop a mobile app for the
organization
 To attract customers by increasing
visibility of the organization
 To enhance the revenue of the
organization
Anurupa Sponsor
Nafeez App Developer
Lijan Database Manager
Manu Facilitator
Aamir Business Analyst
Mission Statement Vision
The main mission of the organization is to
provide excellent service to the customers.
The main vision of the company is to attract
more customers to the organization.
Stakeholders
The stakeholders who are associated with the
project include:
 Government
 Shareholders
 Employees
 Customers
 Business

9
PROJECT MANAGEMENT
 Owners
Success Indicators To be one of the leading mobile application
in Australia within 1 year.
Figure 2: Sequence diagram
(Source: Created by Author)
3.1 Product deliverables
Market research
In each of the projects that is undertaken, it is found that we need to understand different
aspects of the business quite effectively. "Ease in Tees" is one of the mobile application that
undertakes some research before the initiation of the project.
MoSCoW Analysis
It is found that MoSCoW analysis is generally undertaken for determining the users that
require proper service.

10
PROJECT MANAGEMENT
Figure 3: MoSCoW
(Source: Created by Author)
SWOT analysis
SWOT analysis is mainly utilized for determining the strengths, weaknesses,
opportunities as well as threats that are connected with the project. The SWOT analysis is
generally done below:
Figure 4: SWOT analysis
(Source: Created by Author)
Determining the competitors
The competitors are needed to be properly identified with the help of different strategy.
The organization needs to adopt a proper strategy in order to determine the competitors.
Password ID
sharing
Wi-Fi
Visualization
Customer service
Customization
Registration
Login
M-Must
have
S-Should
have
W-Wont
have
C-could
have
Stregths
Excellent service
Proper navigation structure
Weaknesses
Poor content and images
Opportunities
Increased number of customers
Ebnchanced finacial revenue
Threats
Security issue
SWOT

11
PROJECT MANAGEMENT
4. Governance and reporting
4.1 Governance structure
4.1.1 Work breakdown structure
The WBS of the entire project is generally provided below:
Figure 5: Work Breakdown Structure
(Source: Created by Author)
The WBS that is given above are generally divided into a number of steps that are
elaborated below:
Initiation
 In this phase, proper justification is set and organizational resources required by the
project are analysed
 A thorough market analysis is undertaken in order for understanding the nature as well as
preferences about the target customers
Planning
 In the planning phase, proper meeting with the project team are generally arranged
 After then the project team generally creates a proper proposal for the project
 Developing proper agreement within the project for initiating the project
 After the agreement, the project stakeholders who will get engaged with the stakeholders
are arranged
 After the stakeholders are generally identified then the project team gets approval for the
project initiation.
Designing mobile application
 The idea for the project is generally determined for properly designing the mobile
application.
 The needs as well as requirements that the customer’s wants are generally reviewed
 After review activities, proper design for mobile application development is created
based on the objectives of the organization
 Undertaking cost-benefit analysis for the project for ensuring that the project is quite
feasible

12
PROJECT MANAGEMENT
 Analysis of proper budget are mainly needed for the proper development of the mobile
app.
 Proper meeting is mainly arranged for the team members of the project
 After the meeting, the project design generally receives approval
Coding
 In the coding phase, a proper prototype for the project is general developed
 In the development phase, the database for the entire project is generally developed
 After the database development, the code is validated
 After code validation, testing is generally undertaken for making sure that all the
functions of the mobile application are working effectively
 Proper optimization of the project after the project-testing phase.
Mobile application content creation
 In the mobile content creation phase, a proper navigation structure is developed for the
project
 Proper functionality of the mobile app is discussed.
User experience development
 In this particular phase, all the details that are required are generally updated on the
mobile app.
 The other information that is needed on the mobile application is also updated.
Definition of project requirement
 It is found that the mobile based application is properly accessed
 Software as well as hardware that is generally needed for the project are generally
updated
 The requirement of the project is mainly reviewed
Monitoring
 In the project monitoring phase, proper schedule for executing the auditing and
vulnerability assessment works are prepared
 A specific guideline and principle is set for reporting and maintenance
Closure phase
 The risks linked with the project are properly assessed
 The quality management is properly elaborated in the closure phase of the project

13
PROJECT MANAGEMENT
4.1.2 RACI matrix
Activities Project
manager
Project
planner
Application
manager
Developer Database
administrator
Coder Tester Quality
analyst
Financial
manager
Market analysis C A I
Meeting
with the project
team
C I R, A
Developing
the proposal for
the project
R A C I
Developing
project
agreement
R,A C, I
Determining
the project
stakeholders
R, A C
Getting
approval for the
project
R, C
Collecting
ideas
C, I R, A
Reviewing
the needs of the
client
C I R, A
Developing
design
R,A C I
Undertaking
feasibility study
R C I A
Undertaking
budget analysis
C I R,A
Undertaking
project meeting
R,A C I
Getting the
approval for the
design
C I R, A
Developing
prototype
C R,A I
Developing
database
C R,A I
Validation
of code
I C R,A
Testing C I R,A
Proper
optimization
I C R,A

14
PROJECT MANAGEMENT
Navigation
structure
development
I C R,A
Developing
functionalities
I R,A C
Details
update
I R,A C
Updating
information
associated in
mobile app
I R,A C
Accessing
mobile
application
I R,A C
Software
and hardware
estimation
Reviewing I C R,A
Assessing
the risks
I C R,A
Quality
management
I C R,A
Auditing and
reporting
C A I, R
Reviewing
the project
R,A I C

15
PROJECT MANAGEMENT
4.2 Stakeholder management
Stakeholder register
Name Position Internal/External Contact
Anurupa Project manager Internal <Please fill>
Nafeez Coder Internal <Please fill>
Lijan Application
manager
Internal <Please fill>
Manu Database
administrator
Internal <Please fill>
Aamir Tester External <Please fill>
Stakeholder management strategy
Role Interest Power Potential Management
Strategies
Project manager High High The project is responsible of
properly managing the
project.
Coder High Low The coder mainly creates as
well as executes code in
order to meet the objective
related to the project.
Application manager High High The application manager is
responsible for designing as
well as developing the
mobile based application
named Ease in Tees.

16
PROJECT MANAGEMENT
Database administrator High High The database administrator
helps in developing the
database for storing the data
and information.
Tester High Low Tester mainly conducts
proper testing for checking
whether the functionality of
the system is working
properly or not.
4.3 Communication plan
Communic
ation &
Deliverable
s
Delivery
Format or
Method of
Communicat
ion
Purpose of
Communicat
ion
Audience Owner Freque
ncy
Due Additional
Document
ation
Gathering
useful
information
Hard copy Improvement
of mobile
application
services
Team
manager
Project
manager
Monthly Last day
of every
month
Meeting
Conducting
interview
sessions
Recordings Proper
representation
of customer
requirements
Project
team
Sponsor
of the
project
3 days Monday Notes
Conducting
team
discussions
Report Resolution of
project team
issues and
concerns
Project
team
Project
manager
2
months
Friday Status of
the project

17
PROJECT MANAGEMENT
Project
monitoring
Softcopy Determinatio
n of relevant
problems
Project
team
Applicatio
n manager
Monthly Monday Records
5. Project controls
5.1 Schedule and dependencies management
5.1.1 Schedule of the project
As per the schedule that is developed, it is found that the entire project of mobile application
development will be developed successfully within the time-period of 56 days.
WBS Task Name Duration Start Finish
0
Development of mobile
based application Ease in
Tees for LGBT
community
56 days Tue 05-
03-19 Mon 20-05-19
1 Project initiation phase 8 days Tue 05-
03-19 Thu 14-03-19
1.1 Market analysis 2 days Tue 05-
03-19 Wed 06-03-19
1.2 Requirement analysis 3 days Thu 07-
03-19 Mon 11-03-19
1.3 Feasibility study 2 days Thu 07-
03-19 Fri 08-03-19
1.4 Project planning phase 2 days Tue 12-
03-19 Wed 13-03-19
1.5 Meeting with the
project team 3 days Tue 12-
03-19 Thu 14-03-19
1.6 Developing the
proposal for the project 2 days Mon 11-
03-19 Tue 12-03-19
1.7 Developing project
agreement 1 day Mon 11-
03-19 Mon 11-03-19
1.8 Determining the project
stakeholders 2 days Mon 11-
03-19 Tue 12-03-19
1.9 Getting approval for the
project 1 day Mon 11-
03-19 Mon 11-03-19
2 Designing mobile
application 6 days Tue 12-
03-19 Tue 19-03-19
2.1 Ideas collection 2 days Tue 12-
03-19 Wed 13-03-19
2.2 Reviewing needs 3 days Tue 12- Thu 14-03-19

18
PROJECT MANAGEMENT
03-19
2.3 Design development 3 days Tue 12-
03-19 Thu 14-03-19
2.4 Feasibility study 2 days Thu 14-
03-19 Fri 15-03-19
2.5 Budget analysis 2 days Thu 14-
03-19 Fri 15-03-19
2.6 Project meeting 3 days Fri 15-03-
19 Tue 19-03-19
2.7 Getting approval for the
design 2 days Fri 15-03-
19 Mon 18-03-19
3 Coding 19 days Mon 18-
03-19 Thu 11-04-19
3.1 Prototype development 7 days Mon 18-
03-19 Tue 26-03-19
3.2 Developing database 8 days Mon 18-
03-19 Wed 27-03-19
3.3 Code validation 12 days Wed 27-
03-19 Thu 11-04-19
3.4 Proper testing 10 days Wed 27-
03-19 Tue 09-04-19
3.5 Proper optimization 9 days Wed 27-
03-19 Mon 08-04-19
4 Application content 10 days Tue 09-
04-19 Mon 22-04-19
4.1 Navigation structure 10 days Tue 09-
04-19 Mon 22-04-19
4.2 Functionality
development 9 days Tue 09-
04-19 Fri 19-04-19
4.3 User experience
development 10 days Tue 09-
04-19 Mon 22-04-19
5 Details update 17 days Tue 23-
04-19 Wed 15-05-19
5.1 Updating information
on the mobile app 10 days Tue 23-
04-19 Mon 06-05-19
5.2 Definition of project
requirement 8 days Tue 23-
04-19 Thu 02-05-19
5.3 Getting access of
mobile app 9 days Fri 03-05-
19 Wed 15-05-19
5.4 Estimation of hardware
and software 6 days Fri 03-05-
19 Fri 10-05-19

19
PROJECT MANAGEMENT
5.5 Reviewing 4 days Fri 03-05-
19 Wed 08-05-19
6 Project monitoring
phase 4 days Thu 09-
05-19 Tue 14-05-19
6.1 Regular audit 4 days Thu 09-
05-19 Tue 14-05-19
6.2 Maintenance and
reporting 4 days Thu 09-
05-19 Tue 14-05-19
7 Closure phase 4 days Wed 15-
05-19 Mon 20-05-19
7.1 Assessing the risks 4 days Wed 15-
05-19 Mon 20-05-19
7.2 Quality management 3 days Wed 15-
05-19 Fri 17-05-19
7.3 Reviewing the project 3 days Wed 15-
05-19 Fri 17-05-19
5.1.2 Schedule management
It is found that the entire schedule, and the dependencies of the project, is managed with
the help of the Gantt chart. The Gantt is well-defined as the graphical illustration that generally
contains information about the project tasks, durations as well as starting and finishing date of
project including the predecessors. Thus, the Gantt chart that is provided below generally reflects
the predecessor or the dependencies of the project quite effectively.

20
PROJECT MANAGEMENT
Figure 6: Gantt chart reflecting the predecessors
(Source: Created by Author)
The gantt chart is reflecting the 1st phase of the project involving the market analysis and
requirement analysis which is generally completed in 5 days.
Figure 7: Gantt chart reflecting project initiation phase

21
PROJECT MANAGEMENT
(Source: Created by Author)
From the above Gantt chart, it is reflected that the planning phase of the project generally
gets finished within 3 days of time. In the planning phase, meeting with the team is done in 3
days and then a proposal for the project is developed in 2 days whereas 2 days are used for
identifying the stakeholders as well as for getting the approval for the initiation of the project.
Figure 8: Gantt chart reflecting the planning phase
(Source: Created by Author)
It is found that the next phase is the mobile application design phase which generally
gets completed within the time period of 6 days. In the first 2 days, a proper idea about the
mobile design is collected and the requirement of the clients are reviewed which further takes
3 more days. After then, the design for the mobile application application is mainly created in
3 days whereas the feasibility study is conducted within 2 days of time. Additionally, meeting
with the project team are generally done for one day in order to receive approval for the
design project.
Figure 9: Gantt chart reflecting web application phase
(Source: Created by Author)
The Gantt chart further reflects that the 4th phase of the project is the coding phase that
gets completed within 19 days of time. In the coding phase, the prototype is developed in 7
days, the proper database is developed in 8 days whereas them ode validation is generally
done within 4 days of time. Furthermore, for testing as well as optimization, further 10 days
are generally are utilized.

22
PROJECT MANAGEMENT
Figure 10: Gantt chart reflecting the coding phase
(Source: Created by Author)
In the fifth phase of the project, web content creation will be done within 10 days of
time. It is found that the navigation structure will be developed within 10 days of time
whereas the site content pages are generally developed within the other 9 days. It is found
that the user experience development is 10 days.
Figure 11: Gantt chart reflecting mobile application content and user experience
development phase
(Source: Created by Author)
The project mniitoring phase will get completed within 4 days of time. It is found that
both regular audit and maintainence gets completed simultaneosly. Additionally, it is found
that the closure phase get completed within 4 days where quality access, quality management
as well as pojet review runs simultaneously.
Figure 12: Gantt chart reflecting project monitoring and closure phase
(Source: Created by Author)

23
PROJECT MANAGEMENT
5.2 Financial management
The financial plan that is generally provided below reflects that the development of the
mobile based application for the organization will be developed within the budget of $80,768.
The budget that is required in each phase of the project is reflected below:
Activities
Hou
rs Type
$/
hour
Direct
cost Type
Indirect
cost Total cost
Market analysis 10 Salary 32
$
320.00
$
-
$
320.00
Requirement
analysis 10 Salary 3
$
30.00
$
-
$
30.00
Feasibility
analysis 12 Salary 35
$
420.00
$
-
$
420.00
Meeting
with the project
team 32 Salary 40
$
1,280.00
$
-
$
1,280.00
Developing
the proposal for
the project 16 Salary 35
$
560.00
$
-
$
560.00
Developing
project
agreement 16 Salary 45
$
720.00
$
-
$
720.00
Determining
the project
stakeholders 24 Salary 40
$
960.00
$
-
$
960.00
Getting
approval for the
project 24 Salary 45
$
1,080.00
$
-
$
1,080.00
Collecting
ideas 16 Salary 35
$
560.00
$
-
$
560.00
Reviewing
the needs of the
client 40 Salary 40
$
1,600.00
$
-
$
1,600.00
Developing
design 16 Salary 45
$
720.00
$
-
$
720.00
Undertaking
a feasibility
study 16 Salary 45
$
720.00
$
-
$
720.00
Undertaking
budget analysis 8 Salary 40
$
320.00
$
-
$
320.00
Undertaking
project meeting 8 Salary 52
$
416.00
$
-
$
416.00
Getting the
approval for the
design 8 Salary 42
$
336.00
Materi
al
$
30,000.00
$
30,336.00
Developing
prototype 40
Salary
Materi 46
$
1,840.00
$
-
$
1,840.00

24
PROJECT MANAGEMENT
al
Developing
database 48 Salary 45
$
2,160.00
$
-
$
2,160.00
Validation
of code 32 Salary 40
$
1,280.00
$
-
$
1,280.00
Testing
24
Salary
Additio
nal cost 45
$
1,080.00
Additio
nal
$
20,000.00
$
21,080.00
Proper
optimization 24 Salary 40
$
960.00
$
-
$
960.00
Navigation
structure
development 40 Salary 42
$
1,680.00
$
-
$
1,680.00
Site content
page creation 40 Salary 43
$
1,720.00
$
-
$
1,720.00
Details
update 32 Salary 45
$
1,440.00
$
-
$
1,440.00
Updating
information
associated with
the mobile app 40 Salary 40
$
1,600.00
$
-
$
1,600.00
Accessing
web application 32 Salary 52
$
1,664.00
$
-
$
1,664.00
Software
and hardware
estimation 40 Salary 47
$
1,880.00
$
-
$
1,880.00
Reviewing 32 Salary 40
$
1,280.00
$
-
$
1,280.00
Regular audit 20 Salary 35
$
700.00
$
-
Maintenance
and reporting 9 Salary 35
$
315.00
$
-
Assessing
the risks 32 Salary 40
$
1,280.00
$
-
$
1,280.00
Quality
management 24 Salary 40
$
960.00
$
-
$
960.00
Reviewing
the project 16 Salary 42
$
672.00
$
-
$
672.00
$
32,553.0
0
$
50,000.00
$
80,768.00

25
PROJECT MANAGEMENT
5.3 Risk register
ID Risk Description Category Root cause Triggers Response Owner Probability Impact Status
1 Defect in
the
application
It is found
that due to
improper
testing, the
defect in the
app is
identified
later and due
to which the
mobile
application is
not working
properly.
Project
risk
Due to
improper
testing
Creates
problems in
managing
the operation
of the
organization
It is quite
important to
undertake to
test quite
effectively for
lowering the
defects in the
mobile based
application.
Application
manager
Major Likely N
2 Data Breach Due to a data
breach, the
data of the
organization
can be
assessed by
the outsiders
and as a
result, they
can face a
number of
issues.
Security
risk
The data
breach
mainly
occurs due to
the absence
of proper
security
measures.
It is
generally
creating a
number of
ethical issues
including the
loss of
personal
information
of the
clients.
It is quite
necessary for
the
organization to
adopt the
necessary steps
for avoiding
the security
measures.
Application
manager
Catastrophic Almost
certain
Y
3 Budget
failure
The problem
of budget
failure can
occur due to
improper
budget
management
of the project
budget that
further can
cause
financial
issues.
Budget
risk
It generally
occurs due to
inappropriate
tracking of
the project
budget.
It generally
can cause an
obstruction
within the
budget of the
project.
It is very much
necessary for
the
organization to
track the
budget of the
project quite
effectively for
avoiding the
financial issues
within the
project.
Financial
manager
Catastrophic Likely N
4 Improper If the Project It mainly Due to It is quite Researcher Moderate Likely N

26
PROJECT MANAGEMENT
information
gathering
information
that is
associated
with the
project is not
gathered then
which can
raise number
of issues in
gathering
data and
important
information.
risk occurs if the
business
analyst who
is
undertaking
the research
is not very
much
experienced.
inappropriate
information,
it is quite
difficult to
develop the
project quite
effectively.
necessary to
hire
experienced
researchers for
gathering the
information
related to the
research
effectively.
5 Cyber attack Cyber-
attacks
occurs when
the hackers
generally
damage the
network
Security
risk
It mainly
occurs due to
the virus.
It generally
causes
hacking of
data as well
as
information
Implementation
of firewall is
helpful in
resolving the
cyber-attack
risks as well as
challenges
Application
manager
Major Possible Y
6 Improper
management
Due to
improper
management,
the project
manager
generally
faces
problems in
successful
achievement
of the project
objectives.
Project
risk
It mainly
occurs due to
the improper
use of
project
management
strategies.
It generally
can cause a
number of
issues and
challenges in
finishing the
project.
The problem
that is
associated with
improper
management
can be resolved
with the
implementation
of proper
management
strategies
within the
project.
Project
manager
Moderate Possible N
7 Lack skill If the team
members are
inexperienced
then they
faces issues
in successful
project
management
Project
risk
It mainly
causes a
number of
challenges in
managing
the project
effectively.
It can cause
a number of
problems in
successfully
completing
the project
on time.
The problem
that is
associated with
the skill should
be resolved by
hiring team
members who
are skilled as
well as
experienced.
Manager Minor Almost
certain
Y

27
PROJECT MANAGEMENT
Figure 13: Fish bone diagram for dedaline issue
(Source: Created by Author)
Figure 14: Fish bone diagram for software defects
(Source: Created by Author)

28
PROJECT MANAGEMENT
Likelihood
Consequences
Catastrophic
(Cat)
Major
(Maj)
Moderate
(Mod)
Minor
(Min)
Insignificant
(Ins)
Almost
Certain
(AC)
Data Breach Improper
skill
Likely
(L)
Budget failure Defect in the
mobile app
Improper
information
gathering
Possible
(P)
Cyber attack Improper
management
Unlikely
(U)
Rare
(R)
5.4 Quality management
In every project, quality management plays an important part. Flexibility, accuracy,
performance, security, reliability, functionality are some parts of quality management which
help the firm to provide quick response to the clients.
The qualitative analysis of the performance of the project
 Regular updates and feedbacks need to be given on the status of work.
 The goals must be shared and in order to achieve that proper management should be
used.
 The employees should be motivated by acknowledging their good work and awarded
for performing well.
 The stakeholders of the project should have proper communication on the project.
 Skill development programs can be inculcated to improve the skill of the employees.
The Quality of performance of the mobile app
Unresponsive and interruptive applications can be eliminated by planning and
conducting tests to determine the quality of the mobile based application. While making the test
designs real-time facts and situations should be referred to.
 Applications behavior needs to be tested in areas with low connectivity.
 Proper working of the mobile based application along with different networking
setups such as 3G, Wi-Fi, and hotspot.
 Mobile based application behavior should be analyzed in areas outside the range of
the connectivity area.
The project’s reliability is one main element that should be considered and the measures that
can be taken are given below:

29
PROJECT MANAGEMENT
 The project requires to have qualified and skilled employees.
 Recent hardware and updated software must be used in the project.
 Holding regular meetings to keep an update on the project’s quality.
 Regular inspection will help ensure the safety of the project.
 Strict procedures to be followed on a knowledge management system.
 A reliable system must be followed to collect data.
A mobile based application related security plays a vital part in the project. With
the increasing rate of cyber-attacks, it is essential to secure the project from attacks. The
mobile based application can be shielded from the attacks by conducting significant risk
management at the beginning of the project. Strict policies must be implemented and the data
security ensured by strengthening the infrastructure. The accuracy of the project is an essential
factor and should be maintained. Mobile based security is a major concern and data theft is the
most predominant one. In order to ensure mobile based security, the project must go through
certain steps such as:
 Before developing the mobile application, security issues must be tested.
 To prevent unauthorized access the mobile based application should be selective to
links and their relocation, timestamps and key logs.
 The mobile based application should not reveal users' personal information and
when required warnings should be sent.
 The problems relating to instant messaging, abrupt download and transferring of
data should be worked upon.
Flexible User Experience
 The orientations of the mobile based application and the different controls of the
application can be adjusted when required.
 The home page of the application should appear in 0.1ms.
 The search option is available on the application
 The mobile application should be responsive and user intervention should be least.
 The mobile based provides real-time notifications.
Compatibility of the mobile app
 The mobile application is compatible with respect to Android and iOS devices.
 Ease in Tees can successfully run sharing the same environment with other applications.
5.5 Project monitoring and control
As an agile approach has been chosen for the project, in order to keep a track of
the work a project management tool named “Monday.com” is being used. The tool keeps a
record of the task assigned to the members and it also helps them to raise any query faced in
the task. The project manager can access the back end and ensure that the tasks are being
completed within the time given and check on the quality of the task and consider it for
rework. It is just to track the work status of each task and a significant implication to get a
hold on the project. In the process of the development of the mobile app PDCA (Plan-Do-
Check-Act/Adjust) methodology has been used that owes its roots to TQM (Total Quality

30
PROJECT MANAGEMENT
Management) Method. The PDCA theory is applied when it is found that a certain task is not
completed succumbing to particular problems. The PDCA methodology follows certain steps
and they are as follows:
 Plan- It is the first step where the problem is identified as an opportunity, a hypothesis
is made about its occurrence, and then a test is done.
 Do- Tests are performed on a small scale basis so that specific results are obtained.
 Check- The third step includes checking the effectiveness of the results that have been
recorded and the nature of the hypothesis made in step 1 is judged.
 Act/Adjust- The last step is to determine whether the solution is relevant to the problem
and if found correct, the solution is implemented in the project. In case the solution is
found irrelevant then it is not implemented in the ongoing project.
Figure 15: The PDCA diagram
(Source: Martens and Carvalho, 2017)
The PDCA methodology is used in the project to ensure the quality of the ongoing
project and the methodology helps to take prompt action when the project is facing problems.
The process also creates new opportunities based on the performance of the project. The
“Ease in Tees” mobile app is ensuring to avoid any security breach and by using the
techniques such as PDCA the mobile based application is strictly keeping a check on the
advancement of the work in the project and any fault is addressed as soon as possible.
5.6 Lessons learnt
From this entire project, we have gained skills as well as knowledge related to project
management. It is found that proper experience in the project is mainly gained due to being
PDCA
Diagram
Plan
Do
Check
Act

31
PROJECT MANAGEMENT
engaged with the work of the project. Moreover, the paper also taught the importance of
project design as well as report application.
 Proper technical knowledge is generally gained due to the utilization of use case
diagram that is generally created for the project.
 Proper break down of the project activities into the smaller task due to the utilization of
WBS structure
 Proper skill, as well as knowledge, is generally gained related to steps which are
generally beneficial in risk mitigation
 With the help of the project schedule, proper knowledge about the project management
for finishing the project on time.
 Proper knowledge about the requirements are generally gained due to the use of project
scope management
6. Contribution by the team members
Student Name Student ID Contributed Work
<Please fill> <Please fill> <Please fill>
<Please fill> <Please fill> <Please fill>
<Please fill> <Please fill> <Please fill>
<Please fill> <Please fill> <Please fill>

32
PROJECT MANAGEMENT
Bibliography
Andersen, E.S., 2016. Do project managers have different perspectives on project
management?. International Journal of Project Management, 34(1), pp.58-65.
Badewi, A., 2016. The impact of project management (PM) and benefits management (BM)
practices on project success: Towards developing a project benefits governance
framework. International Journal of Project Management, 34(4), pp.761-778.
Bjorvatn, T. and Wald, A., 2018. Project complexity and team-level absorptive capacity as drivers
of project management performance. International Journal of Project Management, 36(6), pp.876-
888.
Bucero, A. and Englund, R.L., 2015, October. Project sponsorship: Achieving management
commitment for project success. Project Management Institute.
Conforto, E.C., Amaral, D.C., da Silva, S.L., Di Felippo, A. and Kamikawachi, D.S.L., 2016. The
agility construct on project management theory. International Journal of Project
Management, 34(4), pp.660-674.
De Carvalho, M.M., Patah, L.A. and de Souza Bido, D., 2015. Project management and its effects
on project success: Cross-country and cross-industry comparisons. International Journal of
Project Management, 33(7), pp.1509-1522.
Ekrot, B., Kock, A. and Gemünden, H.G., 2016. Retaining project management competence—
Antecedents and consequences. International Journal of Project Management, 34(2), pp.145-157.
Eskerod, P., Huemann, M. and Savage, G., 2015. Project stakeholder management—Past and
present. Project Management Journal, 46(6), pp.6-14.
Hoda, R. and Murugesan, L.K., 2016. Multi-level agile project management challenges: A self-
organizing team perspective. Journal of Systems and Software, 117, pp.245-257.
Hornstein, H.A., 2015. The integration of project management and organizational change
management is now a necessity. International Journal of Project Management, 33(2), pp.291-298.
Joslin, R. and Müller, R., 2015. Relationships between a project management methodology and
project success in different project governance contexts. International Journal of Project
Management, 33(6), pp.1377-1392.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Kerzner, H., 2017. Project management metrics, KPIs, and dashboards: a guide to measuring and
monitoring project performance. John Wiley & Sons.

33
PROJECT MANAGEMENT
Kivilä, J., Martinsuo, M. and Vuorinen, L., 2017. Sustainable project management through project
control in infrastructure projects. International Journal of Project Management, 35(6), pp.1167-
1183.
Martens, M.L. and Carvalho, M.M., 2017. Key factors of sustainability in project management
context: A survey exploring the project managers' perspective. International Journal of Project
Management, 35(6), pp.1084-1102.
Meng, X. and Boyd, P., 2017. The role of the project manager in relationship
management. International Journal of Project Management, 35(5), pp.717-728.
Padalkar, M. and Gopinath, S., 2016. Six decades of project management research: Thematic
trends and future opportunities. International Journal of Project Management, 34(7), pp.1305-
1321.
Papke-Shields, K.E. and Boyer-Wright, K.M., 2017. Strategic planning characteristics applied to
project management. International Journal of Project Management, 35(2), pp.169-179.
Qazi, A., Quigley, J., Dickson, A. and Kirytopoulos, K., 2016. Project Complexity and Risk
Management (ProCRiM): Towards modelling project complexity driven risk paths in construction
projects. International Journal of Project Management, 34(7), pp.1183-1198.
Ramazani, J. and Jergeas, G., 2015. Project managers and the journey from good to great: The
benefits of investment in project management training and education. International Journal of
Project Management, 33(1), pp.41-52.
Samset, K. and Volden, G.H., 2016. Front-end definition of projects: Ten paradoxes and some
reflections regarding project management and project governance. International Journal of
Project Management, 34(2), pp.297-313.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Sunder M, V., 2016. Lean Six Sigma project management–a stakeholder management
perspective. The TQM Journal, 28(1), pp.132-150.
Svejvig, P. and Andersen, P., 2015. Rethinking project management: A structured literature review
with a critical look at the brave new world. International Journal of Project Management, 33(2),
pp.278-290.
Zheng, X., Le, Y., Chan, A.P., Hu, Y. and Li, Y., 2016. Review of the application of social
network analysis (SNA) in construction project management research. International journal of
project management, 34(7), pp.1214-1225.