...
- We don’t publish roadmaps with specific release dates.
- The IT Manager and IT Systems Team Leader review requests on a regular basis.
- Features and requests are selected and scheduled based on a number of factors.
This policy procedure does not apply to bugs. See our Bug Fix Policy about our approach to bug fixing.
...
We use a standardised workflow across all our applications.
Status | Definition | Target Time |
Request Received | This request is in the development backlog ready to be reviewed. We aim to review all new requests within 6 months. | 6 months |
Reviewing | This request is being investigated by a member of IT Systems. | 4 weeks |
Under consideration | This request is a strong candidate for our roadmap. We’ll follow up on it in a few months’ time. | 6 moths |
For SMT Approval | Due to the scale of the request, it requires further prioritisation by the Senior Management Team. | 3 months |
Future consideration | This request is a potential candidate for our long-term roadmap. We won't work on it in the short term, but will review it again within a year. | 1 year |
Not Being Considered | We appreciate the merit of this request, but don't intend to work it in the foreseeable future. | - |
In Development Queue | The request has been approved either internally or by the senior management team and is waiting to be implemented by our development team subject to resources and existing priorities. | Various |
In progress | The development team is currently working on this request. | Various |
Waiting for release | The change has been implemented and is waiting to be released. | 2-4 weeks |
Closed | Work on this request is complete. If the change has been implemented, the resolution will be ‘Completed’ If we don't intend to implement this change, the resolution will be 'Rejected’, ‘Unable to Resolve’ etc. | - |