Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VRMS specs and UI requirements #1473

Open
32 tasks
juliagab56 opened this issue Aug 24, 2023 · 1 comment
Open
32 tasks

VRMS specs and UI requirements #1473

juliagab56 opened this issue Aug 24, 2023 · 1 comment
Assignees
Labels
draft Not ready for prioritization yet feature: Product Specs role: Product role: UI/UX research size: 2pt Can be done in 7-12 hours

Comments

@juliagab56
Copy link
Member

juliagab56 commented Aug 24, 2023

Overview

This issue is to keep track of the various UI requirements for all screens in VRMS and the specifications for the existing and upcoming features. Here stakeholders, PMs and Designers can keep track of validated specs, reqs and priorities and make note of any changes.

Action Items

1. Stats

  • What stats are important to display?

2. Project information

  • What info is needed?
    • Name of project
    • Description
    • Current members (active)
    • History of members (past/inactive)
    • Github URL
    • Slack channel link
    • Google drive URL
    • Location (remote/in person)
    • Project Status:
      • Active - A project that currently has assigned team members and has meetings.
      • On Hold - A project that we might bring back in the future. It is waiting to be prioritized.
      • Completed - A project that we have wrapped up.
      • Archived - A project that did not get completed and that we will not be reactivating.
      • Deleted - A project that was created as a test, or otherwise is not real.
    • Is there any special validation needed?

3. Events information

  • What info is needed?
    • Name of event/Practice
      • Admin
      • Content
      • Data
      • Design
      • Dev (Engineering)
      • DevOps
      • Fundraising
      • Marketing
      • PM
      • Research
    • Attendees
      • Lead
      • Jr. Lead
      • Team Member
    • Day of Week
    • Start Time
    • Duration
    • Cadence
      • Does Not Repeat
      • Weekly
      • 2x per Month
      • Every Other Week
      • Monthly
      • Other
    • Video Conference Link
    • Video Conference Platform/Room
      • Team Member's Personal Zoom
      • Unknown
      • Bonnie's Zoom link
      • CTS Zoom 1
      • CTS Zoom 2
      • CTS Zoom 3
      • CTS Zoom 4
      • Team member's Personal Teams
      • Google Meet

4. Users information

  • What info is needed?
    • Name
    • Email
    • Projects they're on (active)
    • History of projects (past/inactive)
    • Status (active/inactive)
    • Privacy policy

5. Dashboard

  • What info should be displayed?
    • Upcoming events
    • Notifications
    • HfLA news/updates
    • Stats
    • Current tasks/projects

6. Check in

  • What is the value of checking in?
  • What events can you check into?

7. Onboarding

  • What steps MUST users be present for?
  • What steps COULD users do async?
    • Pre-meeting
    • Post-meeting

Resources/Instructions

  • What teams does VRMS affect?
  • What cross team partnerships does VRMS have?
@JackHaeg
Copy link
Member

JackHaeg commented Sep 14, 2023

See for more info re: names: #1409 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
draft Not ready for prioritization yet feature: Product Specs role: Product role: UI/UX research size: 2pt Can be done in 7-12 hours
Projects
Status: Agendas & Resources
Development

No branches or pull requests

3 participants