Futbol

We had standup meetings every day via Zoom in the morning and in the afternoon.
We communicated through Slack if we needed help, or needed an impromtu meetings.
We updated Jira frequently when tasks were assigned and completed.
We also left comments on our pull requests when making them and when merging.

We used Miro for the flow of our project, drawing out the exact classes/methods/modules we would need to complete the project.
We used Jira for task management.
We worked in various teams, sometimes a team of two and and team of three and at other times we worked independently.
We did not merge our own pull requests and had a system in place that two people needed to look at the PR's and comment before merging.
We filled out one DTR for all of us on July 29th, 2024 and did the DTR retro on Aug 1st, 2024.

We looked at suggested organizational tools like Tello and Jira, Miro and others. We collectively decided on Jira, it's interface seemed ideal to our purposes. It was easy to make tickets to track our progress and to assign different tasks to ourselves. It kept us very organized.

We chose Miro because it was easy to use, it helped us to sketch out how we thought our classes could be laid out, what would be the superclass and even what methods would come from what classes.
Later, after working on the classes for a few days, we all decided that turning the stat classes into modules would better serve our purposes, keeping our code DRY and efficient.

For our project retro, we used Mural, which served to facilitate a productive retrospective.
Some things that went well during our project are:
- Changing the overall design plan collectively.
- Having two daily check-ins.
- Having two people comment on each pull request.
- Having collaborative coding sessions.
Some things that our team would do differently next time:
- More atomic commits.
- Having a time in our check-in for any interpersonal issues.
- Making git branches only off of main and doing more frequent pull requests.

Contributors