Project Management: Development of Mobile Application 'Ease in Tees'

This project management assignment focuses on the development of a mobile application, named 'Ease in Tees,' targeted towards the LGBT community. The project encompasses a detailed analysis of project scope, assumptions, and constraints, alongside key deliverables. The assignment utilizes an agile project management approach, detailing use case scenarios, system requirements, and proposed deliverables. It presents a comprehensive project charter, outlining project objectives, roles, and responsibilities. Furthermore, the assignment covers governance and reporting structures, including a work breakdown structure and RACI matrix, along with stakeholder and communication plans. Project controls are addressed through schedule and financial management, a risk register, and quality management strategies. The assignment concludes with a section on team member contributions and lessons learned, providing a holistic overview of the mobile app development process.

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