hackforla / hackforla/VRMS

VRMS specs and UI requirements

Open
#1,473 2 comments 0 reactions 1 assignee Claimed by @juliagab56 View on GitHub
complexity: large draft feature: Product Specs role: Product role: UI/UX research size: 2pt
Dominant language
JavaScript
Stars
61
Forks
101
PR merge metrics
No merged PRs in 30d

Description

### 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?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.