Retrospective Review Ticket

[rohinsood]

Aditya Nawandhar, Rohin Sood, Parav Salaniwal

Project Overview

• Goal: Analyze stock data for 2022 and allow users to determine when an optimal time would have been for buying stocks
• Fibonacci Retracement Levels
  • Calculate stock retracements based on the Fibonacci Sequence
• Monthly Stocks Sorting
  • Sort the months based on their monthly average and chronologically

Team

Crossover Score	Runtime	Plan	Github	Analytics
0.83/0.9	Backend, Frontend	Link	On individual tickets	Backend Frontend

Videos

Individual

Name	Team+Indi+Value	Runtime	Issues	Key Commits	Analytics
Rohin S	1.68 +X	Fibonacci Retracement Generation & Sorting	Issue	FIbonacciGenViaMemo RecursiveSort	Backend Commits ,Frontend Commits
Adi N.	1.67 +X	Selection Sort & Big O Notation	Issue	class code working and selection sorting,sorting and modleinit, some more	backend commits, frontend commits
Parav S	1.64 +X	Monthly Stocks (using Bubble Sort) and Full Frontend	Issue	On personal review ticket	Frontend Commits , Backend Commits

Ideation to Retrospective Reflection #1

What went well

• Workflow management
  • Everyone was on top of their tasks
  • We worked on Fibonacci and monthly stocks on he backend in 2 different branches
  • Each of us managed our frontend responsibilities
  • The backend was deployed immediately
• Feature Implementation:
  • Our features aligned perfectly with our ideation

    What could be improved

• Refactoring
  • In the sake of time, we sacrificed some conventional code structures.
  • All API calls were done in ModelInit.java
• Data Parsing
  • Allow for distributions of all months

[Soham360]

Individual Review Soham Kamat grading Aditya N

• [x] Individual should show that they were key contributor and example to team. This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.

Individuals Video, Issue(s), Commits(s)

• [x] Video, includes Web demo of key contribution to project, 1 minute

  Video was a notebook that had screenshots of code cells. Aditya explained the code and the logic behind it. Well executed. 0.8

• [x] Issue(s) that show plans/progress to team objectives

  Aditya encountered a lot of issues when working on this project and he explain each of them and how he overcame them in detail. 0.82

• [x] Highlights of key commit(s) in Issues, summarizes code contributions

  Aditya had many commits and each commit was vital to the group. One of his key commits showed him creating a many to one relationship between 2 backend APIs. 0.84

• [x] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks

  Aditya had the 2nd most commits in both the frontend and the backend and had a lot of deletions and additions. The analytics graph was not flat at all.

Freeform comment.

2nd highest in both backend and frontend commits. He presented a notebook in the video that contained all important commits. The demo of the animation was smooth and well-executed. Had issues that showed objectives and progress. Explained code thoroughly and displayed a high level of understanding. Vocabulary used during demonstration of code was very good.

Grade Calculations

0.8 + 0.82 + 0.84 +0.83 = 3.29 3.29 / 3.6 * 0.9 = 0.82 / 0.9

Aditya showed extensive use of inheritance and displayed a hight level of understanding for code. Teammate spoke well about Aditya's contributions to the team. Went above and beyond for the animation on the frontend for analytics.

[Krishiv111]

Individual Review "Krishiv" grading "Parav"

• [x ] Individual should show that they were key contributor and example to team. This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.

Individuals Video, Issue(s), Commits(s)

• [x] Video, includes Web demo of key contribution to project, 1 minute
• [x] Issue(s) that show plans/progress to team objectives
• [x] Highlights of key commit(s) in Issues, summarizes code contributions

• [x] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks

  Per check.
  0.83/0.9

  Good Feedback

• Really good implementation of the backend and using non static classes and using bubble sort, and other sort methods in order to truly visualize your stocks
• Good knowledge of CTX graphs to visualize the different type of months , also their seems to be overall good understanding of collaborations

Retrospective

• Seems like you have a good set of work and bubble sort implementation, something you could do in the frontend better is show a better application of the use of bubble sort and the other sort methods, this is because I can see you use a child class the next step is to work on implementing the sorting the backend and the frontend to get a true visasulization, I see the visualization is good but I don't see how it supports the sort methods rather than just providing a graph maybe use buttons to indicate what methods of sort are being used in your outputs.

[PaarasPurohit]

Team Review "Scrum Master A" grading "Scrum Master B"

• [x] The team should have a Web Page(s) that teach/explain: Fibonacci, Algorithm, etc. (0.8)
• [x] The team should have a Web Page(s) that teach/explain: Sorting, Timing, comparing swaps, etc. (0.8)

Team Review ticket containing key Team and individual contributions

• [x] Growth/Accomplishments in work are according to the historical Team Plan, or they show revisions to the plan according to work (0.8)
• [x] Shortfalls/Improvement that could be made in Work or Team Plan, team highlights next steps or improvements that could be made (0.8)
• [x] Showing key accomplishments according to requirements in Java Backend such as API, Abstract Class(es), Inheritance, Polymorphic behaviour, Sorting Algorithms, etc. In Sorting, there should NOT be static classes or static methods. (0.8)

• [x] Showing key user interaction and learning(s). For instance how you visualised the Sorting Algorithm: Bubble, Insertion, Selection, Merge... how you captured the Big O, analytical data, usage of Data Structures... And, how you provided response and Feedback to the user on their success in learning or experiencing your interface. (0.8)

  Per check.
  0.55 not attempted/no check 0.7 attempted, incomplete but some runtime 0.8 mastery and runtime 0.9 above and beyond.

  Freeform comment.
  Provide positives and growth summary.
  Justify or comment on the final score.
  Be sure to provide extra details on anything below 0.7 average or above 0.8.