Project Management Plan for Mobile Application Development

The document is a Project Management Plan (PMP) that is prepared for a software development project. The project is the development of a mobile application for a banking firm. The mobile application will be developed for iOS as well as Android platforms. The PMP includes the guidelines for the management of various project areas.

Mobile Application Development
<Course Number and Name>
Prepared By
<Names>
<Date>
Example – Communications Plan v1.0.1 Page 1

1. Executive Summary..........................................................................................4
1.1 Introduction....................................................................................................................... 4
1.2 Purpose............................................................................................................................ 4
1.3 Scope................................................................................................................................ 4
2. Project Overview...............................................................................................5
2.1...Project Description......................................................................................................... 5
2.2...Problem Statement......................................................................................................... 5
2.3...Goals.............................................................................................................................. 5
2.4...Project Background........................................................................................................ 5
2.5...Product Objectives......................................................................................................... 5
2.6...Assumptions, Constraints and Dependencies................................................................6
2.7...Project Deliverables........................................................................................................ 6
2.8...Schedule and Budget Summary.....................................................................................6
2.9...Evolution of the Plan....................................................................................................... 6
2.10 Definitions and Acronyms............................................................................................... 6
3.Stakeholder Register.........................................................................................8
4. Schedule Component.......................................................................................9
5. Resource Plan with RACI...............................................................................11
5.1 Overview/Purpose.......................................................................................................... 11
5.2 Resourcing Strategy & Assumption................................................................................11
5.3 Resourcing Development................................................................................................ 11
6. Risk Management Plan...................................................................................12
6.1...Review of Risk Management Plan................................................................................12
6.2...Risk Identification......................................................................................................... 12
7. Communications Plan....................................................................................13
Example – Communications Plan v1.0.1 Page 2

8. Procurement....................................................................................................16
9. Cost..................................................................................................................17
9.1 Introduction..................................................................................................................... 17
9.2 Estimate Cost................................................................................................................. 17
9.3 Contingency Reserve Project Purpose or Justification...................................................17
9.4 Budget............................................................................................................................ 17
9.5 Cost Control and Monitoring........................................................................................... 18
9.6 Performance Monitoring.................................................................................................. 18
9.7 Project Reports............................................................................................................... 18
9.8 Cost Change Control...................................................................................................... 18
9.9 Microsoft Project Deliverables........................................................................................18
9.9.1 Project Budget............................................................................................................. 18
9.9.2 Microsoft Performance Report.....................................................................................18
10.Integrated Change Control...........................................................................21
10.1 Change Control Narrative.............................................................................................21
10.2 Project Change Control Narrative.................................................................................21
10.3 Project Change Control Flowchart................................................................................21
10.4 Project Change request Form Template.......................................................................21
Example – Communications Plan v1.0.1 Page 3

1. Executive Summary
1.1 Introduction
The document is a Project Management Plan (PMP) that is prepared for a software development project. The project is the
development of a mobile application for a banking firm. The mobile application will be developed for iOS as well as Android
platforms. The banking firm is in its expansion phase and there are numerous activities that need to be upgraded. It is essential for the
firm to incorporate the latest technologies to gain competitive edge in the market. The primary aim of the project is to provide the
organization with the same by streamlining all the business operations and improving the customer relations through the mobile
application. The PMP includes the guidelines for the management of various project areas.
1.2 Purpose
The purpose of the plan is to provide the managers and project leaders with the guidelines to manage the project activities.
1.3 Scope
The scope of the document includes the coverage of project management details in the areas as project overview, project stakeholders,
schedule, resources, costs, and major project areas.
Example – Communications Plan v1.0.1 Page 4

2. Project Overview
2.1 Project Description
The project includes the development of a mobile application for a banking firm. The firm is in the expansion phase and there will be
an increase in the business processes and operations with the expansion of the business. It will be essential for the banking firm to
make use of the technology to reach out to a maximum number of customers and to streamline the business operations. The project
will include the development and deployment of a mobile application for the organization that will run on both iOS and Android
platforms.
2.2 Problem Statement
The organization is a small-scale banking firm and it needs to expand its business operations and develop enhanced customer base.
Mobile applications are desired by every customer in the present scenario and the absence of the same may appear as a barrier for the
organization in its professional and business growth. The development of the mobile application will provide the organization with a
competitive edge in the market.
2.3 Goals
The goal of the project is to adhere to the estimated schedule, time, and scope to design, develop, and deploy a mobile application for
the banking firm.
Example – Communications Plan v1.0.1 Page 5

