...
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 |
---|---|---|---|
1 | 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 |
2 | Obtain approval for the matrix (i.e. horizontal and vertical slicing) approach to covering the scope for content and functionality development (can be cut differently for release to production). | 9 | |
3 | Finalise presentation for key stakeholders: Need a version for PMO, senior stakeholders and content owners | 9 | |
4 | Prepare high level project plan: Showing at least the F&@S coverage over time with key resources requirements. Ideally it would go further out, with decreasing details/accuracy. | 9/10 | |
5 | Draft content strategies for all HLS and/or global menu areas | 9/10 | |
6 | 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 | |
7 | Brief all senior stakeholders in F&S: MS to prepare the ground so team can meet with content owners. | 10 | |
8 | Brief stakeholders/content owners in F&S: Introduce our stakeholders to the project (problem, approach, timing, benefits, solution options, etc). | 11 | |
9 | Complete processes/artefacts required to close the initiation/establishment phase | Draft a project purpose statement and an elevator pitch | 9 |
10 | Draft success measures and targets | 9 | |
11 | Establish a RIDS register | 9 | |
12 | Establish the required project management methodologies (e.g. change, risk/issue, governance, reporting,release, etc.). Or maybe there is a Project Management Plan that should come before this? | 10 | |
13 | Establish the required reference groups | 10 | |
14 | Establish the priorities/order of scope, budget, time and quality | ||
15 | Draft epic-story/task for the first few "development phase" sprints | ||
16 | Document all know business requirements in epic-story/task forma | 9 | |
17 | Document all know user requirements in epic-story/task forma | 10 | |
18 |
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:
...