Final Review Ticket- Rachel

[wrachel]

Overall individual grading: 28/30

scoring explained here

Links to code

main randomization function, additional Student object type

Technical Process/Documentation

Why did this algorithm take me so long?

• I went through multiple iterations of this algorithm in order to reach what I thought to be the most efficient way. It has to be easy to integrate with the front end, which is why it took so long.
• At first, I did it using a 2D array, but I found that to be complicated (especially having to iterate through it every time in order to access the values stored in the 2D array). Then I moved to a more object-oriented algorithm that used an array of a new object type I created (Student).
• I was running into issues where the algorithm wouldn't work when the numStudents was not divisible by numTables --> I had to rewrite parts of the algorithm to accommodate for that (by putting the remainder of the students into tables 0 -> table n until there were no remaining students)
• But this meant that I also had to write another sorting algorithm so that the students names' would be grouped together (easier to manage within the controller/ in the future)

Relevant commits:

0afbc88b010c1e681b9c330526e3abaa29d67dd3 8105a209ddcbf1d577c96caae860c02583184806 87bcd98401e74b1f7f31a1c1533bbb023dd26147 dcbaf04f815c64897e0e3a336f975a7fd9ad9085 6e29fcd23f1b397e2273be84266cf66beda5d107 3bcceac8d0e97dba273510cce5170bad190188fa

overall project reflection:

What I learned from the project was how to iterate, how to go from one iteration of an algorithm to another until it becomes way better. I also learned how to ask for help when I got stuck. Thanks to Calvin, who helped me out with the algorithm. I also got to help out my teammates when they ran into issues :). It was a very wholesome process. I also learned how to manage a team. As the scrum master, I felt for the first time how to simulate a real project with deadlines (3 weeks and checks in between), and how to document progress through review tickets and github pages. It also taught me how to deal with real-life, unforeseeable issues like COVID taking out most of the team.

N@TM reflection:

link to photos N@TM meant sharing our project with people. This taught me how to engage people (since some of them were pretty distracted) and really sell our project. I also learned to be able to use technical terms, but also be able to dumb-down ideas for people who didn't understand the technical aspects.

[wrachel]

Scrum Master grading (Seed): 5/5

Worked diligently in class every day to complete assigned technical aspect, helped out other member in group when they came across issues attended N@TM & engaged with people

[wrachel]

Overall Individual Grading: 32/35

5/5 for Seed see explanation from Scrum Master

Overall Group Grading (explanation from Scrum Master)

19/20 Meeting Tech Guidelines

Individual assignments and completion 4/4

• see tangibles above
• Overall, I think I contributed a lot to helping the project be completed. This meant completing my individual assigned tasks and also organizing review tickets and helping with the commercial, and just doing my role as the scrum master.
• My individual tech contributions were related to data structures & Java (utilized a sorting algorithm & wrote unique java algorithm with "Student" object to fulfill requirements)

Requirements verified and accepted by the sponsor 3/4:

• comments by sponsor is linked here, seemed overall satisfied with our project, but some features could be easier/better to use (e.g. linking the randomization feature to the database so that the database is more integrated).

Presentation at N@TM: 4/4

• pictures linked here
• Had many groups of individuals that we were able to talk to

Presentation to teacher 4/4

• Materials were thoroughly prepared ahead of time, including github pages and review tickets

1 minute commercial video: 4/4

• link
• amazing video in my opinion! very cool animation, well-made visuals, and cool voice over :)

Meeting new tech requirements: 4/5

• has database with multiple tables & meaningful capture e.g. notes, which are described in Github Pages here; but (-1) for not integrating
• application of new tech features not in tech requirements: e.g., randomization feature java code here
• Doesn't have additional distracting features that go against sponsor theme
• authentication and authorization (-1): didn't complete authentication & authorization in time, although attempts were made to. Ultimately ran into too many issues to implement.

Overall, we were organized and followed the timeline closely. Towards the end, our group struggled with efficiency (due to absences because of COVID), but I’m actually really proud of the group for still remaining active in the group chat and through individual messages and getting things done when asked to :). We still made good progress and had an (almost) complete final project to show at N@TM that met most of the tech requirements!

4/5 Teacher Final Assessment

• Documentation of Individual Tech Requirements is in https://wrachel.github.io/PrimitiveApes/database at the bottom
• Includes accurate self-grade assessment
• Documentation of Project here; contains images of tickets/scrum board, notes about maintaining to the master plan, sponsor assessment
• Teacher Assessment (-1): Did not integrate database with the randomization generator