Ryanrob327
commented
10 months ago Team Review "Scrum Master Ryan" grading "Scrum Master Jishnu"
- [x] The team should have a Web Page(s) that teach/explain: Fibonacci, Algorithm, etc. (0.9) nice use of graphs, they look clean and explain the quantitative aspect very well.
- [x] The team should have a Web Page(s) that teach/explain: Sorting, Timing, Compares Swaps, etc. (0.9) graphs demonstrate the aspects of algorithms well, good for visualizing numbers.
Team Review ticket containing key Team and individual contributions
- [x] Growth/Accomplishments in work is according to historical Team Plan, or they show revisions to plan according to work (0.9) I like the evidence of improvement by looking at previous plans and review tickets and how they adapted to the advice provided, I also like how they mentioned Mr. Mort's advice and made changes accordingly.
- [x] Short falls/Improvement that could be made in Work or Team Plan, team highlights next steps or improvements that could be made (0.85) good job talking about it, could use more evidence of short falls like they did with growth.
- [x] Showing key accomplishments according to requirement in Java Backend such as API, Abstract Class(es), Inheritance, Polymorphic behavior, Sorting Algorithms, etc. In Sorting, there should NOT be static classes or static methods. (0.9) all requirements met, demonstrated good use of java knowledge, clearly prepared for AP requirements
- [x] Showing key user interaction and learning(s). For instance how you visualized Sorting Algorithm: Bubble, Insertion, Selection, Merge... how you captured Big O, analytical data, usage of Data Structures... And/or, how you provided response and Feedback to user on their success in learning or experiencing your interface. (0.85) The graphs used in the frontend were a good demonstration of the quantitative results from the algorithms, however, I feel that this project could use more creativity to create engagement.
Freeform comment
- I love the way the graphs look, and how they can overlap on top of past graphs
- Very number oriented project which is great for educational purposes, but it would be nice to see a bit more creativity
Overall score
(0.88333/1) - very clean, I think the graphs are a great way to represent quantitative data in visual form. Good for educational purposes.
Team
Individuals
Fibonacci and Sorting Blog
Fibonacci Blog Sorting Blog
Growth/Accomplishments
Initial Ticket --> Mid Review Ticket --> Ticket after Review
As a team, we have definitely grown and we have reflected based on the review. Fixes such as implementing inheritance into Fibonacci was something that was required hugely by the requirements.
We also made major reflections and developed the code to fit accordingly, for example, another thing that we were largely criticized for was the fibonacci sequence not displaying the steps taken to the solution and we adapted the code to fix that issue as well as the issue that our API set up was weird, we fixed that issue as well based on the feedback provided
Short falls/Improvement
As a team, I felt like there was a lack of collaboration. Although at times we were successfully moving our way through the project, the lack of collaboration dragged us down at the end.
Another issue that was something that was a short fall was the lack of a designated leader/person to make sure that everything was being worked on as well as manging and controlling the parts that everyone works on, dragging us down.
Another short fall is the lack of emphasis on the frontend side of things, we had the backend completed and done but we didn't put enough emphasis into creating a body or working with the frontend to display what we created on the backend.
Individual Contributions
What we worked on after the 12/11 (Monday) Review:
The Amazing Kaiden Do wrote the Sorting backend up and the Outstanding Duo Jishnu and Derrick debugged the code because Kaiden's machine was broken. Jishnu completed the frontend connection. AYYYYYYY!!! Got Sorting Working Frontend for sorting
Team Improvement
As a team, we started off quite fractured with only minimal communication whilst in school. As we progressed through the project, we made a Discord chat to keep up on work and stay on track. Working through problems on call and even going to each other's houses, our collaboration increased tenfold. We pushed each other and guided each other to learn and do better in our code skills.