Meeting Overview

• Date: January 23, 2025
• Attendees: Amir (Co- Lead), Kata (Strat Apprentice), Chen Yi (Strat Apprentice), Gelon (PM Lead), Spencer (PM Apprentice)
• Purpose: Establish sprint plan

Goals

• Strategy Team introduced to Team Leads.
• Establish Product Strategy Roles and Responsibilities.
• Define Sprint Plan for project.
• Establish Communication Plan for the project.
• Remove team blockers for the project.

Action Items

PS Team Action Items

PS Team Action Items

Notes

Key Discussion Points

1. Scope of Project & Product Deep Dive:
   • Discussion centered around the free tier for creators as the primary focus of the project scope.
   • An optional product deep dive session was scheduled for the next day (5–6 PM EST). Team members were invited to confirm their availability.
2. Document Management & Organization:
   • The need to move documents from Google Drive to Notion was emphasized for better organization and accessibility.
   • Chenyi and Katarzyna confirmed their access to Notion and began updating the workspace with relevant documents such as the product requirements document (PRD) and sprint plan.
3. Sprint Planning:
   • Tasks for the next sprint include:
     • Writing the MVP scope.
     • Reviewing the PRD for critical requirements.
     • Refining the backlog and identifying improvements.
   • The team discussed embedding the sprint plan into Figma for better visibility and creating a Kanban board on the sprint hub linked to Figma.
4. Meeting Attendance & Shadowing:
   • Team members were tasked with deciding which UXR and UXD meetings to shadow to stay aligned with cross-functional teams.
   • Time zone preferences were discussed, with Katarzyna favoring UXR meetings due to her location.
   • Coordination challenges and scheduling conflicts were noted, with plans to revisit meeting attendance in future sprints.
5. Improving Sprint Planning Visibility and Collaboration:
   • Suggestions included:
     • Creating a dedicated Figma file for the sprint plan and embedding it on Notion.
     • Establishing a Kanban board to link tasks and sprint plans.
     • Involving other teams, such as UX and engineering, in the sprint planning process.
     • Scheduling regular sprint planning meetings for review and updates.
     • Assigning cross-functional tasks to encourage collaboration and ownership.