Writing effective Change Requests

Image for post
Image for post

Change always happens. No matter what project you are on, no matter how well a requirement is documented, many situations arise where the requirements must change. Client Business logic has changed, new regulatory requirements arise, internal teams have discovered a need to update the solution; no matter the situation, signed-off requirements may need to be updated, changed, or removed.

Depending on the project methodology your organization uses, be it Waterfall, RUP, Agile, Hybrid-Agile, an effective way to track project requirement changes is via the use of Change Requests. This blog post will delve into the creation of the Change Request, but not the approval process behind it, as various development methodologies have different ways of approving the Change Request.

A Change Request document, in itself, is a formal document that allows you to capture how a simple or complex business or technical change impacts the existing implementation of a project.

Below are some key components of an effective Change Request:

The Project Name

The Request Number

The Requestor

This section identifies who requested the change -

Description of the Change

This section should contain meaningful information that allows those who pick up the Change Request to understand, at a glance, what the Change Request pertains to.

The Reason for the Change

This section allows you to document the reason(s) behind the Change Request. This section also provides the readers of the Change Request with further context into the drivers behind the change.

The Impact of the Change

This section should identify the areas of the solution or document artefacts that will be impacted by the Change Request:

The Proposed Action to be Taken

This section provides the details of the action(s) that will be taken to address the change requirement

The Business Priority of the Change

This section would provide the context to the importance of the change to the Requestor making the request.

The Status of the Change (Approval Block)

The Status of the Change allows readers to identify where, along the approval process the Change Request lies.

Author — Francis Roque, DLT Labs

About the Author: Francis Roque is a seasoned Senior Business Analyst with vast experience and extensive knowledge. His experiences span Fintech, Financial Regulation, Human Resources, Telecom, Consulting, Managed Services, and now Freighttech and Distributed Ledger technology.

Written by

DLT Labs is a global leader in Distributed Ledger Technology and Enterprise Products. To know more, head over to: https://www.dltlabs.com/

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store