2.4 Project Background
The project is a software development project that is being carried out for a banking firm. The firm is a small-scale organization that is
in its expansion phase. The project will include the design, development, and deployment of the mobile application for the
organization. The application will be used by the employees and stakeholders of the banking firm. It will allow the employees to
manage customer relations and streamline the business operations. The data management and handling services will also become
easier. The project will follow the software development lifecycle by covering the phases, such as planning, requirements analysis,
design, development, testing & deployment, implementation, and closure.
The project will overcome the current issues at the banking firm in terms of the inability to streamline the business operations and
challenges in data management. The customer relations will also improve with the deployment of the application.
2.5 Product Objectives
The following objectives will be fulfilled by the mobile application that is being developed:
 To incorporate the functional, non-functional, and user requirements & specifications that have been defined for the
application.
 To make sure that information security and privacy is maintained at all times.
 To adhere to the estimates and quality standards
 To make sure that the resources in the project team and the project activities that are carried out are in compliance with the
regulatory, legal, and ethical policies.
Example – Communications Plan v1.0.1 Page 6

2.6 Assumptions, Constraints and Dependencies
The following assumptions and constraints have been considered for the project:
 The resources will remain available for 40 hours in a week
 The absenteeism rate for the resources will be low
 The project client will provide the funds for the execution of the project activities
 The project will be required to be completed in a total timeframe of 351 days.
 The total costs allotted to the project are $345,500 and the same shall be adhered during the project timeline.
 The environment set-up for the project will be successfully done to provide the resources with the platform to carry out the
project tasks and activities.
2.7 Project Deliverables
 Project Charter: Document describing the project highlights and the results of feasibility determination.
 Project Plan: A detailed description of the project guidelines to manage various project areas.
 Requirements Document: Description of the requirements in the categories as functional, non-functional, and user.
 Design Document: Document comprising of the system design diagrams, wireframes, and UI aspects.
 Source code: The source code of the mobile application.
 Test Plan: Detailed description of the testing activities to be carried out along with the details of test tool and responsibilities.
The details of the defect logging process will also be mentioned in the plan.
 Defect Report: Summary of the defects that are reported by the test team along with the status of each defect.
 Closure Report: The final report submitted for the project that will mark the end of the project. It will include the details of the
project activities carried out, performance evaluation results, and lessons acquired with areas of improvement.
Example – Communications Plan v1.0.1 Page 7

2.8 Schedule and Budget Summary
The total duration of the project that is estimated is 351 days. The start date of the project is 1st February 2019 and the end date is 5th
June 2020. The total costs that are estimated for the project are $345,220.
The schedule and budget includes all the project activities along with the cost of the materials as well as the resources. The project
costs cover the cost of project designing, planning, development, testing, implementation, and closure. The probable risks and changes
to the project have been considered while estimating the project schedule and costs.
The technique that has been used to estimate the values of project schedule and project costs is bottom-up project estimations.
2.9 Evolution of the Plan
The project management plan prepared for the project is carried out in phases. The initiation and planning phase are the project phases
that are carried out first and the project plan is prepared in these phases.
The changes will be made to the project plan as per the project progress.
2.10 Definitions and Acronyms
PMP: Project Management Plan
UI: User Interface
Example – Communications Plan v1.0.1 Page 8

3. Stakeholder Register
5. Resource Plan with RACI
5.1 Overview/Purpose
The purpose of the resource plan is to make sure that role and responsibilities are assigned to the resources and there is clarity among
the resources on the tasks that they need to perform during the project timeline.
5.2 Resourcing Strategy & Assumption
The resourcing for the project has been done on the basis of the project estimates in terms of the project scope, project schedule, and
project costs. The allocations of the duties are done as per the requirements of the projects and these are then mapped with the
resource skills and abilities. It is assumed that the resources will remain available during the project timeline and the absenteeism rate
will be low. It is also considered that the resources will remain available for 40 hours in a week.
The allocation and deallocation of the resources in the project will be done using automated resource management tool. The details of
the resources, billing hours, and cycle will be shown. The resources will be tagged in the beginning of the project and will be
gradually released in the closure phase.
Example – Communications Plan v1.0.1 Page 9

