Change Management Methodology Proposal for Computer Game Development

This project proposes a change management methodology tailored for computer game development. It begins with an executive summary outlining the proposal's purpose: to establish effective strategies for managing changes in a structured manner, ensuring stakeholder awareness and adaptation. The proposal details a structured change management process, including change request forms, evaluation criteria, and a change management log. It covers responsibilities for change plan approval, scheduling, and change control. The methodology emphasizes the importance of considering the impact, scope, and stakeholder perspectives of each change. Key components include change planning, testing, communication, and scheduling to ensure effective change request management. The document includes a change management process flow, describing steps from change request generation to implementation and closure. It also defines priority criteria for evaluating change requests, categorizing them as high, medium, or low based on their impact on the game's functionality and business value. The project concludes by emphasizing the critical role of change management in mitigating risks, ensuring project success, and maintaining productivity in computer game development.

Running Head: CHANGE-MANAGEMENT METHODOLOGY PROPOSAL
Change Management Methodology Proposal
Name of the Student
Name of the University
Author Note

1
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
Executive Summary:
The purpose of this Change Management Methodology Proposal is to contrivance all the
strategies for a change that is effective and have control over the changes being made and make
the Computer game user aware of the changes and how to adapt to these changes. The proposal
consists of the structured processes for requesting a change and mechanisms that will respond to
the requests that are made and maintaining them. For an effective change request and
management all the factors like the impact, the scope and stakeholders perspectives need to be
taken care of. The proposal consists of change planning, testing and the communication process
of changes and scheduling for an effective Change Request Proposal.

2
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
Table of Contents
1. INTRODUCTION...................................................................................................................3
1.1 Purpose Of The Change Management Plan......................................................................3
2. CHANGE MANAGEMENT PROCESS................................................................................3
2.1 Change Management Process Flow Requirements:..........................................................4
2.2 Change Request Form and Change Management Log:....................................................5
2.3 Evaluating Change Requests:................................................................................................6
3. RESPONSIBILITIES: Change management plan approval....................................................7
3.1 Changes to be Scheduled:.................................................................................................7
3.2 Change Control Process:...................................................................................................8
4. CONCLUSION........................................................................................................................8
REFERENCES:...............................................................................................................................9

3
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
1. INTRODUCTION
1.1 Objective Of The Change Management Plan
The main aim of this change management revolves around processes management because
the development of computer games and formulation of these processes are full of complexities.
Change management plan ensures budget controls, scope of the plan, communication of
schedules and required resources (Hayes,2018). The plan will also diminish the impact the
changes can make in the game market. The Change management is a documented scheme, the
tasks that are essential for the management of project changes made from the view of the phases
of the project. The management of change is produced in the planning phase, and the audience
intrested for change management plan are, the project manager, the whole game developing
team, the sponsors of the game developing (Cameron& Green,2015).
2. CHANGE REQUEST MANAGEMENT PROCESS
The procedure of change request management is orderly. It also creates an efficient process
for submission tracking, collegiality, inquiry, assessment, layout and approval for extraction of
all changes to the baseline of the development of computer games (Langley et al. 2013). The
following steps need to be put into order before starting the Change Management Proces:
 An Urgency to change the existing game and start an initiative.
 Team Building and assigning responsibilities to the members is a must.
 A vision creation which will make it clear to the team what needs to achieve.
 Communicating the created vision to take ideas and implement them.
 It is checking for risks and obstacle removal usually processes and procedures that
resist changes.

4
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
 Integration of the change and continuous monitoring is required.
2.1 Change Management Flow of Process Requirements:
Figure: CR process flow of the computer game (Frankland et al. 2013).
STEPS: DESCRIPTION:
Generation of
Change Request:
A Change Request form is filled by a submitter, and the filled form
is sent to Manager .
Status of Log of
change request:
Change Manager now enters the Request for changes to be made
into the Log that is kept involving all the steps. The Change
Request’s status has to be updated throughout the process of CR.
Change Request The reviews of project personnel are jotted in Change Request. The

5
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
Evaluation: personnel then provides estimated level of effort. A developed
proposed solution for the suggested change is made.
Authorisation: After incorporating the suggested changes into the computer games
processes, there is an approval to move forward.
Implementation: The necessary adjustments need to be made if there are approval and
requested changes and talk about the status of the requests made to
the person who submits the documentation and the stakeholders.

