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.
...
Question | | | | | | Additional Notes that need clarifying |
|---|
Garvi | | | | | Medium - High Capacity to onboard tasks. |  Image Added |
Tay | Medium capacity to onboard tasks Weekly labs/quizzes for other courses, may intefere Other assignments may interfere Unavailable Monday, Wednesday, Friday nights and Sunday day
|
Edward | |
Michelle | Medium capacity to onboard tasks Weekly labs/quizzes for other courses, may intefere Other assignments may interfere Unavailable Wednesday, Friday and Sunday nights
|
Joshua | Medium - High capacity to onboard tasks. Lectures and assignments for other courses may intefere Unavailable Monday, Wednesday, Sunday nights
|
Sprint Planning (Iteration 2) -
...
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.
| | |
Requirements and Contraints | The team collaborated to try and understand what was required from the spec. The requirements were completed part way through the sprint, which allowed time to plan the project. Constraints were thought out and covered as many scenarios as possible with the information currently known.
| The requirements would be better if we had a better understanding of what the project was meant to achieve. Would have been better if we were able to confirm our thought process with someone. So that we could know we were on the correct track.
| |
Initial Software Architecture Design | | | |
Initial API Design | | | |
Project Planning | Tasks were allocated based on inidivuals’s interests, which meant each member took control of their tasks allocated. i.e. Edward setting up Swagger. Jira was understandable, and tutorials allowed for fast learning curve when creating issues, allocating story points and priority
| Structured understanding on what is considered highest - lowest priority as well as Story points could have been discussed early week 1, allowing for tasks to be allocated accordingly. Issues could only be allocated once members had a clear understanding of the spec – emphasis on clarifying questions with tutor and spending a meeting ~ ensuring everyone is on the same page.
| Structure already completed in Iteration 1 - to be continued for the remainder of the course. Have sprint planning on day 1 without rushing the process to ensure everyone is aware of actionables and tasks that may come ahead. Clarify any uncertainties related to the problem.
|
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 Good structure for meeting minutes / stand ups - using a table format, for which we can easily refer back to (use of template from Confluence - which allowed for efficiency as well)
| 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 standsstandups, 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 Continue same template + consistency of how often meeting minutes and stand ups occurred for iteration 2.
|