"Scrum is an agile project management framework that helps teams structure and manage their work through a set of values, principles, and practices" - Atlassian
Product Owner: Backlogs the list of things that need to be done
Team: Responsible for delivering shippable increments and estimating backlog items
Scrum Master: Responsible for managing the overall scrum process, removing obstacles, facilitating events, and helping communication
Part 1
When: At the start of each sprint
What: Dev team moves items from product backlog to sprint backlog
Who: Dev Team, Product Owner, Scrum Master
How Long: ~6 hours for 4-week sprint
Part 2
When: Daily
What: Each team member answers 3 questions: what was done yesterday, what needs to be done today, identify obstacles
Who: Dev Team, Scrum Master
How Long: ~15 minutes
Part 3
When: At the end of each sprint
What: Dev team demos product increments to stakeholders; product backlog is revised as needed; product may be released
Who: Entire Scrum Team + Stakeholders
How Long: ~3 hours for a 4-week sprint
Part 4
When: At the end of each sprint
What: Scrum team reflects upon the 'process': what went well, room for improvement, experiments to be conducted in the next sprint
Who: Entire scrum team
How Long: ~2 hours for 4-week sprint
For this project, we used the application Trello in order to keep track of what our Front and Back End teams were doing. Our board was organized in the following manner:
This implementation also served to maintain accountability regarding each individual's contributions to the app. It streamlined the process of sharing our contributions and identifying potential critical errors in our code. This was achieved by necessitating that our code branches pass through the checkstyle before merging with the main branch, ensuring a higher standard of code quality and reducing the likelihood of introducing bugs or inconsistencies.