SPRINT-1

In the following post, a detailed breakdown of project work has been explained on per weekly basis to achieve the primary sprint 1 tasks. In the end, a retrospection would follow where what was achieved vs what failed and how to rectify it will be discussed. Given below are the images showcasing the weekly meeting work tasks and meetings that will be held each week to review what was completed and what needs to be done.

WEEK 1: During week 1, the first team meeting was held where the team met and discussed the sprint 1 goals and assigned individual tasks according to the skills of each member. Planning of further meetings was done based on everyone's availability.

WEEK 2: In the week 2 meeting, work done was debriefed and the team brainstormed on use cases followed by identification functional requirements and quality attributes. Progress was noted on the front-end development part. 

WEEK 3: In the week 3 meeting, the main focus was to select what system architecture would do justice to this application and designed the system via various models such as context, architecture, sequence, deployment diagrams, etc. Progress was noted on the front-end development part and a demo was presented of the UI that had been completed. 

WEEK 4: In the week 4 meeting, which was the final meet for the first sprint, the objective that was the front-end development was to be tested and hosted on the internet. The task was achieved for the first sprint with one functional requirement fulfilled for the demo (login page and registration page for the user). Sprint retrospection took place and the team discussed what went wrong and how to rectify it within the next sprints. Presented below is the sprint burndown chart from JIRA.