...
| Epic | Story/Task | Sprint |
|---|---|---|
| Gain approval for all high level scope documents | Complete initial analysis for topics identified as being on our scope boundaries | |
| (Is there anything else PMO require to grant approval? Chrissi to add.) | ||
| Complete all high level content audits | (One task per area and probably all required prior to starting, as the outcome of this will influence where we start) | |
| Complete a working draft of the content strategy for all high level scope areas | (One task per area but spread out according to when we need them, unless this activity will influence where we start) | |
| Agree a purpose statement and success measures for WIP II | Draft elevator pitch | |
| Draft KPIs by | ||
| Agree the KPIs | ||
| Understand user and stakeholder needs | (Some part of this should happen before we start the iterative agile development process, but much will happen in/during it | |
| Agree the high level (2 or 3 levels?) IA | ||
| Develop familiarity with tools | (Maybe each of us has a need ot be proficient with some tools in order to do our parts. Initial learnings only, as the most effective learning is just in time) | |
Thinking about the structure going forward (as per comments from Anne Nelson (Unlicensed) in the task that led to this page I believe we are at a cross road and must decide which way to turn. The two options I see are:
- Epics by main activity group and stories by area of the site where that activity is required: This would give us an epic of "Content Planning" and then for each website area have a story (or more) "Plan content for Postgraduate"; or
Epics by area of the website and stories by activity for that areas: This would give us an epic of "Modernised Postgraduate hub live" and stories such as "Plan content for Postgraduate hub"