T1 Summary

Summary

Summarize any feedback you got during demos.

All user feedback can be found in shared drive folder titled "Technigala Feedback"
Edit the user flow so after account is created the are automatically logged in
Add an emphasis to the teams
Explain how the stars work
Add a pause message after survey is submitted or emphasize the wait message so they can't move forward in demo until match algo has been run
Add wrong password and email in use alerts
Add a premium service to let new hires receive endorsements
Basic info form is a slight hassle to fill out (autofill certain fields if possible)
Basic info form needs validation for certain fields (zip code, grad year, etc.)
Definitely noticed a handful of people trying to click on the arrow nav bar to switch between pages, so would be nice to enable that during winterim
Some people expressed interest in how we would handle free form text in the team matching survey, would be cool to look into AI summary features

Observations

Record your observations and any insights/conclusions you may have about them. Identify top patterns and write them up. Record the number of email signups you got.

We had less than 10 people signup, I recommend demoing the product more during interim to other users not just Dartmouth students.

Analysis

Is there any analysis you can do of the demos - what percentage of users claimed X or Y. If you had numerical answers was there any statistical significance to the answers?

All individuals who filled out feedback form rated visual appeal a 4 or 5 on a scale from 1-5
Same scoring applied to the usability, but this could be skewed by our pitching

Notes To Future Us

Leave notes to yourself for next term - what should your next steps be?

Create HR and Team portals
Add in LLMs to review the long form responses to surveys (after adding long form text questions to the surveys on New Hire side only)
Add in Diversity metrics (both questions and graphics to compare before and after matching info)
Research Project Management APIs to incorporate next term
Add more qualitative questions to the survey (e.g. remote/hybrid/in-person, working style, personality)

Teamwork

Reflect on how your team is working together

Communication and scheduling will remain a priority
Checking and responding on Slack regularly
Maintain three meetings a week (likely MWF) and schedule additional meetings between frontend and backend people when needed
Keep the off-day check-ins at 9pm (TuThSun)

What has been working well?

give kudos and shoutouts, comment on communication techniques that have worked, pr review practices, etc

Overall things have been working well
We have been fairly communicative via Slack and have relatively good code practices using git flow

What has not?

try to discuss any problems openly and respectfully. communication breakdowns? are some team members taking others tasks for themselves? is anybody ghosting? etc

We could definitely work on our daily check-ins - our communication some times breaks down where we don't know who is working on what
Not too much ghosting this term, but there can always be even less!

Steps

if there are problems, think of some ways to resolve them, go back to your team contract from last term to see what you said you would do for resolution

All good here for now!

Documentation

See the shared drive CS98 - Opportune we should have shared with you. https://drive.google.com/drive/u/0/folders/0AE_Q4f6Yk8WjUk9PVA

dartmouth-cs98-23f / opportune-frontend

Term 1 Summary #74