Mobile App Development Project Plan

This assignment details the development of a mobile application. It outlines a comprehensive project plan spanning various stages, including requirements gathering, design, development, testing, deployment, and post-launch maintenance. The plan includes a breakdown of tasks, estimated durations, required resources, and potential risks. A Gantt chart and network diagram are provided to visualize the project schedule and dependencies.

Project Management

TABLE OF CONTENTS
Outline of the project...................................................................................................................1
Stating the functional and non-functional requirements of project.............................................1
Presenting the skills and expertise of project team members......................................................2
Development of project plan.......................................................................................................2
Determining project scope...........................................................................................................4
Estimating the time of project......................................................................................................4
Planning about the quality of project...........................................................................................5
Stakeholder analysis of the project..............................................................................................5
Stating the plan regarding the communication of project............................................................5
Risk management plan.................................................................................................................6
Mention plan for project deployment..........................................................................................6
WBS by using project management............................................................................................6
Gantt chart and network diagram................................................................................................9
Post reviews and recommendations...........................................................................................12
REFERENCES..............................................................................................................................13

Outline of the project
On the basis of cited case situation, project has been chosen from the telecommunication
area regarding the launching of an application namely ‘Info’. Such application will provide high
level of assistance to the customers in getting information about the hotel & restaurants and
transportation modes along with the timings as well as credit rating. Hence, project pertaining to
the launching of an application will start on 1st October 2017 and end on 31st May 2018. Thus,
Telstra will take 8 months for launching such application. Goals and objectives of the concerned
project are enumerated below:
 To capture the large market share by providing customers with mobile app that contains
unique features.
 To explore the business operations and thereby maximize both productivity as well as
profitability.
Stating the functional and non-functional requirements of project
Functional requirements of project: As per the launch of this fruitful app there will
various functional requirements in making project.
 Effective organizational rules
 Execution of transactions, correction as well as adjustments.
 Proper authentication
 Auditing of operations
 Use of historical information (Kerzner, 2013)
 Legal framework with adequate regulatory
Non- functional requirements of project: It acquires all the remaining tasks that must be
covered in filling the project
 Capability of project

 Use of reliable information
 Performance of team members
 Security of information or data (Burke, 2013)
 Measuring the performances
Presenting the skills and expertise of project team members
In order to accomplish project within the suitable time frame project team 4 people has
been made who possess following skills and expertise:
 Effective communication
 Co-ordination
 Delegation of roles and responsibility
 Technical documentation (Meredith & Mantel Jr, 2011)
 Risk management
 Problem solving
Development of project plan
Task
Mod
e
Task Name Duratio
n Start Finish Predecesso
rs
Early
Start
Early
Finish
Late
Start
Late
Finish
Tota
l
Slac
k
Initiation 60 days Thu
9/28/17
Wed
12/20/1
7
Thu
9/28/17
Wed
12/20/1
7
Thu
9/28/17
Fri
2/9/18
0
days
1
Assessing
ideas for
launching a
mobile app
through
investigation
18 days Thu
9/28/17
Mon
10/23/1
7
Thu
9/28/17
Mon
10/23/1
7
Thu
9/28/17
Mon
10/23/1
7
0
days
2 Setting of
project goals
and
10 days Thu
9/28/17
Wed
10/11/1
7
Thu
9/28/17
Wed
10/11/1
7
Thu
11/9/17
Wed
11/22/1
7
30
days