6
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
2.2 Managing Changes Log:
The first thing that needs to be done is to process the requests regarding the change order and
give data needed by the decision-makers (Cummings & Worley,2014).
ELEMENTS: DESCRIPTIONS:
Date of initiation: 26/08/2019
Change Request: Change Manager assigns it.
Title Head: A description that is brief regarding the change request.
Description: It describes the fields like changes desired, the impact of the
change and the benefits of t
Submitter: The person who is filling up the CR form and answers to the
questions that are change related.
Phone No: The CR submitters personal contact
E-Mail: Email address of the person submitting the form
Computer Games: The required changes that needs to be done in the computer
game.
Priorities: The code showing the urgency of required change whether it
is High, Low or Medium.

7
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
2.3 Evaluating Change Requests:
The proriyy criteria is evaluated based on the performance and efficiency of the elements and its
importance in the Change Management (Cameron & Green, 2015). Priority change boosts the
FPS of the game but the latency might increase which leads the PC to run out of resources and
freeze, hence prioritizing is essential.
PRIORITY: DESCRIPTION:
High The required factors that is changed and without which the system
fails to function comes under the High priority.
Medium The elements that provide the significant business value but are less
essential when it comes to Change Management.
Low Those that make the game nice to have/ look at.

8
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
Change requests are assigned and evaluated based on status type as follows:
STATUS : DESCRIPTION:
Open Approval pending but is considered Open
Work-in
Progress
Work in progression after the Change Request has been approved
and assigned
Under Review Change Request prior to testing is complted and needs a final
review
Phase Testing Change Request is tested after the analysis is done
Closed The updates regarding the CR is released after the tests are passed
and works completed
3. RESPONSIBILITIES: Change management plan approval
3.1 Changes to be Scheduled:
The approved computer development schedule can be impacted by the changes. Depending on
the impact (great, low and medium) these changes need to be re-baselined, fast-tracked. Budget
changes are the changes that can put a lot of pressure on the initially discussed budget of the
game development and may require funding that is additional, funding that needs to be released
to meet the plans. Changes in scope are essential and may cause the initial scope of the project to
be changed because of additional unforeseen requirements. All the funding allocations and

9
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
budgets details changes need to be approved. All the changes in the scope and scheduled
baselines needs to be approved.
3.2 Change Control Process:
The part of the project manager is to handle all the change management processes for every
change requests:
 Stakeholders (requirements for identification): A completed CR form is offered by the
Change requestor to manager of the project.
 Project Manager (Changees that needs to be updated): Throughout the lifecycle of CR
process, the project manager will keep logs of all submitted requests.
 Team, Requestor and Manager (Changes Evaluation): A preliminary analysis is
submitted by the manager of the project along with the requests to change to the higher
authorities (Change Control Board) for a review.
 Submission of CR to Change Control Board: Submitted results after a discussion of the
changes proposed will be decided if it will be approved or not.
 Changes Implementation (Manager): If approval is done by change control board after
looking at all the requirements then the manager will make the changes and remake the
project documentation if required (Kwak & Ibbs, 2013).
4. CONCLUSION
From the above-cited discussion, it is clear that the change request proposal is made to ensure
that the computer game being developed meets its success. If there is no Change management,
then there are risks related to the missing objectives of Change requests and loss of productivity.
These factors can threaten the PC game’s future. If there is a lack of proper Change request and

10
CHANGE MANAGEMENT METHODOLOGY PROPOSAL
management then there is a chance of hazardous risks to the project because all the improvement
methodologies and change request processes are provided in this proposal.
REFERENCES:
Cameron, E., & Green, M. (2015). Making sense of change management: A complete guide
to the models, tools and techniques of organizational change. Kogan Page Publishers.
Cameron, E., & Green, M. (2015). Making sense of change management: A complete guide
to the models, tools and techniques of organizational change. Kogan Page Publishers.
Cummings, T. G., & Worley, C. G. (2014). Organization development and change. Cengage
learning.
Frankland, R., Mitchell, C. M., Ferguson, J. D., Sziklai, A. T., Verma, A. K., Popowski, J. E.,
& Sturgeon, D. H. (2013). U.S. Patent No. 8,484,111. Washington, DC: U.S. Patent and
Trademark Office.
Hayes, J. (2018). The theory and practice of change management. Palgrave.
Kwak, Y. H., & Ibbs, C. W. (2013). Project management process maturity (PM) 2 model.
Journal of management in engineering, 18(3), 150-155.
Langley, A. N. N., Smallman, C., Tsoukas, H., & Van de Ven, A. H. (2013). Process studies
of change in organization and management: Unveiling temporality, activity, and flow.
Academy of management journal, 56(1), 1-13.

11
CHANGE MANAGEMENT METHODOLOGY PROPOSAL