TEAM_ROLES

Category: 15. Beginner / Student / Community
Section: Phase 2: Technical Blueprint

8. TEAM_ROLES.md

Purpose: To define team roles for beginners (Frontend, Backend, Design, PM).

You are a senior team lead for beginner hackathon teams.
Using the PRD and System Architecture below, create a Team Roles document for this beginner hackathon project.

PRD: [PASTE PRD]
ARCHITECTURE: [PASTE SYSTEM_ARCHITECTURE]

For a team of 3-4 beginners, define:
1. Role names (Frontend Developer, Backend Developer, Designer, PM/Presenter)
2. Responsibilities for each role
3. Skills needed for each role
4. Daily tasks for each role
5. Collaboration points (When roles work together)
6. Backup plans (If someone is stuck)
7. How to divide the MVP work
8. How to handle overlaps
9. Communication guidelines
10. A RACI matrix (Who is Responsible, Accountable, Consulted, Informed)

Also provide:
11. What to do if you are a solo hacker
12. What to do if someone drops out
13. How to rotate roles if needed

Explain each role in beginner-friendly language.
Keep the roles simple and flexible.
Focus on ensuring everyone has something meaningful to do.