rohinsood
commented
9 months ago Individual Review "Rohin" grading "Paraas"
- [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 - .8
- [X] Issue(s) that show plans/progress to team objectives - .78
- [X] Highlights of key commit(s) in Issues, summarizes code contributions - .8
-
[X] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks - .75
Per check.
0.55 not attempted/no check 0.7 attempted, incoomplete, but some runtime 0.8 mastery and runtime 0.9 above and beyond.
Positive Comments
-
Video Demonstration
- Created a 1-minute video showcasing a web demo of significant contributions to the project.
-
Planning and Progress Documentation
- Contributed to Iteration Review, Mini-Project Check-In, Team's Review Ticket (self-created), Ideation Key Commits, and Individual Check-In to demonstrate planning and progress toward team objectives.
-
Key Code Contributions
- Solely responsible for the frontend development, including the implementation of Bubble Sort and contributions to the API controller.
-
GitHub Analytics Review
- Regularly reviewed Frontend GitHub Analytics and Backend GitHub Analytics, demonstrating consistent participation over three weeks.
-
Effective Communication and Documentation
- Active involvement in various documentation aspects, including team reviews, check-ins, and planning, reflects a commitment to effective communication within the team.
-
Technical Proficiency
- Sole responsibility for frontend development, especially the implementation of Bubble Sort, showcases technical proficiency and individual coding skills.
-
Consistent Participation
- Regular engagement in reviewing GitHub analytics for both frontend and backend indicates sustained commitment and contribution throughout the project.
Overall Evaluation
-
Comprehensive Involvement
- Active participation in planning, coding, and documentation highlights a well-rounded contribution to the team.
-
Demonstrated Leadership
- The initiative to create the Team's Review Ticket indicates leadership and a proactive approach to project documentation and evaluation.
-
Alignment with Team Objectives
- Tangible contributions align with team objectives, showcasing a clear understanding of project goals and active efforts to achieve them.
Individuals Video, Issue(s), Commits(s):
Images
Frontend Analytics:
Backend Analytics:
Reflection:
Reflecting on our project's initial challenges, it's evident that we encountered a rocky start in the first week. However, the silver lining was our ability to rebound and learn crucial lessons along the way. The paramount takeaway from the initial phase was the absolute necessity of consistent and open communication within the team.
In response to the communication challenges faced during ideation, we've decided to adopt a more inclusive approach. Instead of zeroing in on a single idea, our strategy now involves generating 3 to 5 viable concepts. This way, we can present the options to Mr. Mortensen, fostering a collaborative evaluation process to determine the most promising direction. This approach aims to mitigate complications regarding the purpose of each idea and whether that purpose holds significance.
Despite the hurdles in ideation, there were notable achievements in other aspects of the project. The meticulous assignment of roles within the team proved instrumental in streamlining our workflow. Ensuring that all designated features were completed contributed to our ability to deliver a finished project by the stipulated due date.
However, as we assess areas for improvement, it's evident that certain technical aspects could be refined further. The front-end, in particular, left room for enhancement. The styling was rudimentary, with the use of basic div elements for the sorting animation. This minimalistic approach, while functional, resulted in a visually unappealing presentation, and the page experienced disruptions during the animation phase.
On the backend, our communication regarding the system's operations could have been more seamless. A more transparent and consistent flow of information would have enhanced the team's understanding of the backend processes, fostering a more cohesive and synchronized development environment.
In summary, while we managed to complete the project adequately, there is a clear acknowledgement that there is room for improvement. The lessons learned, particularly in the realm of communication and collaborative decision-making, will undoubtedly serve as valuable foundations for future projects. As we reflect on this experience, our commitment to growth and improvement remains steadfast, and we are poised to leverage these insights to elevate the quality of our work in subsequent endeavors.