Change Management and Change Control
Introduced Software Change Management and Software Change Control to the organisation, defined workflow, frequency and appointed board members to represent the products, and disciplines such as development, quality assurance, subject-matter, product and user experience.
What is a Change Management and Change Control ?
Software Change Management and Software Change Control are systemic processes used to review, assess, identify, manage and translate requirements for future adaptations of software products.
Why ?
The purpose is to ensure issues and changes and requests are assessed using a combination of factors, such as priority, severity, importance, risks and value while ensuring efficient utilisation of available resources.
Information flow and traceability is key for an efficient development cycle to ensure what is in development is as per user requirements.
Therefore, having a consistent and single source of truth, and simple, transparent workflows allow development to accommodate changing circumstances and adaptations promptly to deliver as expected.
Effective implementations of these sessions also help mitigate and minimise risks, and disruptions.
Workflow
The workflow had to be simple so that it can be consumed and understood by both internal and external users but at the same time, it also had to facilitate complex development / test stages and scenarios.
In order to achieve this, a combination of issue linking and automation (Transitions + Conditions + Permissions) within Jira were used within workflows to automate the majority of the process, including notifications.
- NEW -> ACCEPTED -> SCHEDULED -> IN PROGRESS -> RELEASED
- ACCEPTED: Item is reviewed and validated but not yet planned.
- SCHEDULED: Item is triaged and planned within a future release.
- IN PROGRESS: Item is triaged within the immediate Development Cycle.
- RELEASED: Item competed and deployed within a release.
References: