Starter repository for the Turing School Futbol project.
A 1-2 summary or bullet points outlining your plan for check-ins throughout the duration of the project.
- Morning standups everyday at 8:30 am MST.
- Slack messages for immediate assistance/issues
A 2-4 sentence summary of your plan for project organization and workflow. This can include bullet points. If you plan to use a project management tool, please include a link to your project board.
We are using GitHub projects to assign tasks to our team members to complete. We plan on using this tool, morning stand ups, and Slack to communicate workflow and organization. Pull requests will be reviewed within a single stand up by two people, meaning PR is created, we have a stand up, then before the next stand up the next morning it should be reviewed by two team members.
A 2-3 sentence summary describing the different approaches your group discussed for project organization and how you collectively made a decision on which to use.
We discussed possibly using Trello and GitHub Projects. We decided to go with GitHub projects because of its intergration with github. GitHub Projects also came recommended by previous cohorts so that finalized our decision with using GitHub Projects.
A 2-3 sentence summary describing your approach to the code design.
We created game, league, and season classes that will be supported by the main stat_tracker class. This will allow us to use the methods all in one place in the runner file.
Include link to your initial DTR document and the date it was completed. If you do additional DTRs later in the project, you should link the revised versions here as well with the date. New versions should be listed alongside older versions. Do not delete old DTRs.
DTR https://docs.google.com/document/d/1ku5tPA3S3jpF-9TP_w3iCD44BkuOnGZM_R8dU1qkQYA/edit - completed 04/18/2023
Create a section in your README called “Contributors”. List each group member’s name and link to their LinkedIn and Github profiles.
LinkedIn - https://www.linkedin.com/in/austin-woods-1830aa195/ GitHub - https://github.com/boomclear
LinkedIn - https://www.linkedin.com/in/steven-stackhouse/ GitHub - https://github.com/stackmm
LinkedIn - https://www.linkedin.com/in/jesse-sorman/ GitHub - https://github.com/Jesse193
LinkedIn - https://www.linkedin.com/in/blaine-glasgow-134a9017a/ GitHub - https://github.com/GlowMunch
Jamboard we used to organize our thoughts: https://jamboard.google.com/d/1FqUzVNPRLoVg4FYs8RlmsJJR4zOxpJufAS5KCavODds/edit?usp=sharing
- Communications between member of the team. Verbal and messaging
- Daily Stand up and group meetings
- Method testing
- Being more thorough with our git workflow standardizing
- Spend more time in code design planning before jumping into coding
- Spend more time condiering what methods go together and have shared helper methods