Communications

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

• 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