Change Control in Mobile Application Development

This document discusses change control in mobile application development, including its purpose, steps, and impact on project schedule and budget. It also provides a change request form template and describes the process of approving or rejecting change requests.

Mobile Application Development
Example – Communications Plan v1.0.1
Page 1

Example – Communications Plan v1.0.1
Page 2

10.Integrated Change Control
10.1 Change Control Narrative
Change control is known as some systematic approach that is used to manage the changes
that are made in a product or in a system. The main purpose of change control is ensuring the
there is no change in the project and the changes that are made are documented in the project
document. With the change in a project, the delivery or the service is not generally gets affected
and there is efficient use of resource. There are some basics steps that are to be followed while
carrying out a change control in a project. The change control processes are shown in the figure
below.
10.2 Project Change Control Narrative
The change control is done in this particular project is increasing the cost of the project
by 10% and for that the time schedule of the project is also increased by 10 %. The project
manager has tried to control the change in this project by documenting all the changes that
happens in the project. The stakeholder who is responsible for the change in the project for
developing the mobile application is the system developer. The system developer has to
responsibility to carry out the project and complete the testing in the changed schedule and make
the project to be successful one. As increasing the total number of days will also increase the
total budget of the project and there might be a shortage of contingency resource that is available
for the project. The change control template is shown in the below section that defines all the
changes that takes place in the project.
Example – Communications Plan v1.0.1
Page 3

10.3 Project Change Control Flowchart
There are five steps that are implemented in a change control that shows the five steps
that re to be carried out. The first step is change request that states requesting the change that is
to be undertaken in a project, the impact of the change is analyzed in the second step. The third
step includes approval of the change from the project team leader or the project manager. after
the changes gets approved, the change is implemented in the project and lastly, the change is
documented and reviewed for future use.
Figure 1: Change Change Control plan and process diagram
(Source: Created by Author)
Example – Communications Plan v1.0.1
Page 4

Example – Communications Plan v1.0.1
Page 5

10.4 Project Change request Form Template
Change Request
Project: Mobile Application Development Date:
Change Requestor: System Designer Change No:
Change Category (Check all that apply):
□ Schedule □ Cost □ Scope □ Requirements/Deliverables
□ Testing/Quality □ Resources
Does this Change Affect (Check all that apply):
□ Corrective Action □ Preventative Action □ Defect Repair □ Updates
□ Other
Example – Communications Plan v1.0.1
Page 6

Describe the Change Being Requested:
The system designer request the project manager to increase the time of the project because the system designer
needs time to test the unit of the application that is being built.
Describe the Reason for the Change:
There is a need of unit testing while developing the android application for the bank. So, the change request is
to be initiated.
Describe all Alternatives Considered:
The alternatives that are to be considered are testing each unit of the application.
Describe any Technical Changes Required to Implement this Change:
Technical change required is changing the time schedule of the project.
Describe Risks to be Considered for this Change:
Increase the cost of the project.
Estimate Resources and Costs Needed to Implement this Change:
The cost of the project will increase.
Example – Communications Plan v1.0.1
Page 7

Describe the Implications to Quality:
The quality of the project will not change as testing will be required for increasing the quality pf the project.
Disposition:
□ Approve □ Reject □ Defer
Justification of Approval, Rejection, or Deferral:
This is justified as testing phase will increase the quality of the project.
Example – Communications Plan v1.0.1
Page 8

Example – Communications Plan v1.0.1
Page 9