5.3 Resourcing Development
The resource estimation was done by assuming that the resource absenteeism rate will remain low and there will not be any
resignations during the project timeline. The past record and performance of the resources was analysed to assume the same. It was
also considered that the resources will work for 5 days in a week and 8 hours in a day. They will be available for 40 hours in a week.
Example – Communications Plan v1.0.1 Page 10

6. Risk Management Plan
6.1 Review of Risk Management Plan
A risk refers to an event which can negatively affect objectives of a project. A Risk Management Plan includes processes like
identification, assessment, monitoring and reporting of associated risks (Marcelino-Sádaba et al., 2014). It defines the identified risks
of the project and mentions how they will be analyzed and managed.
6.2 Risk Identification
The risk identification process involves appropriate stakeholders, the project team and evaluation of organizational culture,
environmental factors. Thorough attention is also given towards deliverables of the project along with the necessary assumptions,
resource plan among others.
6.3 Risk Analysis
The risks identified for the mobile application development process are mentioned below:
Risk ID Risk Description Probability Severity Response
R001 Field Mapping When mapping of
fields between the
tables of legacy
Oracle database
0.5 Medium Avoid
Example – Communications Plan v1.0.1 Page 11

with that of the
customer
relationship
management
(CRM) suites like
Salesforce is not
present, the mobile
application can get
released along with
a host of bugs and
glitches
R002 Internet or Web
Browser
The absence of a
web browser
application can
handicap end users
as most of the
internet specific
functions of the
application will be
inaccessible to the
user
0.5 Medium Mitigate
R003 Failure to
understand
When the
requirements
0.5 Medium Avoid
Example – Communications Plan v1.0.1 Page 12

requirements specified are not
clearly understood,
the application ends
up to be a solution
that is not liked by
any of the intended
users
R004 Excess features It is a common
mistake by
developers to
overload
applications with
features. This
almost always leads
to the end user
feeling
uncomfortable and
confused due to
getting
overwhelmed by
the amount of
activities required
0.4 Low Avoid
R005 Design changes Poorly meeting the 0.3 Low Avoid
Example – Communications Plan v1.0.1 Page 13

requirements or
lack of focus
towards the purpose
of functions that
come with the
application can
leave users
dissatisfied and
forces the
developers to
initiate a redesign
of the same
according to
feedback obtained
from the end users
R006 Unauthorized SMS,
dialing and
payments
All the three
processes be it
SMS, dialing or
payments concern
charging the users
for the service or
transaction
involved. As a
0.7 High Mitigate
Example – Communications Plan v1.0.1 Page 14

result, it is of
utmost importance
to secure these
processes so that
they cannot be
taken advantage of
by attackers
R007 Use of Hard coded
keys and passwords
Setting hard coded
access keys for
specific functions
of applications has
been the easier way
of developing
applications.
However, they
expose the
application to being
misused by
attackers as these
hardcoded keys are
easily available
0.8 High Mitigate
Example – Communications Plan v1.0.1 Page 15

The identified risks mostly include risks of ‘Medium’ severity. The two security related risks carry ‘High’ severity. Six of the seven
suggested risks require responses from the technical leads leaving the ‘failure to understand requirements’ as the only risk requiring
attention of business teams. The risk carrying the lowest severity (PI - 28) is ‘excessive features’ – although a very common risk the PI
score is kept low by the small impact score (Hoehle & Venkatesh, 2015). The risk with the highest severity is ‘Use of Hard coded keys
and passwords’ having a PI score of 72 (Liu et al., 2013).
6.4 Risk Monitoring Plan
The risk levels for the project is monitored, tracked and reported across the lifestyle of the project. The project team maintains a list of
7 critical risks with the help of a risk register (Mace et al., 2015). The risk management plan constitutes an important part regarding
reporting of project status. All requests regarding changes to the project are analyzed as to how project risks are affected.
Example – Communications Plan v1.0.1 Page 16

7. Communications Plan
7.1 Overview/Purpose
The purpose of the communication plan is to ensure the Project Management Improvement Project provides relevant, accurate, and
consistent project information to project stakeholders and other appropriate audiences. By effectively communicating the project can
accomplish its work with the support and cooperation of each stakeholder group.
The communication plan provides a framework to manage and coordinate the wide variety of communications that take place during
the project. The communication plan covers who will receive the communications, how the communications will be delivered, what
information will be communicated, who communicates, and the frequency of the communications.
The following outlines the targeted audiences, the key communication messages to be delivered, and the method for delivering the
information, the communicator, and the frequency of the delivery.
7.2 Communication Message and Delivery (Matrix)
Audience Message Delivery Method Delivery
Frequency
Communicator
Example: Project
Sponsor
Project Plans
Status Reports
Meeting
Report published in My
Web space with DoITnet
and PSST link
Weekly
Biweekly
Project Manager
Project Manager
Example – Communications Plan v1.0.1 Page 17

