Product Manager Onboarding

Welcome to the team! We are excited to have you as a product manager for our next project cycle
- As a Blueprint PM, you are the future of the organization
Purpose of the Runbook
- Explain the goals of the onboarding process.
- Outline what the developer can expect to learn

Blueprint is a student organization created to serve Non-Profit Organizations(NPOs) by providing them with free web or mobile app development

Organize project team and NPO meetings
- Project teams meet weekly consist of:
  - Standup – Quick updates on progress
  - NPO feedback review(if applicable)
  - Task Review – Evaluate ongoing/completed tasks and address any concerns.
  - Task Assignment – Define and assign tasks for the upcoming week.
  - Open Discussion – Address any additional topics or unplanned updates
- NPO meetings occur biweekly and consist of:
  - Progress Report – DIsplay project progress to stakeholders
  - Open Discussion – Ask any relevant questions regarding the project or project status
Define Tasks/Features to be implemented
- Create user stories and task descriptions for developers to implement
- Work with the Tech Lead decide technical implementation of tasks/features
Set goals and Timeline
- - Set goals for each meeting and sprint
  - Determine the timeline of the project
    - What features can be done by the MVP, by the final product handoff?
    - What features need to be cut?
      - If so, how should I tell the NPO?
Team Dynamics/Hierarchy
- The project team hierarchy is as such: PM & Tech Lead --> Designer & Developers
- PMs have the final say in all decisions
  - Decide what can and cannot be done
- Determine priority of tasks/features
Track Project Progress
- Utilize time management applications to track status of project
  - Github taskboard, Jira, etc..

For Project Team
- GitHub Task Board
- Meeting Minutes
- Discord Channels
For NPO
- Google meet, zoom, etc...
- Email
- For fast/urgent communication
  - Slack, Discord, etc...