Jupiter Product Meeting Notes

Jupiter Product Updates

• Talk about what y’all did

• Returning team for semester

• Ran surveys with other orgs over summer

• Interviewed a few club presidents

  • Asked “what do you want to give to students?”

  • Response:

    • Events

    • news

    • updates/presentation

    • Ability to contact org members

• Proposed design changes

  • Design for the “Liked” page

    • On Jupiter unmet needs

  • Registered tab

  • Notification tab

Jupiter Project updates

• Talk about current status of Jupiter

• Roadmap for semester

• Team size

• Previously, moved to new design

• Engineering: Achieved partial implementation of new UI

  • Looking to build a larger engineering team to increase pace of UI/backend work

  • Don’t have a large engineering capacity right now

  • Backend is a major focus currently, will influence feature capability

  • Targeting 5-7 new engineers

• Would like 5±2 PM’s for Jupiter

• From Product, need:

  • What do Orgs need

  • What do students want to know about an org

  • Who should be able to join an org/application process

    • Permissions/access control roles

Things to resolve

• Who will be on the Jupiter product team for this semester?

• How will the product team interface w/ Ruben & Sharon?

• How to communicate

  • Jupiter-product channel

    • Will need to create threads for specific topics

    • Want to move all communication to the Jupiter general Discord channels

  • Jupiter team meetings

    • Team meetings Wednesdays @ 7PM in person

  • Recurring meetings with @Ruben Olano + @sharon lnu (Unlicensed) + PM’s outside of meeting times

    • Those who can make it can share info with the rest of the team

  • Planning 4-5 active PM’s for Jupiter

  • Meeting with @Ruben Olano and @sharon lnu (Unlicensed) every two weeks

  • Internal Jupiter Product meetings every week

• Sharon + PM’s will collect focused surveys from stakeholders on campus

Summer Task Update

Work Done by PM Team