Mobile Application Development: Risk Management & Project Planning

This document outlines a comprehensive project management plan for the development of a mobile application for a banking firm, targeting both iOS and Android platforms. The plan covers various aspects including an executive summary, project overview, stakeholder register, schedule, resource plan, risk management, communications, procurement, and cost management. It details the problem statement, project goals, objectives, assumptions, constraints, and dependencies. Key deliverables include project charter, project plan, requirements document, design document, source code, test plan, defect report, and closure report. The risk management section identifies potential risks and proposes mitigation strategies. The communication plan outlines the methods and frequency of communication among stakeholders. The document also includes sections on integrated change control and cost management, providing a holistic view of the project's execution and management. Desklib offers similar solved assignments and past papers for students.

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