Task: Sprint 3 Retrospective, Sprint 4 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')

• Sprint3 closed off (this happens automatically when using iterations)
• Any issues which were linked to Sprint3 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
• [ ] Task4 Update readme with work to date

[DeeMcCart]

DMcC 12/02/24: Task1 Retrospective, Task2 Backlog Grooming:

51.5 Story Points attributed to Sprint3.
Main progress in areas of

• Product Administration (which still needs some tidy-ups);
• Deployment (which is not yet operating correctly for static files and media images)
• Address handling at checkout (which requires further work)
• Email processing (only as far as dummy email generation, this needs further config on deployed site)
• Error handling (unproven)

So a lot of stuff done but incomplete. Tasks added to Sprint 4 where the gaps are small (e.g. #55 , #56 ) otherwise the user story has been returned to backlog.

[DeeMcCart]

Task3 - Sprint Planning & Issue Prioritisation Focus on: Redo deploy so that static and media files operate correctly #56 Add remaining custom functionality (reviews #57 and feedback form) Get additional addresses functionality working Apply consistent looks & feel (particularly to AllAuth forms) Consider additional/new PP5 elements (robots.txt, facebook page) #59

60

Task4 - UpdateReadme Not done - however I have gathered screenprints as each new feature is developed, tese are ready for adding into READme and should speed it up a little.