Communications

Are meeting minutes well laid-out, detailed and insightful?
Has the team been using a platform for regular communication?
Has the team undertaken Agile communications? (standups, sprint planning, sprint retrospective)

Meetings

Prior to the meetings that were held on the 27th of February, where the meeting was done via Teams, all communication had either been done on Tuesdays (1-4pm) during our tutorial slot, or on discord.

Meeting minutes

Please find attached, our meeting minutes throughout the the duration of sprint 1

2022-02-15 Meeting notes

2022-02-21 Meeting notes

2022-02-22 Meeting notes

2022-02-27 Meeting notes

Standups

Please find attached, our stand ups throughout the duration of sprint 1

Standups

Sprint Planning (Iteration 1)

Question	What is the goal for this sprint? Big Picture.	What product backlog items are ready and contribute toward the sprint goal?	Who is available for this sprint? Identify any vacations, holidays, other activities that will impact everyone’s availability during the sprint.	What is the team’s capacity based on everyone’s availability
Garvi	Complete Iteration 1 Create Initial API Design and interface Evaluate on the Stack Architecture (as well as what platform will be used) for future	API design (4) was allocated to the group	N/A holidays/ vacations - team will be active throughout the whole duration of Iteration 1, unless there are unforeseen circumstances	Medium - High Capacity to onboard tasks. Weekly Labs and Quizzes for other subjects may interfere Unavailable Monday nights - extracurricular
Tay
Edward
Michelle
Joshua

Sprint Planning (Iteration 2) -

To be completed on the first day of the 2nd iteration being released.

Sprint Retrospective

Topics	What Went Well	Even Better If	Ways Forward for Sprint 2
Team Roles	Team roles were delegate early in the iteration (week 1, where each role had been explained) Members took control of their role, yet were open to getting help from each team member. i.e. As Garvi was delivery manager, she would set structure to each of the meetings - and be minute taker. Team roles were allocated based on the strengths and skillset of each member as well as their interests.	Had a clearer understanding of what each member does throughout the iteration - i.e. when does Project manager take lead in a space.	Refer back to Lecture 2 in week 1, for team roles as well as do additional research
Requirements and Contraints
Initial Software Architecture Design
Initial API Design
Project Planning		Structured understanding on what is considered highest - lowest priority as well as Story points could have been discussed early week 1, allowing
Communications	Consistent communication from each member in the team Due to each members own strengths and interests, easily able to delegate tasks yet still have discussions to provide our insights e.g. Joshua and Edward, were able to set up and work on Swagger for the team. Post main meeting agenda, meeting continued with workspaces, which allowed for discussion and further team work	Better planning for when our online meetings were held, to ensure every member is present and can stay for the whole duration. Place better emphasis on Asynchornist stands, for members to update the team on their progress	Create a when2meet on the first day of sprint 2 - to ensure that there is a consistent meeting time going forward