This repository implements SpeedScore, a web app that enables users to log, analyze, share, and discuss their speedgolf rounds and experiences.
SpeedScore is built using MongoDB, Express.js, React.js, and Node.js
You can access our team's deployed app at this Heroku site
You can acces our team's Project Board
- Team leader: Hekili Jordan HekiliJordan
- Team member 2: Eric Alvarez Eric-Alz
- Team member 3: Cole Hensley cjhWSU
- _Team member 4: Jeremiah Strzelczyk JeremiahStrzelczyk
Story Point Counts | |||||||||
---|---|---|---|---|---|---|---|---|---|
Issue | Linked PR | Total | H.J. | E.A. | C.H. | J.S. | % Complete | Notes | |
Issue #10 | PR #58 | 5 | 0 | 0 | 0 | 5 | 100 | ||
Issue # | PR # | 3 | 0 | 0 | 0 | 0.8 | 40 | Updated database schema. Updated server routes. Did not implement UI. | |
Totals: | 8 | 3 | 1 | 1 | 0.8 |
Team Member | Contribution Reflection Statement |
---|---|
H.J. | <Required: I initially create the updateRound route and the updateRound function in App.js and later on it was improved. Later on I helped with testing, modifying the test to work accurately with our web application.> |
E.A. | <Required: The story points data is unlikely to tell the whole story about your contribution. Write a brief statement explaining and reflecting on your contribution to this milestone.> |
C.H. | <Required: The story points data is unlikely to tell the whole story about your contribution. Write a brief statement explaining and reflecting on your contribution to this milestone.> |
J.S. | I worked on the Profile & Settings page, along with the unit tests for the page. In addition, I worked on the Google OAuth feature. |
Issue | Test File | Feature Tested | Results Summary |
---|---|---|---|
Issue # | Google.js | Google Authentication | 3/3 tests passed |
Issue # | routes.js | PUT and DELETE routes for rounds | 15/15 tests passed |
Post/Reply Counts | ||||||
---|---|---|---|---|---|---|
Date | Total | H.J. | E.A. | C.H. | J.S. | |
11/9/21 | 5 | 2 | 1 | 1 | 1 | |
11/12/21 | 4 | 1 | 1 | 0 | 0 | |
Totals: | 9 | 3 | 2 | 1 | 1 |
In attendance? | ||||||
---|---|---|---|---|---|---|
Date | Duration (min) | H.J. | E.A. | C.H. | J.S. | |
11/9/21 | 17 | ✓ | ✓ | ✓ | ||
11/12/21 | 31 | ✓ | ✓ | |||
Totals: | 48 | 2 | 2 | 0 | 1 |
In attendance? | ||||||
---|---|---|---|---|---|---|
Date | Duration (min) | H.J. | E.A. | C.H. | J.S. | Notes |
11/10/21 | 45 | ✓ | ✓ | ✓ | We met in CUB conference room | |
11/14/21 | 20 | ✓ | ✓ | We met at Starbucks for coffee | ||
Totals: | 65 | 2 | 2 | 0 | 1 |
Team Member | Communication Reflection Statement |
---|---|
H.J. | <Required: In discord we all went over what we preferred to do and I also had to delegate some roles to people who had not picked up any.> |
E.A. | <Required: The posts/replies data is unlikely to tell the whole story about your communication. Write a brief statement explaining and reflecting on your communication with your team during this milestone.> |
C.H. | <Required: The posts/replies data is unlikely to tell the whole story about your communication. Write a brief statement explaining and reflecting on your communication with your team during this milestone.> |
J.S. | There were a few wrinkles in our communication. I think we were able to come together in the end to finalize a game plan, which will set us on the correct path for milestone1 |
We did not use Zoom, we used a private discord meeting to go through what we did and what we still needed to do.
- Communication for the most part was quick and smooth.
- We had everything we needed by the time our demo came along however a few bugs led us to not be able to demo at 100% completeness.
- Teammates were cooperating and working together
- Giving ourselves a day or two earlier to finish
- Giving everyone evenly as possible distributed points
- Finishing quicker
- Everyone reviewing PRs
- Work quickly but do not rush, give ourselves time
Story Point Counts | |||||||||
---|---|---|---|---|---|---|---|---|---|
Issue | Linked PR | Total | H.J. | E.A. | C.H. | J.S. | % Complete | Notes | |
Issue # | PR # | 5 | 3 | 1 | 1 | 0 | 100 | ||
Issue # | PR # | 3 | 0 | 0 | 0 | 0.8 | 40 | Updated database schema. Updated server routes. Did not implement UI. | |
Totals: | 8 | 3 | 1 | 1 | 0.8 | 0.4 |
Team Member | Contribution Reflection Statement |
---|---|
H.J. | <Required: In this milestone I completed four tasks, 80,81,82,83. There was a lot of communication among the team members and everyone helped each other out best they could> |
E.A. | <Required: The story points data is unlikely to tell the whole story about your contribution. Write a brief statement explaining and reflecting on your contribution to this milestone.> |
C.H. | With a lot of help from my team, I contributed to adding an "earn badges" link that gives information about badges, as well as making sure users could earn badges based on their golf strokes. |
J.S. | <Required: The story points data is unlikely to tell the whole story about your contribution. Write a brief statement explaining and reflecting on your contribution to this milestone.> |
Issue | Test File | Feature Tested | Results Summary |
---|---|---|---|
Issue # | Google.js | Google Authentication | 3/3 tests passed |
Issue # | routes.js | PUT and DELETE routes for rounds | 15/15 tests passed |
Post/Reply Counts | ||||||
---|---|---|---|---|---|---|
Date | Total | H.J. | E.A. | C.H. | J.S. | |
11/9/21 | 5 | 2 | 1 | 1 | 1 | |
11/12/21 | 4 | 1 | 1 | 0 | 0 | |
Totals: | 9 | 3 | 2 | 1 | 1 |
In attendance? | ||||||
---|---|---|---|---|---|---|
Date | Duration (min) | H.J. | E.A. | C.H. | J.S. | |
11/9/21 | 17 | ✓ | ✓ | ✓ | ||
11/12/21 | 31 | ✓ | ✓ | |||
Totals: | 48 | 2 | 2 | 0 | 1 |
In attendance? | ||||||
---|---|---|---|---|---|---|
Date | Duration (min) | H.J. | E.A. | C.H. | J.S. | Notes |
11/29/21 | 180 | ✓ | ✓ | ✓ | ✓ | We met to discuss Milestone 1 issues and architecture |
12/1/21 | 90 | ✓ | ✓ | ✓ | ✓ | We met to discuss further development on issues |
12/9/21 | 120 | ✓ | ✓ | ✓ | ✓ | We met to discuss final touches on Milestone 1 |
Totals: | 390 | 3 | 3 | 3 | 3 |
Team Member | Communication Reflection Statement |
---|---|
H.J. | <Required: The posts/replies data is unlikely to tell the whole story about your communication. Write a brief statement explaining and reflecting on your communication with your team during this milestone.> |
E.A. | <Required: The posts/replies data is unlikely to tell the whole story about your communication. Write a brief statement explaining and reflecting on your communication with your team during this milestone.> |
C.H. | I communicated consistently with my team in both the chat channels of Discord and Slack, as well as thorough video calls where everyone was involved and we were all getting work done together. |
J.S. | <Required: The posts/replies data is unlikely to tell the whole story about your communication. Write a brief statement explaining and reflecting on your communication with your team during this milestone.> |
- Team Synergy was great and everyone was on the same page
- Communication was effective and efficient
- We managed our time well and met to work together over Discord a lot
- Fixing bugs more efficiently
- Making sure we're on top of the Slack schedule
- Keeping up with the Slack schedule
- Managing bugs within a reasonable time frame
Story Point Counts | ||||||||
---|---|---|---|---|---|---|---|---|
Issue | Total | H.J. | E.A. | C.H. | J.S. | % Complete | Notes | |
#24 | 8 | 0 | 0 | 0 | 8 | 100 | Created DB schema. Initially structured as a table, but later switched UI to look more like a Feed Post. | |
#120 | 3 | 3 | 0 | 0 | 0 | 100 | Added to the schema to take count of the number received. Searched online for free svg icons to use. Implemented this by giving specific rows onClick() abilities. | |
#123 | 3 | 3 | 0 | 0 | 0 | 100 | Accomplished by creating a `Comment` icon that users can click. Creating document-wide handlers affected handlers that existed in the children. | |
#121 | 3 | 0 | 3 | 0 | 0 | 100 | While rendering the table of Posts, we can save the index and use it to link to specific handlers | |
#122 | 3 | 0 | 3 | 0 | 0 | 100 | Updated `RoundForm` to include a box to check. If this is checked we don't render this Post | |
#147 | 2 | 0 | 0 | 0 | 2 | 100 | Updated `RoundForm` to include a box to check. If this is checked we don't render this Post | |
#147 | 6 | 0 | 0 | 0 | 6 | 100 | Updated `RoundForm` to include a box to check. If this is checked we don't render this Post | |
#42 | 3 | 1 | 1 | 0 | 1 | 100 | Complete TPM2 Report | |
Totals: | 31 | 7 | 7 | 0 | 17 | 100 |
Team Member | Contribution Reflection Statement |
---|---|
H.J. | <Required: During this milestone i worked on two tasks. I worked on 120 and 123 that led to a user being able to click a post action button and see a post page, write text or upload a file and with Jeremiah's help, submit to and have it seen on the feed. 123 I created a pop up modal for when users click a round on the feed page, they can view the stats.> |
E.A. | I worked on #121 and #122. These Issues added the ability to "like" and reply to posts. It required writing a Comment Schema, and updating the Post schema to allow for an array of Comments. I also added the ability for users to check a box to keep their rounds showing up in the Feed Mode. This involved updating Schemas.> |
C.H. | <Required: The story points data is unlikely to tell the whole story about your contribution. Write a brief statement explaining and reflecting on your contribution to this milestone.> |
J.S. | I worked on #124 and #47 I was responsible for setting up the schema to allow posts. I was also responsible for writing all the routes for both Posts and Comments. I set up the FeedMode to display the Posts. I also wrote the front-end connections to the backend for the backend-related methods. |
Issue | Test File | Feature Tested | Results Summary |
---|---|---|---|
#148 | postPutRoute | Put route for Posts | 1/1 tests passed |
#148 | postGetTest | Get route for Posts | 1/1 tests passed |
#148 | postPostTest | POST route for Posts | 1/1 tests passed |
#148 | commentPostTest | POST route for Comments | 1/1 tests passed |
#148 | uiTests | UI Tests for FeedMode | 7/7 tests passed |
Post/Reply Counts | ||||||
---|---|---|---|---|---|---|
Date | Total | H.J. | E.A. | C.H. | J.S. | |
12/13/21 | 37 | 11 | 5 | 3 | 18 | |
12/15/21 | 69 | 22 | 13 | 5 | 29 | |
12/16/21 | 54 | 15 | 11 | 7 | 21 | |
Totals: | 160 | 48 | 29 | 15 | 68 |
In attendance? | ||||||
---|---|---|---|---|---|---|
Date | Duration (min) | H.J. | E.A. | C.H. | J.S. | Notes |
12/13/21 | 60 | ✓ | ✓ | Met over discord to talk about the features we wanted to implement for this milestone | ||
12/15/21 | 120 | ✓ | ✓ | ✓ | We met over discord to talk about our current features and resolve merge conflicts among the different versions of similar pages | |
12/15/21 | 120 | ✓ | ✓ | ✓ | We met over discord to talk about the final product, resolve merge conflicts among the different versions of similar pages and make sure we had a working product. | |
12/16/21 | 120 | ✓ | ✓ | ✓ | We met over discord to put any final touches on our app before deployment | |
Totals: | 360 | 4 | 3 | 0 | 4 |
Team Member | Communication Reflection Statement |
---|---|
H.J. | During this milestone I worked closely with my teammates to figure out and meet the requirements needed for tpm2 to the best of our ability.> |
E.A. | We met over discord much more than we did in previous milestones. Because of that, we ran into much less problems. Previous milestones were a nightmare when it came to merging; however, we noticed that this milestone was much less so. In addition, we kept each other updated constantly via discord, creating channels for specifics so they didn't get lost in the feed. |
C.H. | <Required: The posts/replies data is unlikely to tell the whole story about your communication. Write a brief statement explaining and reflecting on your communication with your team during this milestone.> |
J.S. | Communication went well. With each TPM, our team dynamics improved significantly. This TPM, we did a great job getting together and discussing lower and lower tasks that needed to be done to accomplish this milestone. We met several times on Discord to discuss both issues and team dynamics. We resolved merged together more as a team which led to less loss of features after merge. One improvement that we could have made would be to discuss architecture more. |
Something happened with the retrespective recording. We tried to recreate the meeting, but it felt weird.
- Team communication
- Implemented a lot of this milestone
- Everyone played a big part in this milestone
- Drilling into the issues and discussing smaller and smaller chunks.
- Fixing our previous bugs that we haven't had a chance to look at
- Digging even deeper into the issues to discuss smaller chunks
- Discuss architecture layout before coding