...
We then have the choice between doing the next faculty or doing the Postgraduate Information and and Research Centres, Institutes and Chairs for the FHSS.
Based on this approach (or a similar one) we might be able to draft a project roadmap, a list of key features or scope areas sequenced (even with dates) on a timeline. This approach is a useful answer to the myth that in agile there is no long term planning. JIRA even provide a help article on this.
A few things to be aware of:
- Consider complexity early on: To reduce risk of rework if we build templates for the simplest and find they do not grow/scale. This does not mean we have to tackle all the complex areas early but we might do some prototyping or proof of concept. Audit findings would be useful here, so Anne Nelson (Unlicensed) please join the discussion. For example, I selected HPPI because they have an institute.
- Start with a good school: Meaning that they have a good handle on their content (especially subjects and courses) and are willing to work with us.
This approach should meet with stakeholder approval because it aligns with the recruitment imperative. It also allows us to release early and often (with a 1 October deadline bringing focus on how much we can achieve).