Sprint Retrospective Meetings

Sprint 10

@Paweł Gesek to investigate the possibility to mock backend with Cypress in order to make the split between backend and frontend even more seamless
@Rafał Stencel to update frontend module’s README with a short description on how snapshots work
@Paweł Gesek to shorten build timeout to ~10/15 mins
@Steve Conrad to create a task in Jira for Rails clean-up - removing unused methods from controllers, tests and gems
@Steve Conrad to add a job to GitLab to deploy to dev server after each merge to development branch
@Nyoman Ribeka to explore possibilities to block merging on GitLab i.e. all threads must be resolved before merging is enabled


Sprint 9

All - think about how we can highlight blocking issues or issues that need immediate attention - maybe developers channel?
@Steve Conrad@Paweł Gesek - nightly dev server redeployment

Sprint 8

@Steve Conrad to start the review with sprint goal overview
@developers to show the Jira issue before showcasing the work done to help reviewers gather context
@Sarah Farooqi to explicitly add a “Sprint Goal” to Jira for each sprint during Sprint Planning meeting
@Nyoman Ribeka / @Steve Conrad to think about introducing auto-deployment to dev server
@Sarah Farooqi, @Steve Conrad to add only those tasks to sprint which are in scope of Sprint Goal and match the team’s velocity


Sprint 7

@Steve Conrad to create a task in backlog to update New Developer Guide and README files
@Steve Conrad to deploy changes merged into development branch to the dev instance before Sprint Review meetings so that the changes can be showcased on that instance