[24/01/24] - Scrum master meeting notes:

[Nintails-TF]

Scrum master meeting notes

[Nintails-TF]

• What's been working well/poorly
• Go through personal challenges that people have faced.
• Douglas
  • Overall things are going well.
  • The definition of done is a helpful idea. e.g. things have to be accessable and mobile ready.
    • need testing and formatting.
  • Talking about the definition of done.
  • Challenges
    • Code is integrating together well.
  • The most important thing is getting people to play to their strengths.
  • Refining the product backlog is important. Make sure that the things are definiend.
  • Estimating during time using T-Shirt sizes, XL and L are generally the same size.
• Gibby
  • Splitting people up into groups - Luke and Jake are dealing with DB.
  • 3 people on front end.
  • 1 person on presentations
  • 1 person on review and saving.
  • So people not turning up for the first week hurt alot
  • We need to follow the agile methodlogy better
  • Communication is struggling.
  • Master students are struggling and communication is breaking down.
• Sam
  • What has worked well is that planning took a long time, booked a room and planned out user stories and technologies.
    • NoSQL DB made the DB side very easy. Put in JSON data and you are done.
    • Website -> API -> Wrapper -> DB
    • Sprint 2 - Do a day of planning to avoid blocks in the future.
    • Good communication and knowing everyone in the group is very helpful. Knowing what teammates are where.
    • People can talk remotely and you know what is happening in front of you.
• Everyone is pretty much using Discord, Jacksons group is on teams.
• Scale of the project - we can probably finish the project.
• Client meeting - throw a curveball at you guys. A curveball might get thrown at us.
  • No curveballs are being thrown, past students suggest that this doesn't happen.
• Talk about agile methodology during your meeting with the client.
• Jackson
  • Splitting up into groups of 3 - API, Website and Database.
    • Integrating them together, DB got finished quickly on sunday.
    • API is working but not integrating with website
  • Splitting up is key. Because we didn't have the product backlog created. We then delegated tasks from the sprint backlog.
    • Use peoples strengths to complete the project faster.
  • Daily standups: 9am, asking people do we have communication issues.
    • People coming in late to standup
  • Challenges recording the daily scrum meeting. People pushing comitts that weren't reviewed.
  • Communication was pretty easy, since people joined the cliques that have formed.
  • Talking and working is draining, so it is important to take care of work-life balanced