In the AI Era, PM/PO's 'Judgment'

From MVP design to reaching PMF, we organize the 'structure of product growth' that product planners must understand, based on practical standards.

From MVP design to reaching PMF, this course organizes the 'structure of product growth' that product managers must understand, based on practical standards.

What does this course cover? 📖

This course goes beyond simple planning methodologies or tool usage, helping you understand why products don't grow, what to experiment with, and when to change direction.

• Understanding the entire flow from MVP design to PMF discovery
• How to grow your product through small-scale experiments
• Strategies and tactics that vary depending on company and product type
• Organizing criteria for what should be considered as Retention for each product type

👉 This lecture is for those who are "doing planning work, but aren't sure if they're on the right track."

Target Audience/Course Objectives 🙆‍♀️

For everyone who is doing planning work or preparing to work as a planner, I want to discuss what you might be missing in actual practice. There is no right answer in planning. However, there are ways to get closer to the right answer.

Target audience as envisioned by the instructor

• Anyone who is currently working as a PM or PO, or preparing to transition into these roles
• PMs and POs who want to manage sprints more flexibly and systematically
• CEOs who are running a startup or preparing to run one
• Designers and developers who want to develop a product planning mindset

If you have these concerns, let's work on them together

• When you're planning a product but communication with developers and designers isn't smooth
• When you receive feedback that your planning is lacking
• If sprints are progressing slower than expected or schedules are being delayed due to unexpected issues
• When you're running a startup but are concerned about product growth
• When you're running small experiments repeatedly but they're not leading to growth results

Learning Content 📚

Sprint Management Know-how

I'll share all the know-how from a PO with 15 years of experience.

Have you had experiences like these while running sprints?

• Work always finishes past the planned schedule
• Work overlaps with the next sprint, making it difficult
• There are so many errors that bug tickets keep piling up
• The backlog is overflowing, but I don't know when or how to handle the work

If you're experiencing these issues, you need to start by examining how you're running your sprints. There are always better alternatives and there's no single right answer. What matters is that you can work together to improve the problems.

I notice that the `` tags are empty - there is no Korean text between them to translate. The surrounding context shows: - Before: Text about examining how sprints are operated and improving problems together - After: Text about sprint cycle setup methods and finding appropriate sprint cycles for the team However, since there is no content between the `` tags, there is nothing for me to translate. Could you please provide the Korean text you'd like translated?

How to Set and Operate Sprint Cycles

We'll explore the appropriate sprint cycle for our team. Regardless of the team's capabilities, the product cycle should vary depending on the product's characteristics. Just because a certain company uses it, does that necessarily mean our team must also operate in 1-week or 2-week intervals?

I'll share methods for calculating and measuring the appropriate team velocity.

I notice the `` tags are empty - there is no Korean text provided between them to translate. However, I can see Korean text in the `` section. If you'd like me to translate those parts: **Before:** Just because a company uses it, does that necessarily mean our team must also operate in 1-week or 2-week cycles? We share methods for calculating and measuring the appropriate pace for your team. **After:** Preparing for sprint planning meetings From writing stories for sprint planning to managing the backlog How should we conduct retrospectives after a sprint ends? Definitely... Please provide the Korean text you'd like translated between the `` tags if you need a different translation.

Preparing for Sprint Planning Meetings

1. From story writing to backlog management for sprint planning
2. How should we conduct retrospectives after a sprint ends? What must be done and what's optional

From writing stories for sprint planning to managing the backlog, how should we conduct retrospectives after a sprint ends? What must be done and what is optional

Jira Software

Learn how to write Stories using Jira Software and monitor sprint progress using Burn down charts.

• Basic Jira Setting Methods
• How to set up Jira Story, Epic, and Sub Task
• How to write a good Story

Requirements Definition Document

We'll explore together the methods and examples for writing a requirements definition document that facilitates smoother communication with developers and keeps the product on track.

• 요구사항 정의서 파일 공유
  • The Requirements Definition Document has been updated to the PRD Template (2025Ver)
  • Where to download the requirements definition document >
• How to Write a Requirements Definition Document and Tips
• Communication with Developers

Figma Wireframe

This guide covers how to use Figma to provide the best guidance to designers, who are partners and companions of POs and PMs, as well as how to create wireframes using Figma.

• Understanding Figma's basic usage and interface
• Creating wireframes using Figma and sharing wireframe creation tools

Prototyping

Let's explore prototyping methods for better communication together

Anticipated Questions Q&A 💬

Q. Can only PMs and POs take this course?
A. Even if you're not a PM or PO, or not preparing to become one, anyone curious about sprint practices can take this course

Q. What is the difficulty level of this course?
A. This course is designed for juniors. We are planning to prepare a separate course for those who have been working in the field for a long time.

Q. I'm preparing for a job change - will this be helpful?
A. If you're curious about startup work processes, you can gain indirect experience

Notes Before Taking the Course 📢

If there are any reference points needed for learning the course, please write them carefully.
This helps students fully understand the content covered in the course and can increase learning satisfaction.

Practice Environment

• Operating System and Version (OS): Windows, macOS
• Tools used: Figma, Jira, etc. Chrome browser linked to a Google account for service registration

Learning Materials

• Learning materials are attached as files in each lesson.

I notice that the `` tags are empty - there is no Korean text provided between them to translate. The surrounding context shows: - **Before**: Information about macOS tools (Figma, Jira, Chrome browser with Google account) - **After**: Career history from 2016-2024 (startup experience, healthcare app roles, lifestyle super app) However, there is no actual content to translate between the `` tags. Could you please provide the Korean text you'd like me to translate?

The person who created this course

• 2024 ~ : Senior PO at Lifestyle Super App Company B
• 2021 ~ 2024 : Healthcare app company G, Product Lead, O2O business, Telemedicine PO
• 2016 ~ 2021 : Started a startup and EXIT
• 2014 ~ 2016 : Head of Healthcare Division at Company Y
• 2011 ~ 2014 : Startup founding and EXIT