Task: Sprint 1 Retrospective, Sprint 2 Planning

[DeeMcCart]

EPIC: #10

As a scrum master/developer I can follow Agile principles so that project functionality is achieved incrementally across sprints

Assumptions or Pre-Requisites:

• Agile methodology is being followed for this project
• Closing out (weekly) sprint should be done with a retrospective
• Planning of next sprint should be done with backlog grooming and deciding which tasks to move to 'to do' for this sprint
• Respect timeboxing and not try to complete any tiny outstanding items from previous Sprint 'quickly' in the new Sprint. The time has passed so now deal with any hangover items in CURRENT sprint

Acceptance Criteria: (Must be completed before task is moved to 'Done')

• Sprint1 closed off (this happens automatically when using iterations)
• Any issues which were linked to Sprint1 but not in 'Done' status reviewed and moved to next sprint for completion of outstanding tasks
• OR if the acceptance criteria is met and tasks done, but there are issues, then log the issues as a bug and closeout the original UserStory/ task

Tasks

• [x] Task1 Retrospective
• [x] Task2 Backlog groominig
• [x] Task3 Sprint Planning and issue prioritisation
• [x] Task4 Update readme with work to date

[DeeMcCart]

Task 1 Retrospective: Sprint1 was Monday 22/01 to end of day Sunday 29/01 Boundaries a bit blurred in this first sprint review, as there are a number of almost-completed issues (mainly around UserProfile and AllAuth customisation). Continued working on these Monday 29/01 even though these are Sprint1 issues.

Total elapsed SPs (hours) Sprint1: c.48 hours Main achievements: core site setup, is responsive, provision for Toasts messaging created, allauth implemented, first deploy attempted (although hits a run time error when app is opened). Apps created for 'home' and 'profiles', with a placeholder app for 'products'.

[DeeMcCart]

Task 2 Backlog Grooming / Task 3 Planning next Sprint: bit of chicken-and-egg here as the first task was to gather & formalise a list of user stories #14 as I hadnt already done this. From this list (backlog), I prioritised the basket & checkout functionality for Sprint2, these are created under issues (EPIC) and (Issues)

Created progress tracking charts (project 'Insights') =; this required me to set up a new project field 'EPIC' to be able to group by EPIC on the stacked barchart (the existing '0_EPIC' label cannot be accessed for grouping). Note that these bar charts dont give a lot of information at the end of just this Sprint but will deliver some useful analysis as the weekly Sprints close out.