**Initial · Development → MVP · After MVP → Final · What not to expect**

This doc specifies ways Co-Directors (maybe directors) would work with Project Leads throughout the semester. This is a live document and should be constantly updated and improved as semesters go by and feedback continues. This is more for directors, but also for leads to know what to expect from their directors.

Initial (Lead’s training, Project Scoping, First nonprofit meeting)

• Getting goals from each director and project lead
• Directors give Project Leads Semester Schedule. Important dates:
  • PRD Final Deadline
  • MVP
  • Final Product Showcase
• Setting expectations
  • What directors expect leads to be like. What standards will they hold them up to
  • Ask leads about what they expect from directors (show them this doc and add to this as well)
  • Read Effective Leadership on what we expect leaders to be like
• Directors being there during the first nonprofit call (gives leads a little more peace of mind if it’s their first time doing so)
• Letting leads know that you could help
  • ex: let them know you could provide more feedback throughout their drafting of PRDs, answer questions, help with brainstorming/prioritization, looking over their feature priorities, their tech stack, etc., working with nonprofit
  • But make sure you aren’t micromanaging, and that your help is needed and are not doing their job
• Provide Docs about previous PRDs, thought processes
• Product Review/Discussions with directors + All leads after PRD Drafts
  • This should be after first meeting with teams
• Final PRD Feedback
• Providing tips, especially for
  • Sample First Client Meeting Outline
  • Sample First Team Meeting Outline

During Development → MVP

• Directors sitting in Dev nights
• Lead Meetings that include check-ins almost once a week
  • Slack Check-ins may replace these occasionally
• General Tips and Reminders on Slack
  • Ex: what MVP would look like, reminders to speed up dev process if slow, etc.