From our requirements, we figured out that our main tasks were to:
Send an email with the invoice
Create a communication report
Be able to send to multiple recipients
We decided our MVP was to be able to send an invoice to the recipient via email.
We made these as our epics, and mapped them out on our roadmap/gantt chart, with communication report and multiple recipients being further down the timeline. This reflects our priorities and the fact that epics 2 and 3 cannot be completed unless there is significant progress in epic 1.
The breakdown of tasks is up to you as a team, however you should (a) ensure that tasks are broken down at a technical level and not just a product level, and (b) document your logic behind the breakdown of tasks.
Using Jira, you will need to:
Create a sprint that details all of the work up until the end of Sprint 2;
Create tickets / work items for each task;
Appropriately group tickets together under epics;
Where needed, split tickets down into subtasks;
Allocate assignees and reporters to each ticket;
Allocate Story Points to each ticket;
Allocate Priorities to each ticket;
Sequence the tickets appropriately in the backlog; and
Highlight dependencies and prerequisites between tasks as needed.
Document any important reasoning that occurs as part of this process
After being broken down into epics, tickets were created under each. For example, sending an invoice was broken down into first having a framework for flask, then being able to send an email, and finally sending an email (with subtasks of loading the XML and saving the XML). A separate issue was created to check the health of the system.
Priorities have been allocated according to the MVP. The task of simply sending the invoice was vital - so those were very high priority.
Further tasks were lower priority - and also sequenced logically (for example, there needs to be multiple emails sent before we can make a communication report with multiple deliveries).
Dependencies and prerequisites have been highlighted by using the “blocked/blocking” function on Jira. For example, in SE2Y22G21-48 - Getting issue details... STATUS , it is blocked by SE2Y22G21-46 - Getting issue details... STATUS .
Story points
Do tickets correspond to logical segmentations of work?
Are the tickets written at a technical level of abstraction?
Have individuals been logically assigned to tasks?
Are task allocations approximately equal?
Have dependencies and prerequisites between tasks been highlighted?
Have story points been logically allocated to tasks according to a specified structure?
Have tasks been appropriately broken up into sub-tasks?
Have priorities been logically allocated to tasks?
Is the backlog sequenced logically?
Have tickets been logically grouped under epics?
Does the plan provide a complete layout of the next sprint of work?