Development Request Procedure

This procedure does not apply to bugs. See our Bug Fix Procedure about our approach to bug fixing. 

This procedure outlines how requests for new systems, enhancements, or significant changes are handled by the IT Systems team.

1. Submitting a Request

All development requests should be submitted via the self-service portal. These should include:

• A clear description of the change or new feature

• The system it relates to

• Any relevant background or reason for the request

2. Initial Review

Once submitted, requests enter a Reviewing stage. The development team will:

• Clarify requirements if needed

• Estimate the work involved

• Identify if it's a small change or a larger development

3. Larger Requests - Steering Group Referral

If the request involves significant changes, it will be marked as Pending Steering Group Referral.

At this point, the requester should discuss the request with the relevant system owner or their SMT representative.

If the requester is unsure who the system owner is, they can contact the team for guidance.

If no action is taken to progress a Pending Steering Group Referral request within 4 months, it may be closed.

4. Approved Work

• If approved by the Steering Group (or by the development team for smaller items), the request moves to the Backlog

• Work will be prioritised and scheduled based on available capacity

5. Development and Release

Requests in progress will move through the following stages:

• In Progress actively being worked on

• Awaiting Release completed and ready to deploy

• Resolved fully delivered and released

6. Request Not Progressed

Requests that are not approved by the Steering Group or not suitable for development will be marked Not Being Considered.