Product: Update HUU Team Roster

## 🧩 Overview
- Update and maintain the Home Unite Us (HUU) team roster to ensure accurate volunteer information, proper access permissions, and effective team coordination. We need to systematically review and update all team member details to maintain project security, communication effectiveness, and volunteer engagement tracking.

---

## 🎯 Objective
- Complete comprehensive roster update to ensure all team member information is current, accurate, and properly configured for project participation and access management across all platforms and tools.

---

## 🔍 Background / Context
- HUU roster requires regular maintenance to track volunteer participation and manage access
- Accurate roster data is essential for project coordination, communication, and security
- Volunteer status changes frequently requiring systematic updates
- Platform access permissions need to align with current team member roles and involvement
- Related Resources:
- Current HUU roster spreadsheet/database
- Leverage TDM Calculator format

---

## 📝 Scope of Work
- [ ] Core Team Information
- Team Member Status - Verify active/inactive status for all listed members
- Team Role(s) - Update current roles and responsibilities
- Email - Confirm primary contact email addresses
- Slack Name - Verify current Slack display names
- Slack ID - Update Slack member IDs
- GitHub Handle - Confirm GitHub usernames
- Phone Number - Update contact numbers (add dash if texting declined)
- Texting Preference - Confirm yes/no for text communication
- Phone Notes - Add any relevant contact preferences or restrictions

- [ ] Skills and Availability
- Current Skills - Document existing capabilities and expertise
- Skills Interested in Developing - Track learning goals and growth areas
- Availability - Update current time commitment and schedule
- LinkedIn - Verify professional profile links

- [ ] Project Management
- Roster Dashboard - Update Leader (L) or Member (M) designations
- Link Text for Agenda - Verify meeting agenda access and formatting
- Issues Assigned - Review and update current GitHub issue assignments
- Removed From Open Issues At Offboarding - Track cleanup status for departed members
- Involves Volunteer - Confirm volunteer participation status

- [ ] Access Management
- Check HfLA GitHub Member Profile - Verify Hack for LA organization membership
- HFLA Github Member? - Confirm organization membership status
- Github Member is Public? - Verify public visibility settings
- Check Read Team - Verify read access permissions
- Check Write Team - Verify write access permissions
- Check Admin Team - Verify administrative access permissions
- Permission on Google Drive - Update file and folder access levels
- Permission on Figma - Verify design tool access and permissions

- [ ] Administrative Tasks
- Notes - Add relevant administrative notes or status updates
- Files to Move - Identify and relocate files for departed or role-changed members

---

## 📎 Deliverables
- [ ] Updated HUU Roster Database - Complete spreadsheet with all current information
- [ ] Access Audit Report - Summary of permission changes and access updates
- [ ] Offboarding Checklist - Documentation of files moved and access removed for departed members
- [ ] Onboarding Requirements List - Identified gaps requiring new member setup
- [ ] Permission Matrix - Clear documentation of who has access to what resources
- [ ] Contact Verification Report - Confirmation of updated communication preferences

---

## 🧭 Success Criteria
- [ ] 100% Data Accuracy - All active team members have complete, verified information
- [ ] Proper Access Alignment - All permissions match current roles and involvement level
- [ ] Communication Preferences Updated - All contact methods and preferences confirmed
- [ ] Security Compliance - Departed members have appropriate access removed
- [ ] Onboarding Readiness - Clear requirements documented for new volunteer integration
- [ ] Stakeholder Approval - Team leads review and approve updated roster information

---

## 🛑 Risks / Dependencies
- Risks:
- Volunteer availability for information verification may vary
- Some team members may be unresponsive to update requests
- Access permission changes could temporarily disrupt workflows
- Outdated contact information may prevent successful outreach

- Dependencies:
- Cooperation from team members to verify and update their information
- Access to GitHub organization management for permission updates
- Google Drive and Figma administrative access for permission changes
- Slack workspace administrative privileges for member verification
- Coordination with HfLA leadership for organization membership verification

- Coordination Requirements:
- Schedule with team leads for roster review sessions
- Coordinate with GitHub administrators for permission updates
- Align with Google Drive and Figma administrators for access changes
- Communicate roster update timeline to avoid disruption during critical project phases

---
## Action Items
- [ ] Assignee: Assign yourself to this issue.
- [ ] Assignee: Move the issue from Prioritized Backlog to In Progress.
- [ ] Product Manager (Assignee): Conduct the necessary research (if applicable), clarify any questions
- [ ] Product Manager (Assignee): Work with PM team/lead to clarify any questions about the Task/Initiative
- [ ] Product Manager (Assignee): Work with Product Team Lead to assign the appropriate size & complexity
- [ ] Product Manager (Assignee) and Lead: determine if work should be split into multiple issues, if so, create issue(s) and link them in this issue (if applicable) or create as standalone.
- Draft and Review:
- [ ] Product Manager (Assignee): Change Issue Status to "In Progress"
- [ ] Product Manager (Assignee): Draft the issue. Once complete provide for review
- [ ] Product Manager (Assignee): Change Issue Status to "For Review/Feedback Needed"
- [ ] Product Manager (Assignee): Add Label "Ready for: Design Peer Review"
- [ ] Product 1st Level/Peer Review: Review to ensure the issue captures the objective/goal outlined above provides adequate information to Design and Dev, if applicable. Provide comment(s) in the comment section of the issue and tag assignee.
- [ ] Product 1st Level/Peer Reviewer: Change Issue Status to "Questions/Clarification" and add label "Ready for Product.....Persona"
- [ ] Product Manager (Assignee): Change Issue Status to "In Progress"
- [ ] Product Manager (Assignee): Review issue comment(s) and resolve accordingly
- [ ] Repeat above steps until all comments are resolved
- [ ] Product 1st Level/Peer Reviewer: Change Issue Status to "For Review/Feedback Needed" and add label "Ready for: Product Lead"
- [ ] 2nd final/Product Lead: Review and provide feedback (if any) in comment section below, add label "Ready for Product...Persona"
- [ ] Repeat above steps until all comments are resolved

---

## 🔗 Related Tickets / Resources
- Epic: [link]
- Design: [link]
- Engineering: [link]