Content Comparison

Software Design and Architecture (+ API Design)

• Review of feedback from Sprint 1 → able to update the Stack Architecture (comparative table for application and persistence methods)

Data Modelling

Software Quality / Development of the Service

Deployment

Project Management + Communication

Image Added

• Consistent updates on progress from team

• Good use of sprint planning - to delegate tasks

• Consistent meetings - when needed which included free workspace times → + group programming

• What went well (from Sprint 1 - ) was well kept (refer to picture on the right)

• Improvement on setting clear goals , and actionable for meetings

• From Sprint Retrospective Sprint 1 Ways Forward : “Continue same template + consistency of how often meeting minutes and stand ups occurred for iteration 2” Generally done well.

• Not everyone could always make the meetings

• Great emphasis on

• due to unexpected plans (not noted in the sprint planning) coming up - and us moving our meeting times.

• Similarly from Sprint 1, greater emphasis on Asynchronous standups, for members to update the team on their progress

• From Sprint Retrospective Sprint 1 Ways Forward : “Create a list of questions during every meeting, that can be brought up during the physical tutor time slot” Questions weren’t brought up as often. due to Sydney weather, half the team could not attend the physical tut

• Many issues that had been planned during Sprint 1 ~ for Sprint 2, weren't accounted for. A lot more issues needed to be added onto Jira

• Need to re-evaluate our availabilities for Sprint 3 + 4

• Use the first 5 minutes of each meeting to CLEARLY update the team in addition to updating via messages / somewhere throughout the meeting. (set aside specific time)

• Consistent group evaluation on the Issues created - Last minute → recognised that “emails sent to multiple recipients” didnt need to be completed, hence was removed from