Change request management

[Eydís Sigurðardóttir]

We are a company that has approximately 800 clients and 150 employees, and the current project setup is based on Jira Cloud. We work on implementing software for our clients. The goal is to streamline how change requests are managed within the jira environment to improve efficiency and transparency.

The plan is to implement a process that supports four distinct types of change requests, categorized based on the nature and complexity of the request. This structured approach will help ensure that each request is handled appropriately and consistently. Additionally, the process will include obtaining customer approval for each change request, which will make it easier to justify and invoice the project costs at the end of the engagement.

By introducing this framework, we aim to enhance collaboration, reduce ambiguity, and provide clear accountability for both the customer and our team. This will ultimately lead to smoother project delivery and improved customer satisfaction.

Has anyone out there done this and could share how it went, what were the biggest obsticles and how has it helped to justify invoicing customers for the changes they approved?

[John Funk]

Hi Eydis,

Yes, this is fairly straightforward to implement. Create your JSM space if you haven't already. Then turn on the Change Management feature. This will give you the framework you need to do wat you want.