objectives
3
Defining
scope of the
project
5 days
Tue
10/24/1
7
Mon
10/30/1
7
2
Tue
10/24/1
7
Mon
10/30/1
7
Mon
2/5/18
Fri
2/9/18
74
days
Planning 50 days
Thu
10/12/1
7
Wed
12/20/1
7
Thu
10/12/1
7
Wed
12/20/1
7
Tue
10/24/1
7
Fri
2/9/18
8
days
4
Development
of
communicati
on plan
15 days
Tue
10/24/1
7
Mon
11/13/1
7
2
Tue
10/24/1
7
Mon
11/13/1
7
Tue
10/24/1
7
Mon
11/13/1
7
0
days
5
Making
risk
management
plan
16 days
Tue
10/24/1
7
Tue
11/14/1
7
2
Tue
10/24/1
7
Tue
11/14/1
7
Mon
11/20/1
7
Mon
12/11/1
7
19
days
6
Making
estimation of
time
7 days
Thu
10/12/1
7
Fri
10/20/1
7
3
Thu
10/12/1
7
Fri
10/20/1
7
Thu
2/1/18
Fri
2/9/18
80
days
7
Setting
standards for
quality
17 days
Tue
10/24/1
7
Wed
11/15/1
7
2,3
Tue
10/24/1
7
Wed
11/15/1
7
Thu
11/23/1
7
Fri
12/15/1
7
22
days
8
Determining
devices need
to build for
mobile app
24 days
Tue
11/14/1
7
Fri
12/15/1
7
6
Tue
11/14/1
7
Fri
12/15/1
7
Tue
11/14/1
7
Fri
12/15/1
7
0
days
9
Technical
architectural
by project
team
26 days
Wed
11/15/1
7
Wed
12/20/1
7
6,7
Wed
11/15/1
7
Wed
12/20/1
7
Tue
12/12/1
7
Tue
1/16/18
19
days
Execution 42 days
Thu
11/16/1
7
Fri
1/12/18
Thu
11/16/1
7
Fri
1/12/18
Mon
12/18/1
7
Fri
2/9/18
20
days
10
Development
of prototype
by using agile
methodology
22 days
Thu
11/16/1
7
Fri
12/15/1
7
9
Thu
11/16/1
7
Fri
12/15/1
7
Thu
12/21/1
7
Fri
1/19/18
25
days
11
Assessment
of technical
feasibility
20 days
Mon
12/18/1
7
Fri
1/12/18 9,10
Mon
12/18/1
7
Fri
1/12/18
Mon
12/18/1
7
Fri
1/12/18
0
days
12 Testing
mobile app
by using
10 days Thu
12/21/1
7
Wed
1/3/18
11 Thu
12/21/1
7
Wed
1/3/18
Wed
1/17/18
Tue
1/30/18
19
days

UAT and beta
method
13
Launching
a mobile app 10 days
Thu
12/21/1
7
Wed
1/3/18 11
Thu
12/21/1
7
Wed
1/3/18
Mon
1/29/18
Fri
2/9/18
27
days
Closure of
the project 40 days
Mon
12/18/1
7
Fri
2/9/18
Mon
12/18/1
7
Fri
2/9/18
Mon
1/15/18
Fri
2/9/18
0
days
14
Monitoring
the success of
Mobile app
and assessing
difficulties
which are
facing by the
user through
feedback
15 days
Mon
12/18/1
7
Fri
1/5/18 13
Mon
12/18/1
7
Fri
1/5/18
Mon
1/22/18
Fri
2/9/18
25
days
15
Making
appropriate
changes in
the app as per
the feedback
provided by
customers
20 days Mon
1/15/18
Fri
2/9/18 14 Mon
1/15/18
Fri
2/9/18
Mon
1/15/18
Fri
2/9/18
0
days
16
Re-
launching 8 days Thu
1/4/18
Mon
1/15/18 15 Thu
1/4/18
Mon
1/15/18
Wed
1/31/18
Fri
2/9/18
19
days
Determining project scope
By undertaking the project of launching a mobile application team member want to
enhance the customer base as well as sales of Telstra to a great extent. Thus, by undertaking the
standardized process from initiating and testing to the execution business unit would become
able to meet the project goals and objectives (Schwalbe, 2015). Thus, scope of the project is
wide which in turn helps firm in building or sustaining competitive edge over others.
Estimating the time of project
For the completion of project there will be requirement of 243 days, that means at least 8
months to be required for launch of this application. Team efforts can be made on the basis of
collecting the data from various locations and seeking the requirements of the individuals. The
initiation of the project needed 60 days for the completion of generating data through sources.

Setting goals and vision for the launch of project as well as planning the suitable decisions for
the better marketing of product. Plans were made in accordance with advertising the launch of
app as well as estimating the costs of the project (Wysocki, 2011). The promotion of company
and its application took the duration of 50 days. Execution of such project requires 42 days as
well as the closer for 40 days.
Planning about the quality of project
Assessment must contain all the legal requirements of consumers in context with the
launch of this application. There must include the features which will be fruitful for them as well
as satisfy them. Team of 4 members has made the fruitful plans in the completion of these tasks.
Quality and the best part of project is that it has been completed within the expected time period
and with the optimum results (Walker, 2015). Members have made favorable plans for launching
the application that contains information regarding nearby restaurant and rest lounge of users. It
has the fruitful results when it was initially used by some consumers and it has the positive
results.
Stakeholder analysis of the project
Stakeholders of company Telstra such as managers, board of directors as well as
consumers has shown positive response over these projects. They have given their positive
response to managers such as they show their interest in the launch of this application. Many of
clients found the application as a useful tool specially when they make tours and travel to the
unknown places. It been very easy for them to easily fetch nearby restaurants (De Bakker,
Boonstra & Wortmann, 2010). They will be able to book such hotels and restaurant in advance as
well as fetch the menu card to decide the meals they preferred. With the help of these favorable
responses investors has shown their keen interest in making the investments.
Stating the plan regarding the communication of project
Plan will be discussed by the members of this project through various communication
tools like mails, calls, messages as well as personal interactions. These helps in making the
coordination in the completion of project on expected time period. It helps them in switching the
plans or decisions as per requirements or need of time (Jun, Qiuzhen & Qingguo, 2011). No
communication barrier helped in making the favorable plans as well as helps in the completion
of project. There has been adoption of new plans or techniques as per requirements of project.

Risk management plan
There will be threat of losing the data regarding launch of this application. It is very
essential asset for organization so this will be discussed with the managers as well as team
members. This application must be made with proper licensing as well as consideration of
legality (Caniëls & Bakens, 2012). If there is any loophole into the functioning of this app in
devices than there must be prompt action against the errors and must be cured on favorable time
duration.
Mention plan for project deployment
Deployment is containing with the several linked plans or stages with the project. It helps
team’s members in making the innovative changes in plans before the completion of project. If
there is any theft of data related with the application then there must be preparation of such
software which will protect application from theft. Plans must be discussed with the managers
and supportive organizational professionals. Thus, they will be helpful in the deployment of
project. There must be use of tracking devices that helps in catching theft or hacker of such plan.
WBS by using project management
It denoted as the work to be divided as per skills or capacity of members. It contains the
plan which has detailed information about each activity and task to be done several individuals.
Task Mode Task Name Duration Predecessors WBS
Initiation 60 days 1
1
Assessing ideas for
launching a mobile app
through investigation
18 days 1.1
2
Setting of project goals and
objectives 10 days 1.2
3
Defining scope of the
project 5 days 2 1.3
Planning 50 days 1.4
4
Development of
communication plan 15 days 2 1.4.1
5
Making risk management
plan 16 days 2 1.4.2
6 Making estimation of time 7 days 3 1.4.3
7
Setting standards for
quality 17 days 2,3 1.4.4

8
Determining devices need
to build for mobile app 24 days 6 1.4.5
9
Technical architectural by
project team 26 days 6,7 1.4.6
Execution 42 days 2
10
Development of prototype
by using agile methodology 22 days 9 2.1
11
Assessment of technical
feasibility 20 days 9,10 2.2
12
Testing mobile app by using
UAT and beta method 10 days 11 2.3
13 Launching a mobile app 10 days 11 2.4
Closure of the project 40 days 3
14
Monitoring the success of
Mobile app and assessing
difficulties which are facing
by the user through feedback
15 days 13 3.1
15
Making appropriate changes
in the app as per the feedback
provided by customers
20 days 14 3.2
16 Re-launching 8 days 15 3.3

Gantt chart and network diagram
Gantt chart

Network diagram

Post reviews and recommendations
It is recommended to the firm to lay emphasis on the aspect of continuous monitoring. By
doing this, project team would become able to do necessary changes in the mobile app within the
suitable time frame.

REFERENCES
Books and Journals
Burke, R., (2013). Project management: planning and control techniques. New Jersey, USA.
Caniëls, M. C. & Bakens, R. J., (2012). The effects of Project Management Information Systems
on decision making in a multi project environment.International Journal of Project
Management. 30(2). pp.162-175.
De Bakker, K., Boonstra, A. & Wortmann, H., (2010). Does risk management contribute to IT
project success? A meta-analysis of empirical evidence. International Journal of Project
Management. 28(5). pp.493-503.
Jun, L., Qiuzhen, W. & Qingguo, M., (2011). The effects of project uncertainty and risk
management on IS development project performance: A vendor perspective. International
Journal of Project Management. 29(7). pp.923-933.
Kerzner, H.R., (2013). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Meredith, J. R. & Mantel Jr, S.J., (2011). Project management: a managerial approach. John
Wiley & Sons.
Schwalbe, K., (2015). Information technology project management. Cengage Learning.
Walker, A., (2015). Project management in construction. John Wiley & Sons.
Wysocki, R. K., (2011). Effective project management: traditional, agile, extreme. John Wiley &
Sons.