Team Retrospectives

[darrylyeo]

Week 3

What went well last week?

• We were able to come up with a plan to split up the work and research possible technologies.

What didn't go well last week?

• We didn't have too much time to discuss what we found.

What experiment (or change) we'll make next week to improve as a team?

• Start discussing our findings with each other so that we can move forward.

[saraford]

Please do not create placeholder comments. Delete these to make it easier to leave feedback.

[darrylyeo]

Week 4

What went well last week?

• We efficiently split up the tasks for setting up the backend, modeling the database, and creating wireframes and mockups.

What didn't go well last week?

• We didn't finish everything we set out to do. We'll have to push some things to next week.

What experiment (or change) we'll make next week to improve as a team?

• We can be more detailed and clear with each other about what we're expecting each other to do, and communicate back and forth more.

[warthogs32]

Week 5

What went well?

• Database tables created, backend up and running on azure.

What didnt go well?

• Preoccupied with midterms so didn't accomplish much.

Improvements

• We need to know who is doing what and who is out of work.

[Hunter-Lane]

Week 6

What went well?

• Got backend queries, controllers, and basic frontend page setup

What didnt go well?

• Some confusion on what libraries to use and how to use them

Improvements

• We need to spend more time working collaboratively in a single setting

[darrylyeo]

Week 7

What went well?

• Project is starting to come together. Back end is pretty solidified now, and front end is on track.

What didn't go well?

• A few technical setbacks with back-end/front-end communication and setting up CORS and HTTPS, so we didn't accomplish everything we set out to do.

Improvements

• Need to work together more in person.

[Hunter-Lane]

Week 8

What went well?

• Finally have the sql server testing figured out, we are now working towards adding more features outside of the basic CRUD operations.

What didn't go well?

• We fell behind on UI testing and verifying valid usernames/login information was tricky. We also still have work to do on HTTPS.

Improvements

• Need to assign tasks to group members earlier to prevent confusion when dear deadlines.

[warthogs32]

Week 9

What went well?

• Finally have the automated builds and tests for frontend and backend working.
• event bookmarks feature done

What didn't go well?

• slow and disorganised as usual.
• no pull requests/no github flow

Improvements

• need better management