Agile - Abandoning a Change Note

The attached guide explains how to “abandon” a Change Note. This means that we no longer require it and need to take it off its normal workflow.

If we leave it without taking any action, then it will appear in reports and metrics, and over time we will accumulate many unwanted Change Notes, causing confusion for users.

There is not a single solution to abandoning a Change Note. The choice will depend on where the Change Note has reached in its workflow.

This “How To” Guide explains what to do at each stage of the workflows.

Examples of why a Change Note needs to be abandoned:

· The user has selected the wrong type of Change Note for what they require e.g. trying to release parts to Oracle on a “non-ERP” Change Note.

· The affected items on the Change Note are going to be modified via a different Change Note.