Structs Visions and Goals - 2024

• What do you want your team to achieve overall this year?

  • We want to complete the visual debugger with support for arrays (1D and 2D), linked lists, binary search trees and graphs (adjacency lists and adjacency matrices)

  • We want to see COMP1511 and COMP2521 use Structs more to help them through the course - particularly through the new visual debugger feature.

  • We want our subcommittee members to feel both valued with the work they do and have a good time along the way.

• Who do you want to improve the lives of and how?

  • We want to improve the lives of COMP1511 and COMP2521 students (as well as users doing leetcode in C / C++) by making the process of debugging DSA a much simpler process through visualising their code.

• What’s a rule or way of leading that you want to follow/live by this year?

  • We want to train the subcom to took over our role in the future.

  • Skill development → ensure that all of our subcommittee members are learning something and expanding their skillset.

  • Inclusivity → ensure that all subcommittee members feel valued and appreciated for their contributions and dont feel left out at bonding events.

  • Communication → emphasise open and transparent communication to facilitate a collaborative environment, even between members handling disparate tasks, such as keeping people working on a frontend ticket informed about the ideas and progress of those working on a backend ticket.

• What features/tasks do you want to complete? Are they realistic?

  • Break big ones down into smaller achievable goals

  • Make sure to include a ‘deadline’ or time the goal should be achieved by

  • How many people will you assign to this?

    • Pair programming? Individual?

• Any features/parts you want to fix or improve? 

Team members breakdown:

• Debugger backend: 3 people

• Visualiser (frontend): 3 people

• UI / UX: 1 person

• What kind of team dynamic do you want to build?

  • Do you want them to spend most of their time working on tickets? Bonding? (make sure to have a fair split between the two)

  • Bonding: what ideas for fun outings do you want to do as a team? How often would you like them to be?

• How often will you hold meetings? In-person or online? 

  • What will go on in these meetings?

• How will you keep subcoms engaged?

  • Mini presentations within dev sessions showcasing features that were completed → as its very motivating to work on something that you know will be seen

  • Shoutouts\celebration posts for when someone completes a feature/ticket → Created a “small-win” channel on discord for these posts

  • Full-ownership → Give subcommittee members more freedom to choose what features they want to work on or implement their own ideas

• How will you ensure everyone has a good time?

  • Organising bonding events such as badminton, board game meetups, dinners, and other meetups

• How often will you check-up on subcom? 

  • Weekly dev sessions to work on structs or just hang out and bond

    • Will check up on both progress with tickets and also find out how our subcom members are doing outside of Structs e.g. asking them if they feel bogged down by assignments or if they feel motivated to complete some more work

  • Bi-termly showcases within the subcommittee (probs during weekly dev session)