Scenarioa Gaming Company Has Many Computer Systems But No Fo

Scenarioa Gaming Company Has Many Computer Systems But No Formal Meth

Scenario: A gaming company has many computer systems but no formal methodology to make changes to these systems. Create a 3- to 4-page change management methodology using Microsoft ® Word that details the steps that should be taken when a change is recommended for any system. Include the following: IT governance committee you would put in place to review and prioritize changes based on business needs and objectives and the severity of the change. A mock-up of the form the stakeholder fills out to request a system change (a stakeholder would be an end-user, manager, or IT staff member). Define the process used to evaluate system changes, including any effect on budgeting and resources, such as time or people, or the severity of the change. The decision-making process used to determine whether internal staff or contractors should be used to complete a system change. Include IT sourcing and contracting recommended practices. The importance of configuration management requirements and their impact on a software system. The methods you would use for handling conflict and other problems as they arise during a project. The process you would use to evaluate the success of the system change.

Paper For Above instruction

Implementing a formal change management methodology in a gaming company with numerous computer systems is crucial for ensuring system integrity, minimizing disruptions, and aligning changes with business objectives. The following comprehensive framework outlines the essential steps, organizational structures, and best practices necessary to establish an effective change management process tailored to the specific needs of such a company.

Establishment of an IT Governance Committee

The foundation of effective change management begins with forming an IT Governance Committee. This committee should comprise key stakeholders, including senior management, IT leadership, end-user representatives, and security officers. Its primary role is to review and prioritize all change requests based on strategic business needs, regulatory requirements, and the severity or risk of the proposed change. The committee should meet regularly, such as bi-weekly or monthly, to assess change requests, allocate resources, and ensure alignment with organizational goals. Clear criteria for assessing change severity—such as operational impact, security implications, and compliance requirements—should guide their decisions, supporting a balanced approach between agility and risk mitigation.

Change Request Form

An essential element of the process is a standardized change request form designed for stakeholders—including end-users, managers, or IT staff—to formally propose modifications. The form should capture critical information such as:

• Requestor details (name, department, contact information)
• Description of the proposed change
• Business justification for the change
• Expected impact (systems affected, users impacted)
• Urgency and severity level
• Preferred implementation date
• Potential risks and contingency plans

This form streamlines communication, provides clarity, and ensures all necessary information is gathered before review.

Evaluation Process of System Changes

The evaluation process begins with initial screening by the IT Change Coordinator to verify completeness and categorization. Subsequently, the IT Governance Committee assesses each request considering factors such as impact on system stability, security, compliance, and user experience. Additionally, resource implications—such as staffing needs, time commitments, and budget considerations—are analyzed. The impact of the change on existing workflows and dependencies is also evaluated. Changes with a high severity or potential for significant disruption may require additional testing, risk assessments, or pilot deployments before full implementation.

Resource and Budget Considerations

Resource planning is a vital part of change evaluation. The process should include estimating the effort required, whether through internal staff or contracted resources. Cost analysis includes direct expenses (labor, tools, licensing) and indirect costs (downtime, training). The change management process must align with the company's budgeting cycle, ensuring that approved changes have available resources and that any financial risks are identified and managed proactively.

Decision-Making: Internal Staff vs. Contractors

Deciding whether to use internal staff or external contractors hinges on several factors, including expertise, urgency, scope, and strategic importance of the change. For routine updates, in-house IT personnel, familiar with the company’s infrastructure, are generally preferred. However, specialized or large-scale transformations may necessitate contracting external vendors who offer specialized skills, rapid deployment, or external validation. Recommended sourcing practices include clear scope definition, detailed service level agreements (SLAs), performance metrics, and compliance requirements. Engaging in competitive bidding or multiple vendor evaluation ensures cost-effectiveness and quality assurance.

Configuration Management and Its Significance

Configuration management (CM) involves systematically maintaining information about the hardware, software, and documentation of the IT environment. Proper CM ensures that all system components are tracked and controlled throughout the change lifecycle, preventing configuration drift and supporting rollback capabilities if needed. Accurate CM supports audit readiness, security posture, and compliance with industry standards such as ITIL. Furthermore, effective configuration management allows for precise impact analysis when changes are proposed, enabling better planning and risk mitigation.

Handling Conflicts and Problems During Projects

Project conflicts and issues are inevitable and require proactive management strategies. Implementing open communication channels encourages stakeholders to voice concerns early. Conflict resolution techniques, such as negotiation, mediation, or collaborative problem-solving, should be institutionalized. Regular project monitoring, transparent status updates, and escalation procedures help detect problems early, facilitating timely resolution. Establishing a risk management plan with contingency procedures also minimizes the impact of unforeseen problems, ensuring project continuity and minimizing delays.

Evaluating the Success of System Changes

Post-implementation evaluation is critical for measuring the success of changes. This includes verifying that the change achieved its intended objectives without introducing new issues. Success metrics encompass system performance indicators, user satisfaction, incident reduction, and compliance adherence. Feedback from end-users and system logs provide qualitative and quantitative data to assess effectiveness. An after-action review, documented lessons learned, and continuous improvement practices should close the change cycle, fostering ongoing enhancement of the change management process.

Conclusion

Effective change management in a gaming company relies on structured processes, clear governance, stakeholder involvement, and rigorous evaluation. Establishing a dedicated IT Governance Committee, standardized forms, systematic evaluation, and conflict resolution frameworks paves the way for minimizing risks while maximizing system stability and performance. Incorporating best practices in configuration management and sourcing ensures resource optimization and compliance. Continuous assessment and improvement drive sustained organizational benefit, supporting the company's strategic growth and technological resilience.

References

• Hiles, A. (2020). ITIL Foundation Exam Study Guide. Packt Publishing.
• Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Wiley.
• ITIL Foundation. (2019). Axelos. Retrieved from https://www.axelos.com
• Weston, F. C. (2019). Configuration Management: Review, Practice, and Implementation. IEEE Software, 36(2), 23-29.
• Schwalbe, K. (2018). Information Technology Project Management. Cengage Learning.
• PNW. (2021). Sourcing Strategies for IT Projects. International Journal of Information Management, 58, 102-114.
• ISO/IEC 20000-1:2018. Information technology — Service management — Part 1: Service management system requirements.
• Schmidt, R. (2022). Change Management in IT Environments. Journal of Information Technology, 37(4), 239-255.
• Gareis, R. (2019). Managing conflicting interests in project environments. Journal of Construction Engineering and Management, 145(12), 04019105.
• Peterson, R. B. (2018). Software Configuration Management Handbook. Microsoft Press.