Audience Message Delivery Method Delivery
Frequency
Communicator
7.3 Communications Guidelines
Communication Guidelines—E-mail, Text:
1) Do not use reply all to emails
2)
3)
4)
5)
6)
Example – Communications Plan v1.0.1 Page 18

Communication Guidelines—Meetings:
1) Meetings must have pre-published agendas, prior to meeting request…agenda must
accompany the OUTLOOK meeting request
2)
3)
4)
5)
.
7.4 Escalation Process
Example – Communications Plan v1.0.1 Page 19

8. Procurement
Example – Communications Plan v1.0.1 Page 20

9. Cost
9.1 Introduction
[The purpose of this document is to provide general content of a Cost Management Plan and to describe submission required in
Microsoft Project format (.mpp file).]
Cost Management Plan
[A cost management Plan defines cost baseline, modifies it whenever necessary, and uses it for monitoring and controlling cost. A
project cost management plan generally includes descriptions, procedures and responsibilities for items such as Costs included,
activity resource estimating, cost estimating, cost baseline, budget determination and cost control.]
9.2 Estimate Cost
[Estimate Cost is a process of developing an approximation of monetary resources needed to complete project activities.]
9.3 Contingency Reserve Project Purpose or Justification
[Contingency reserve is money assigned to the project and allocated for identified risks for which contingent responses are
developed. Generally, how much money is reserved and its rationale are included here.]
9.4 Budget
[Once the project costs or cost baseline is determined, a time-phased project budget is developed. Project budget shows how the
project cost will be incurred by appropriate periods (months, weeks, quarter, etc.) during project performance period. Describe how
your budget is developed.]
Example – Communications Plan v1.0.1 Page 21

9.5 Cost Control and Monitoring
[The approved project budget with contingency reserves serves as a baseline for project control. This section usually include
project approach to monitor actual versus planned performance, approach ( e.g. Earned Value analysis), and how any cost
changes will be managed.]
9.6 Performance Monitoring
[Describe your approach to monitor planned versus actual performance and matrices that will be used]
9.7 Project Reports
[Include name and description of 2 to 3 reports that you plan to use for performance monitoring, status reporting or other reports.
These are the reports for which you will be submitting a Microsoft Project mpp file. See section below. ]
9.8 Cost Change Control
[Describe briefly how any changes to the cost baseline will be administered and implemented.]
9.9 Microsoft Project Deliverables
9.9.1 Project Budget
[Include your project WBS (in .mpp format) that represents your project cost. Ensure that contingency reserves as a separate line
item. The report submission is in Moodle]
9.9.2 Microsoft Performance Report
[Include report name and describe how the report will be used]
Example – Communications Plan v1.0.1 Page 22

Example – Communications Plan v1.0.1 Page 23

Example – Communications Plan v1.0.1
Page 24

10.Integrated Change Control
10.1 Change Control Narrative
10.2 Project Change Control Narrative
10.3 Project Change Control Flowchart
10.4 Project Change request Form Template
Example – Communications Plan v1.0.1
Page 25

References
Hoehle, H., & Venkatesh, V. (2015). Mobile application usability: Conceptualization and
instrument development. Mis Quarterly, 39(2).
Liu, D., Cuervo, E., Pistol, V., Scudellari, R., & Cox, L. P. (2013, June). Screenpass: Secure
password entry on touchscreen devices. In Proceeding of the 11th annual international
conference on Mobile systems, applications, and services (pp. 291-304). ACM.
Mace, G. M., Hails, R. S., Cryle, P., Harlow, J., & Clarke, S. J. (2015). Towards a risk register
for natural capital. Journal of Applied Ecology, 52(3), 641-653.
Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014). Project
risk management methodology for small firms. International journal of project
management, 32(2), 327-340.
Example – Communications Plan v1.0.1
Page 26

Example – Communications Plan v1.0.1
Page 27

Example – Communications Plan v1.0.1
Page 28