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

• Sprint2 closed off (this happens automatically when using iterations)
• Any issues which were linked to Sprint2 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]

Mon 05/02/24: Having a bit of difficulty reviewing the Sprint as a lot of work was done in Sprint 2 (Products, including Product Search & Filter, Basket, Checkout, Stripe). Each is working at a basic level now but there are issues which need to be resolved and sub-features which needs to be split out into separate user stories for a round 2 approach.

Note that there are some code elements that will need re-factoring, e.g.:

• the Stripe js wasn't picking up (getting a 404 on the .js file), so has been incorporated as a Githubissues.
• Githubissues is a development platform for aggregating issues.