| Ref | Title | As a . . . | I want . . . | So that . . . | Reason for not completing |
| 2 | Input local contracts | Procurement Officer | to input local supplier contracts | staff see these when searching for approved suppliers | Not needed as local contracts can be input into Hunter and will then automatically flow through into Buy@Ed |
| 3 | Input internal providers | Procurement Officer | to input internal service providers | staff see these when searching for approved suppliers | Not needed as internal service providers can be input into Hunter and will then automatically flow through into Buy@Ed |
| 11 | Audit trail | Procurement Officer | Audit trail on changes to contract details | I can see when details were last updated and by who | Not needed as the Procurement Office team is quite small. Could perhaps be considered as a future enhancement is tracking amendments became an issue |
| 12 | FAQs | Procurement Officer | to maintain an FAQ section | users can get answers to common queries without having to contact me | FAQs are not generally considered to be a helpful thing to provide. Could perhaps be considered as a future enhancement |
| 16 | View supplier feedback | Staff User | to view other people's feedback on suppliers | I can tell if they're a reliable supplier | Could perhaps be considered as a future enhancement though careful consideration would have to be given to freedom of information and careful vetting of inappropriate comments. Could be delivered in conjunction with story 37 |
| 18 | Contract eligibility | Staff User | to see which contracts are available to me personally or to my area (e.g. just E&B) | I can take advantage of University bulk purchasing deals | This would require the end user to be logged in so that the system recognised them. This would go against what the system is trying to achieve i.e. open access |
| 22 | Product code search | Staff User | to search by product code | I can see which suppliers provide the product I want | This would require suppliers entire catalogues to be loaded in to the system which is not practical |
| 36 | Attach documents | Procurement Officer | to store documents against contracts and suppliers | I can keep all my documentation in one place | The system already offers the ability to link to documents so this was not deemed necessary |
| 37 | Moderate feedback | Procurement Officer | to moderate feedback received from users | I can mange what comments are made public about suppliers | Could perhaps be considered as a future enhancement though careful consideration would have to be given to freedom of information. Could be delivered in conjunction with story 16 |
| 40 | Supplier address search | Staff User | to search by postcode | I can see which suppliers are nearby | This was not deemed necessary. Could perhaps be considered as a future enhancement if sufficient feedback is received from users to support it |
| 47 | Maintain 'how to buy' | Procurement Officer | to maintain the 'how to buy' data | details can be kept up to date without IT support | eProcurement systems rarely change so this was not deemed a priority. A new system could easily be added via a support call |
| 50 | Maintain contract categories | Procurement Officer | to add/edit contract categories | I can maintain the info without IT support | This category list rarely changes so this was not deemed a priority. Amendmants could be done via a support call |
| 57 | By-pass screens if only 1 result | Staff User | to by-pass the search results screens if there is only one result | I have less clicks to get to the data I want | This was investigated but found to be too confusing for the end users |
| 83 | Analyse search statistics | Procurement Officer | to analyse search statistics | I can continually improve the data/keywords in Buy@Ed | Could be considered as a future enhancement |
