12 semanas · intensivo
Para quien tiene plazo
Unas 8 horas por semana, en 1 ciclo centrados en las brechas que más pesan.
Carrera en 2026 y 2027
Product Owner
A Product Owner decides what a team builds next and why, turning user needs and business goals into a prioritized backlog the team can deliver. The role grows from writing clear stories, to choosing and measuring what matters, to aligning executives and other teams around a strategy.
Contenido revisado el 20 de octubre de 2026
- Niveles
- 4
- Habilidades mapeadas en Mid-level
- 8
Lo que cada nivel debe demostrar
Mid-level
Accountable for deciding what the team builds next and showing, with numbers, why that choice beats the alternatives.
You own a backlog and a roadmap instead of only feeding them. You rank competing requests, read funnels and a core metric to see whether shipped work moved anything, and defend trade-offs to stakeholders. Compared with junior work, the question changes from how to write it well to whether it should be built at all.
Puntuación media exigida: 72%
User Interviews
Por qué: You can design interview rounds to test a specific assumption behind a roadmap bet, and recognize when answers only confirm what you hoped to hear.
Persona Development
Por qué: You can decide which segment a quarter's work serves and say no to requests from segments you chose not to prioritize, citing the persona data.
User Story Writing
Por qué: You can keep a backlog healthy across several sprints, re-slicing large epics so that each story still delivers visible value on its own.
Acceptance Criteria
Por qué: You can catch edge cases and error states in criteria during refinement, so they do not appear as bugs after release.
RICE Framework
Por qué: You can score ten competing requests with Reach, Impact, Confidence and Effort and explain to a disappointed requester why theirs ranked lower.
Roadmap Planning
Por qué: You can build a roadmap around outcomes rather than a feature list, leaving room for the delivery slips and surprises that always arrive.
North Star Metrics
Por qué: You can pick the single metric that reflects delivered user value and reject vanity numbers like sign-ups when judging whether a release worked.
Funnel Analysis
Por qué: You can locate the step where users drop off in an onboarding or checkout flow and propose the experiment that tests the likely cause.
Estudia para Product Owner: rutas y simulacros
Cada nivel de esta carrera corresponde a una ruta de estudio. Lee gratis el mapa completo de temas y luego mide tu nivel.
Dos caminos para subir un nivel
40 semanas · regular
Junto al trabajo
Unas 4 horas por semana, en 3 ciclos. Cada ciclo lleva lo que quedó pendiente del anterior.
Preguntas frecuentes
¿Qué es Product Owner?
A Product Owner decides what a team builds next and why, turning user needs and business goals into a prioritized backlog the team can deliver. The role grows from writing clear stories, to choosing and measuring what matters, to aligning executives and other teams around a strategy.
¿Qué debe demostrar cada nivel de Product Owner?
Product Owner está mapeado en 4 niveles: Junior, Mid-level, Senior y Expert. Abre cada nivel arriba para ver las habilidades que debe demostrar.
¿Cuánto dura el plan de Product Owner?
El plan tiene 2 ritmos: 12 semanas por nivel, con unas 8 horas por semana (intensivo) y 40 semanas por nivel, con unas 4 horas por semana (regular).
Cómo funciona el plan
Tutor IA
Una sesión de estudio para cada tema nuevo, a tu nivel.
Escuela de IA
Clases prácticas de uso de IA en el día a día de tu carrera.
Evaluaciones
Cada requisito se demuestra midiendo, no marcando una casilla.
Revisión de etapa
Al final de cada ciclo ves qué avanzó y qué pasa al siguiente.
Descubre en qué nivel estás
Un diagnóstico corto mide las habilidades que ya tienes. El recorrido empieza ahí.