Assignment Points Grade Evidence
Sprint 1-3 Review Ticket 3   Sprint 1 Student Skill Check & Sprint 1 General Checklist and Hacks & Planning Part 1, Planning Part 2 & Sprint 2 Review & Sprint 2 Team Teach Planning. I put some links to previous sprint review tickets for reference and so that you can see my past achievements and compare them with today to view my progress. This also serves as a useful tool for me of things I tried, things that failed, and things that worked.
Sprint 3 Team Issue(s)/Plan 2   Tinkle Time Project Board, Team Planning Issue. These links are more important! I listed our GitHub project board which we used for our repository. This was super useful in keeping track of what features to add, what to work on, and to make sure we knew who was doing what. We chose to designate certain features to different people, and the board let us visualize that. It was also useful for ideation. During our ideation, we had all our group members randomly throw out different ideas. And during that, I would just sit and write them down. After wards, we chose which ideas to implement. However, being able to brain-dump and spew out every possible idea we had (even if it’s terrible) is super useful. I also linked a GitHub issue we used to plan out features.
Beginning-2-End Contribution 2   UI Testing, Dark Mode Testing. Profile Page Overhaul, Corrective Iteration of Lillian’s Code. Adding MyPlan to backend. All of these links are evidences of iteration and design testing. We chose to use a clean style with a bit of depth to add character. The UI tests helped us visualize what the site looked like. While backend is more important, we felt that getting a visual (even if it’s basic) helps a lot to align our ideas and envision the final project. There are also links to my corrective coding such as helping out Lillian’s code as well as my main feature which was adding MyPlan and account creation to the backend.
N@tM Team Presentation 2   image Here is a cool photo of our presentation! It was super fun, and a lof of people we met were actual software engineers, so it was interesting to hear their thoughts and ask what they use in real life scenarios.
Live Review Indi Demo 1   image image Here is a snipped of our Google Form. We made a form so that anyone who sees our presentation can leave feedback. We collected statistics on our audience demographic and one of the screenshots is from Rachit’s feedback (alumni).
Total 10    
Skill Points Grade Evidence
Work Habits (Analytics) 1   image My analytics.
Evidence of Role in Team 1   image image image image Here are some images from our Slack groupchats and me communicating to the team. I think an important skill is being able to communicate to team members, especially when you are working on different features. You need to be able to clarify things or ask for help, so I chose to list examples of that.
Function / Purpose Design 1   image image Here is a screenshot of our database and the feature that I worked on! It allowed users to create their own account as well as add a MyPlan user ID to help keep better track. We wanted to do official integration with MyConnect’s API’s, but we realized that we needed to access a school admin account to do so which we can’t. We thought about adding a “sign in with Google” option, but you need to own the domain to the website which we also can’t do.