...
| Epic | Story/Task | Sprint | |
|---|---|---|---|
| Obtain approval for launch meeting with F&S stakeholders (i.e. those most impacted, probably content owners/editors) | Obtain approval for all HLS documents: Via PMO to give certainty Additional analysis can happen before or after. | 9 | |
| Obtain approval for the horizontal and vertical scope | |||
| Finalise presentation for key stakeholders: Need a version for PMO, senior stakeholders and content owners | 9 | ||
| Prepare high level project plan: Showing at least the F&@S coverage over time, probably with key resources blocked in | 9/10 | ||
| Draft content strategies for all HLS and/or global menu areas | 9/10 | ||
| Initial validation of (assumed) user needs | 10 | ||
| Brief all senior stakeholders in F&S: MS to prepare the ground so team can meet with content owners. | 10 | ||
| Brief stakeholders/content owners in F&S: Introduce our stakeholders to the project (problem, approach, timing, benefits, solution options, etc). | 11 | ||
| 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 | ||
...