Minimum Viable Product
From our requirements, we figured out that our main tasks were to:
...
Additionally, through previous experiences of understanding Story Point allocation, Epics and understanding priorities, Tay was able to take lead in this role in ensuring all members had an understanding. Through this, there were many of times, where members worked alongside each other in pair work, to offset the workload (as well as provide more insights). This includes co-creating the User Stories, as well as discussing what the team defines as highest to lowest priority, as well as the story points.
This is in addition to also the Framework, where there had been constant discussion the type of
Are the tickets written at a technical level of abstraction?
Have individuals been logically assigned to tasks?
Have dependencies and prerequisites between tasks been highlighted?
Have story points been logically allocated to tasks according to a specified structure
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?
Are task allocations approximately equal?
Have tasks been appropriately broken up into sub-tasks?
Do tickets correspond to logical segmentations of work?
...
Planning for Iteration 2
We are going to do our Sprint Planning on 1 March - in our tutorial, on the first day of the sprint.