Visions and Goals
Overall Visions
What do you want your team to achieve overall this year?
more degree support
cleaner codebase
subcomm that can do work
a positive feedback loop on advertising
a good foundation for future teams
BETTER DOCUMENTATION
Who do you want to improve the lives of and how?
UNSW students that arenโt just enrolled in CS
Double degree enjoyers, etc
ย
Principles
Whatโs a rule or way of leading that you want to follow/live by this year?
commitment to your promises
not being afraid to make mistakes/changes
you can never over communicate
open company, no bullshit
ย
Project Features/Tasks
degree support
social degree-tabling
friends
ability to search someone zid and get their degree plan
some way to show your friends taking a term when you drag a course
how many people total are planning this course in this term
NOT SYNCHRONOUS
public API
enables social timetabling
would be paired with a privacy page where users can disable certain endpoints
public/friends/no-one
context menu changes
how to use circles tutorial popups
streamline degree selector page
no-degree mode
backend changes to allow for no degree
frontend to disable certain features if no degree
unilectives integration
better breakpoints
disable the old Jira automation
transcript parser
allow having failed courses on planner
align course data to users start year
explore postgrad
graphical selector tabs
TESTING
frontend unit tests
VR/snapshot tests
storybook examples
Done by directors:
split the API
events and feature flags for new features
Moonshots/Would be nice :
Every degree
Post graduate
Full social degree-ing
auto degree planning
degree adding UI
degree profiles (like notangles timetable tabs)
guest accounts / no log in mode**
allow having failed courses on planner
align course data to users start year
Achieve by end of the following Term | Goal |
---|---|
T1/Subbie Onboarding | degree selector improvements, transcript parser frontend, breakpoints, unilectives integration, context menu |
T2 | no-degree mode, testing, wider degree support, explore public api & social timetabling (friend support) |
T3 | social timetabling cont. if it works out, wider degree support, course recommendation |
ย
Goals for Leading Subcommittee
I LOVE BONDING
I LOVE DRINKING
Team dynamic
good split between tickets and bonding
good banter
grind sessions every flex weeks
in person meetings
pairing on larger more indepth tasks
outing ideas
hitting the pub
pool
restaurants
bowling
possible bouldering
meetings โ weekly
IN PERSON
weekly standups if possible; meetings can always be grind seshes
retros at end of big features, 1 end of each term
ideation sessions once a term
flex week grind sessions
public confluence minutes
decision logs when making decisions about features
subcom check-ups
actually make it happen
bi-termly, can slow down in later terms
less engaged people get more reaching out