finished sprint-04 docs (#49)

Co-authored-by: Ishaan Upadhyay <[email protected]> Co-authored-by: PDOracle <[email protected]> Co-authored-by: TheDannyG <[email protected]>
CSCC012023 · Aug 5, 2023 · 237de1e · 237de1e · vercel · Aug 5, 2023
1 parent d007901
commit 237de1e
Show file tree

Hide file tree

Showing 6 changed files with 156 additions and 0 deletions.
diff --git a/doc/sprint4/PB.md b/doc/sprint4/PB.md
@@ -0,0 +1,9 @@
+CIT-18 - As a user, I would like to view the profiles of other users so I can connect with them.
+CIT-19 - As a user, I want to create a profile to display my interests to other users.
+CIT-28 - As a user, I would like to message other users, so that we can plan events together.
+CIT-30 - As a user, I would like to view individual tickets, so that I can see the details of my ticket.
+CIT-45 - As a user, I would like the website to be visually appealing, so that I can enjoy using it.
+CIT-24 - As a user, I would like to be able to indicate that I have prepaid for a ticket, so that I can use the ticket to enter the event.
+CIT-25 - As a user, I would like to be able to indicate that I have prepaid for a ticket, so that I can use the ticket to enter the event.
+CIT-26 - As a user, I would like to add payment methods and review existing payment methods so I can keep track of how I am purchasing tickets.
+CIT-31 - As a user, I want to be able to contact the application developers so that I can resolve any issues.
diff --git a/doc/sprint4/burndown.pdf b/doc/sprint4/burndown.pdf
diff --git a/doc/sprint4/iteration-04.plan.md b/doc/sprint4/iteration-04.plan.md
@@ -0,0 +1,70 @@
+# Eventual
+
+## Iteration 04
+
+ * Start date: Jul 25, 2023
+ * End date: Aug 4, 2023
+
+## Process
+
+#### Changes from previous iteration
+
+List the most significant changes you made to your process (if any).
+
+ * Team members are now encouraged to take on more monolithic tickets with
+ more story points assigned. This is to minimize the number of tickets assigned
+ to different people with cross-team-member dependencies
+ * Encouraging team members to ask more questions as the functionality each
+ person is working on for this sprint is much more complex than the previous
+ sprints
+
+#### Roles & responsibilities
+
+Similarly to the previous two iterations, all team members will be working full stack developers for this sprint and as such there are no unique roles and responsibilities for development work. Each of our full-stack developers will be responsible for:
+
+* Developing user-friendly interfaces using our front-end tooling, such as TailwindCSS and Next.js 
+* Managing databases directly through the use of Prisma
+* Creating and modifying API endpoints to support front-end functionality through Next.js API routes. 
+
+#### Events
+
+Describe meetings (and other events) you are planning to have:
+
+We are planning to have at least one in-person meeting on Wednesdays at 3pm in BV. The goal of the meeting will be to summarize and debug and go over any issues that come up. We will also have a weekly online meeting on Saturday for a quick sync-up. We also will have daily stand ups on Slack to keep track of progress and to ensure that everyone is on the same page. The main assignee and co-collaborator for each story will keep in communication on what is being done.
+
+#### Artifacts
+
+List/describe the artifacts you will produce in order to organize your team.
+
+The following below are continuing to be used from last sprint:       
+
+ * We will be providing a burndown chart as well as a dependency graph to maintain organization.
+ * We will provide similar plan and review documents
+
+#### Git / GitHub workflow
+
+* Same Git workflow as previous sprint
+
+
+## Product
+
+_This entire section is mandatory._
+
+
+#### Goals and tasks
+
+ * Building Chat Functionality
+ * Clean up website aesthetic
+ * Create and view user profiles
+ * Create payment methods
+ * Create groups to coordinate with other users
+ * Contact page for contacting devs and adding credibility
+
+#### Artifacts
+
+List/describe the artifacts you will produce in order to present your project idea.
+
+ * Build a 'user profile' page for users to be able to edit and view each other's profile information
+ * Build a chat page where 2 or more users can chat with each other privately
+ * A payment processing workflow using the Stripe API enabling users to purchase a premium membership
+ * A better user interface across all the previously created artifacts
diff --git a/doc/sprint4/schedule.pdf b/doc/sprint4/schedule.pdf
diff --git a/doc/sprint4/sprint-04.review.md b/doc/sprint4/sprint-04.review.md
@@ -0,0 +1,77 @@
+# EVENTUAL
+
+## Iteration 04 - Review & Retrospect
+
+ * When: August 04, 2022
+ * Where: In an online meeting
+
+## Process - Reflection
+
+#### Decisions that turned out well
+
+List process-related (i.e. team organization) decisions that, in retrospect, turned out to be successful.
+
+ * We decided to let each team member take on a larger, more complex ticket that
+ encompassed several different functions. This decision was quite successful, as
+ we had a greater sprint velocity for this sprint than any other previous sprint.
+ * Telling team members to do a large amount of upfront work in the first week as
+ time estimates can be deceiving. The amount of work snowballed towards the end 
+ of the sprint, so we got several tickets finished by the end. 
+
+#### Decisions that did not turn out as well as we hoped
+
+List process-related (i.e. team organization) decisions that, in retrospect, were not as successful as you thought they would be.
+
+* Too much emphasis was placed on getting big, complex tickets merged. We could 
+have simultaneously have team members work together on smaller ticket (such as 
+polishing work) while blockers affected their main ticket.
+* For this sprint, we had less pair programming sessions due to each person 
+working on a complex ticket that only they understood. However, because of this,
+team members could only rely on themselves for assistance and bugfixing was problematic.
+
+#### Planned changes
+
+Seeing as this is our final sprint, our team does not plan to implement any further process changes to our product.
+
+
+## Product - Review
+
+#### Goals and/or tasks that were met/completed:
+
+ * From most to least important.
+ * Refer/link to artifact(s) that show that a goal/task was met/completed.
+ * If a goal/task was not part of the original iteration plan, please mention it.
+
+* Adding payment methods for premium users was added in CIT-26
+* Building the chat functionality was completed in CIT-28
+* Creating and viewing other users profiles was completed in CIT-18 and CIT-19 
+* Contact page was added in CIT-31
+
+#### Goals and/or tasks that were planned but not met/completed:
+
+ * CIT-45: Making the page visually appealing
+This has not been completed yet as each team member has been working on different elements of the project, and now that the project is coming to a close, only now do we have all the pages completed for us to be able to ensure that the formatting and layout are consistent across the website
+
+ * CIT-24: Indicating tickets have been prepaid for   
+This task has the majority of its functionality in place, and the reason it has not been considered as completed is that bugfixes are continuing to be made before deploying the final product
+
+ * CIT-30: Viewing individual tickets
+This task has not been completed yet as a blocker is being faced with our implementation of a QR-code on the tickets, which we aim to correct by the final presentation
+
+## Meeting Highlights
+
+Since this is the final iteration, our main insights are:
+
+* Maybe, dividing work into large, complex blocks when their functionality is
+first being implemented and then allowing smaller tickets to build off the complex
+blocks would have been a better development model. Several times, user stories
+in virtually the same domain, where one depended on the other, were being worked
+on at the same time until a blocker prevented any further work.
+* Settling on and determining our tech stack as early as possible would have 
+greatly reduced the amount of time spent per sprint simply figuring out what
+tools were suitable for a particular problem. For example, we only added Stripe
+and Ably as third-party providers for payment and messaging respectively this sprint.
+We had known from the start that we would at least implement messaging and quite
+a bit of time was spent selecting Ably as the provider this sprint. This time 
+could have been better used on development work, with sprint 0 having been used
+for the research.
diff --git a/doc/sprint4/system_design_document.pdf b/doc/sprint4/system_design_document.pdf