...
| Step | Notes | Duration estimate | Status |
|---|---|---|---|
Analyse Treejack (user testing) results, identifying where users had difficulty finding the required subjects. Devise changes to address these issues | Sam and Paul mostly, although anyone can have a say | 1d | PS has done his partDone |
Refine groupings and labels based on the findings from the step above. | Sam and Paul mostly, although anyone can have a say. Document changes and reasons in case we are asked (and to reconcile our consultation proposal with the Treejack version) | 1d (before end of Tuesday 14th) | Done |
| Prepare "pitch" for meeting with F&S, this being the overall objectives (the rationale for why/how we have grouped), the process followed to date, and the results from the user testing. | This will involve (at least) Sam, Anne, Jo, Jane and Paul. Ensure Nigel is aware/up to date. Where to we involve 'Tash? | Will draft this week (week 2 sprint 15), with input from Sam. | Done |
| Consult with F&S, in priority order, starting with FHSS and FAD (assuming these are the first faculties we will work with) | Expect changes in (but not limited to) the following categories: Mistakes or omissions we have made; 2016 changes we were unaware of; changes based on domain/study knowledge we do not have; preferences/opinions, etc | Sprint 16, depending on how comprehensive the pitch and associated approval process is. Meetings booked sprint 15 where possible | Done FHSS, Education, Law |
| Negotiate agreement on as many of the suggested changes as is possible in the meeting, both the changes we will adopt ("easy wins") and those the requester withdraws (based on our perspective). | Same as above | ||
| Document all remaining or unresolved change requests. | Ongoing/as discovered | ||
| Retire to consider/deliberate the where to next. | Discuss with team for new perspectives. We might need to test all/most of them, given that there is essentially a disagreement. | A few days | |
| Take proposal to CSP Reference Group for guidance. | Only for contentious issues. Could be by email, as no meeting has been booked? Or we book one in and work towards that date? | ||
| Second meeting (or communication) with F&S to resolve all outstanding change requests. | As and when required only. May not be needed at all and certainly not for all faculties. | ||
| Take proposal to PMO for decision. | Sprint 17 decision | ||
| Share final shape of groupings with all affected parties | Agenda item for Faculty Managers meeting? |