...
Thinking about all of the above and the team members involved I propose the following Epics - story/task breakdown, at least until the high level analysis is completed. This is an approach and the start but is not yet complete.
| Epic | Story/Task | Sprint | |
|---|---|---|---|
| Obtain approval for launch meeting with Introduce (at least) F&S stakeholders (i.e. those most impacted, probably content owners/editors) to WIP II | 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. At this level is it a roadmap rather than a project plan? | 9/10 | ||
| Draft content strategies for all HLS and/or global menu areas | 9/10 | ||
| Initial validation of (assumed) user needs | Validate user needs: At least those where the business requirements for WIP II assume specific user needs. Could also create an epic for user research and have one task in this phase. | 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 itComplete artefacts required to close the initiation/establishment phase | Draft a project purpose statement and an elevator pitch | 9 |
| Draft success measures and targets | 9 | ||
| Establish a RIDS register | 9 | ||
| Establish the required project management methodologies (e.g. change, risk/issue, etc.). | 10 | ||
| Document all know business requirements in epic-story/task forma | 9 | ||
| Document all know user requirements in epic-story/task forma | 10 | ||
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:
...