Task: Sprint 5 retrospective

[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
• Sprint5 is 'final' sprint and ends with delivery of Version 1 of the Jeweller website

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

• Sprint5 closed off (this happens automatically when using iterations)
• Any issues which were linked to Sprint5 but not in 'Done' status reviewed and documented
• 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 Update readme with work to date

[DeeMcCart]

Extended Sprint 5 to revised project submission date- so Sprint 5 was 13 days long instead of the normal 7 days. The burndown chart showing time spent by EPIC reflects this:

Considerable time was spent in Sprint5 on code refactoring, testing and adjustment. At time of submission there are still open issues. This project would benefit from additional work to quickly progress to a Version 1.1 to include bug fixes. The issue log is shared in the comment below, and a screenprint of open issues remaining is shown

[DeeMcCart]

ISSUE LOG is at https://docs.google.com/spreadsheets/d/1c03-8MvHUGg_ebzb8hMKn2PpbqHV23T5cvY5oasyAaE/edit?usp=sharing

Analysis of isssues at time of PP5 submission: issues raised : 137** issues closed: 97 future : 26 workaroud: 6

8 issues remaining (bugs)