Links to our project:

1. Our project repository
2. Table view of our project backlog

Burndown Chart

Stories Completed in Sprints:

Sprint 1

1. Deploy app onto flyctl
• Link
• Points: 4 (Large)
2. Deploy SQL database
• Link
• Points: 5 (X-Large)

Sprint 2

3. As a user I would like the website to be hosted online so that I can visit it
• Link
• Points: 1 (Tiny)
4. As a user I want to have an about page of the website so that I can learn more about the authors
• Link
• Points: 3 (Medium)
5. As a user I want to have the user nicknames viewable on the about page so that I can learn more about the authors
• Link
• Points: 2 (Small)
6. As a user I want to have the team nickname viewable on the about page so that I can learn more about the team
• Link
• Points: 4 (Large)

Sprint 3 and beyond

7. Create backend models
• Link
• Points: 5 (X-Large)
8. Design website theme
• Link
• Points: 2 (Small)
9. Add header and footer
• Link
• Points: 1 (Tiny)
10. As a user I want to be able to see who has RSVP for an event so that I can see who else is attending
• Link
• Points: 4 (Large)
11. As a user I want to be able to RSVP for an event so that others know I am attending
• Link
• Points: 4 (Large)
12. As a user I want to be able to donate to an event so that I can support it
• Link
• Points: 3 (Medium)
13. As a user I want each event to be clickable so that it leads me to a new page with info
• Link
• Points: 3 (Medium)
14. As a user I want to be able to create a new event so that I can share it with other users
• Link
• Points: 4 (Large)
15. As a user I want to see a footer on all pages of the website so that I can navigate the website easily
• Link
• Points: 3 (Medium)
16. As a developer I want to have a database for RSVPs so that I can keep track of this data
• Link
• Points: 3 (Medium)
17. As a developer I want to have a database for events so that I can keep track of this data
• Link
• Points: 3 (Medium)
18. Set up HTML for event page
• Link
• Points: 2 (Small)
19. As a developer I want each an event detail page with static content so I can see event details
• Link
• Points: 3 (Medium)
20. Add email validation for RSVP function
• Link
• Points: 3 (Medium)

Traffic analysis:

For traffic analysis, we started off by using Google Analytics. We connected Google Analytics to our website but we had difficulties getting any metrics using it. Afterwards, we decided to develop our own analytics tracker as one of our sprint goals. While we put a lot of time and effort into writing it, we ran into several errors that made it so our tracker does not function as expected. Nevertheless, the progress we have made on this part is contained in our repository.

Donate/Support A/B test results:

Overall, our team found this to be the most difficult portion of the project. Our initial thoughts were to use Google Analytics's built-in features to conduct the A/B test. However, we were not able to get the Analytics tracker working as intended. Developing our own A/B test from scratch was too advanced of a task for our team to implement.

Final sprint description:

In our previous three sprints, we finished developing most of the features required by the project. Therefore in our final sprint, we focused on running tests and fixing bugs. We were using manual deployment on Fly in previous sprints, and we tried to re-deploy our application on Render to enable automatic deployment.

Conclusion:

Our team collaborated efficiently during the first sprint. We mainly communicate in group chat using Slack in group chat instead of in-person meetings because of conflict. However, some of the teammates stopped to show up in class and contributed to the project, so we did not have enough time to solve all bugs in our test results. However, the project experience enhanced our understanding of version control, CI/CD, and agile practices through hand-on experience.