Curriculum 101
Product Thinking
Product Documentation
Prioritization Frameworks
Agile & Development
100

What is product management? 

Definition: "Product management is an organizational function that guides every step of a products lifecycle- from development to positioning and pricing- by focusing on the product and its customers first and foremost"

100

“This early version of a product includes only core features to validate assumptions with users before full development.”

MVP (Minimum Viable Product)

100

This document is used by PMs to clearly communicate feature goals, user needs, and requirements to engineering and design teams.

Answer: Product Requirements Document (PRD) 

100

This framework stands for Reach, Impact, Confidence, Effort.

RICE

100

A short, time-boxed development cycle in Agile is called this.

Sprint

200

Product management is at the intersection of which 3 key areas?

User Experience (UX), technology & Business

200

“When a PM conducts interviews or observes users to uncover pain points and motivations, what key skill are they applying?”

user empathy

200

Which section of a PRD would you reference to justify to stakeholders why building a new feature solves a user problem?

Problem statement / background

200

What does MoSCoW stand for?

This prioritization method uses Must have, Should have, Could have, Won’t have.

200

This meeting is held daily to sync the team.

Daily Standup

300

Which tool is used by product managers to plan a product lifecycle that is also a shared source of truth?

Product Roadmaps

300

“When mapping all touchpoints a user has with your product, from discovery to final action, what is this called?”

user journey

300

If a PM wants to know whether the feature increases retention or engagement, which PRD section should they look at?

Metrics / success criteria

300

“In a scoring framework, you want to estimate feature adoption across your user base. Which RICE component helps you do this?”

Reach

300

This Agile artifact lists all work items.

Product backlog 

400

This concept means building, measuring, and learning quickly.

Iteration

400

“To decide whether to build a feature, a PM formulates a ______, which will later be tested. Fill in the blank

Hypothesis

400

“Where in a PRD would you detail the user flows, functional requirements, or stories describing exactly how the feature works?”

Requirements/User Stories
400

A PM is scoring a feature using RICE. The feature has the following scores:

  • Reach (R): 4 (reach 4/5 of our user base)
  • Impact (I): 3 (on a scale of 1–5)
  • Confidence (C): 4 
  • Effort (E): 4 (on a scale of 5)

Question: What is the RICE score?

4*3*4/4 = 12 

400

This role is responsible for maximizing product value in Agile teams.

Product Owner

500

Describe Nidhi's product project.

+100 if you can describe the product project that won that year. 

Crampus - help students find study spots on Campus.

500

“You are a PM at Spotify. Data shows that users skip 40% of recommended playlists. You want to improve engagement. What's the first thing you do to test why users are skipping?

Conduct user research / gather qualitative insights

500

A PM needs to ensure that the engineers know how to build, designers know how to design, and the business knows why. Which three groups does a PRD align?”


  • Engineering, Design, Business 
500

You are a PM at Netflix and have two feature ideas:

Watch Party

-Reach (R/5): 4

-Impact (I/5): 3

-Confidence (C/5): 4

-Effort (E/5): 3

Personalized Trailers

-Reach (R/5): 3

-Impact (I/5): 5

-Confidence (C/5): 5

-Effort (E/5): 4

  1. Calculate the RICE score for both features.
  2. Which feature should you prioritize if you can only pick one?


  • Personalized Trailers → 18.75 ✅ prioritize first
  • Watch Party → 16


500

Name 1 of the 12 principles of Agile Methodology.

  • Customer – satisfaction via early/continuous delivery
  • Change – welcome changing requirements
  • Delivery – frequent working software
  • Collaboration – business & developers work together
  • Motivation – build around motivated individuals
  • Communication – face-to-face preferred
  • Progress – measure by working software
  • Sustainability – maintain pace indefinitely
  • Excellence – technical quality & good design
  • Simplicity – maximize work not done
  • Self-organization – teams decide how to work
  • Reflection – regularly improve processes
  • Customer satisfaction through early and continuous delivery of valuable software
  • Welcome changing requirements, even late in development
  • Deliver working software frequently, from a couple of weeks to a couple of months
  • Business people and developers must work together daily
  • Build projects around motivated individuals
  • Face-to-face conversation is the most efficient and effective method of conveying information
  • Working software is the primary measure of progress
  • Agile processes promote sustainable development
  • Continuous attention to technical excellence and good design
  • Simplicity—the art of maximizing the amount of work not done—is essential
  • Self-organizing teams produce the best architectures, requirements, and designs
  • Regularly reflect on how to become more effective, then tune and adjust behavior accordingly