Summary
- We don’t publish roadmaps with specific release dates.
- The IT Manager and IT Systems Team Leader Systems Steering Group review requests on a regular basis along with the Head of IT Services, IT Systems Team Leader and Product Owner.
- Features and requests are selected and scheduled based on a number of factors, including resources required and projected impact and benefit.
This procedure does not apply to bugs. See our Bug Fix Procedure about our approach to bug fixing.
...
We use many factors to help decide which requests to implement, including:
- College Strategy - the long-term strategic vision of the college.
- Customer Feedback - formal and informal customer interviews and other research activities.
- Support Team Insights - our support team know which issues are the most challenging, and most common for our customers.
- Product Analytics - analytics are used which helps us understand how existing features are being used.
- College Strategy - the long-term strategic vision of the collegeComplexity and Resources - some features are straightforward and provide increased value, while others look simple but may require weeks of complex development.
We use a standardised workflow across all our applications.
Status | Definition | Target Time |
Backlog | 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 |
reviewed by the IT Systems Steering Group, a member of IT Systems |
and the Product Owner. | 4 |
Under consideration
This request is a strong candidate for our roadmap. We’ll follow up on it in a few months’ time.
-6 weeks | ||
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 |
SMT 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. |
1-4 weeks |
Resolved | 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. | - |