Skip to main content

Product Manager Onboarding

1. Introduction

  • Welcome to the team! We are excited to have you as a product manager for our next project cyclecycle.

    • As a Blueprint PM, you are the future of the organization

  • Purpose of the Runbook

    • Explain the goals of the onboarding process.

    • Outline whatthe scope of the developerproduct canmanager expect to learnrole.

2.  Blueprint Overview

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

3.  Team and Role Responsibilities Responsibilities 

  • Organize project team and NPO meetings

    • Project teamsteam meetmeetings weeklymay consist of:
      • Standup – Quick updates on progress
      • NPO feedback review(if applicable)
      • Task Review – Evaluate ongoing/completed tasks and address any concerns.concerns
      • NPO feedback review (if applicable)
      • Task Assignment – Define and assign tasks for the upcoming week.
        week

      • Open Discussion – Address any additional topics or unplanned updates

    • Weekly meetings will alternate between standup and sprint planning/review. More info linked down below
    • NPO meetings occur monthly and consist of: 
      • Progress Report – DIsplay project progress to stakeholders  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 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  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 project 
      • Github taskboard, Jira, Notion, etc.. .

4. Learning Resources and Documentation

5. Communication Channels  Channels  

  • For Project Team  

    • GitHub Task Board

    • Meeting Minutes Minutes 
    • Discord Channels Channels 
  • For NPO NPO 
    • Google meet, zoom, etc...
    • Email
    • For fast/urgent communication communication 
      • Slack, Discord, etc...


Back to top