Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 13 Next »

Meeting Minutes

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

2022-03-13 Meeting Notes

2022-03-10 Meeting notes

2022-03-08 Meeting Notes

2022-03-07 Meeting notes

2022-03-01 Meeting notes

Standups

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

Standup Sprint 2

Sprint Planning

  • What is the goal for this sprint? Big Picture.

What product backlog items are ready and contribute toward the sprint goal?

What items will the team include on the sprint backlog?

Timeframe for each issue?

Issues that could disrupt progress to sprint goal?

What a finalised issue should look like (when “Done”)

Additional Notes

  • Get an MVP!!!

  • Try to do extra requirements (security, performance, etc.)

  • None

Requirements

Tomorrow (3rd March)

MVP

End of the Week 1 (6th March)

-Send an email by the end of the week

Write design our database

Second Week (8th March)

Make our ER diagram for the database,

by Friday (4th March)

Design our interface,

by Friday (4th March)

Write up a starter UML,

End of Week 1 (first draft) (6th March)

Garvi

Edward

Joshua

Tay

Michelle

When2Meet- https://www.when2meet.com/?14788698-I3Akr

  • No holidays will hinder capacity

  • Weekly labs, quizzes and assignments due in the next 2 weeks

Nothing coming up

  • Away for weekend (5-6/3/2022)

Assignment for Operating Systems 11/3/22 RIP

Industry agreement making + emailing (dead)

Confirmed meetings : 10:30am Monday (Virtual)

9pm Thursday (Virtual)

1-4pm Tuesday (In-person)

Sprint Retrospective

Topic

What Went Well (WWW)

Even Better If (EBI)

Ways Forward

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

  • 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 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

  • No labels