Program

Technical Product Owner 360

Technical Product Owner 360 - training program designed to prepare you for modern product roles in tech-driven environments. The program combines business strategy and technical knowledge, covering Agile methodologies, requirement writing (PRDs, user stories), market analysis, prioritization, roadmapping, and collaboration with technical teams. It equips you with practical, job-ready skills to lead products end-to-end.

Application to the program is currently not active
Start date

March 2026

Duration

6 months

Group size

20-25

Schedule

on Tuesday and Thursday at 19:00-21:00

Admission requirements
Age

21 years old və above

Language skills

Knowledge of English at least Intermediate level

Requirement

To have a personal computer or a laptop

Expectation

Product or business oriented mindset is the main requirement; having analytical thinking skills and being open to learning is sufficient

Upon the course completion you will::

You will learn to use Postman, Swagger (OpenAPI), and SQL to test and document APIs, while developing effective collaboration skills with technical teams

You will master writing PRDs, user stories, and tracking plans, and learn how to document requirements clearly and in a structured way

You will gain practical skills in market research, competitor analysis, and identifying customer needs

You will learn Agile approaches (Scrum, Kanban), prioritization techniques, and how to work with roadmaps and OKRs

You will be able to bridge business and technical teams, ensuring effective collaboration between them

Program

Technical Product Owner 360
12

Number of modules

  • PO vs BA vs TPO responsibilities
  • Why “Junior PO” is unrealistic without BA foundation
  • Product lifecycle in tech companies
  • Agile product team structure
  • PO accountability vs responsibility
  • Agile mindset vs Agile rituals
  • Scrum roles, events, artifacts
  • Product Owner in Scrum (real responsibilities)
  • Backlog ownership vs backlog writing
  • Definition of Ready (DoR)
  • Definition of Done (DoD)
  • Sprint planning from PO perspective
  • Requirement types:
    • Business
    • Functional
    • Non-functional
  • Requirement elicitation techniques
  • Stakeholder analysis
  • As-Is / To-Be analysis
  • Scope vs value trade-offs
  • Documentation vs over-documentation

  • Why PO must understand processes
  • BPMN basics (reading & writing)
  • UML overview (what PO must know, what not)
  • User journeys vs business processes
  • Swimlane diagrams
  • Mapping product flows end-to-end
  • Epic → Feature → User Story hierarchy
  • Writing INVEST-compliant user stories
  • Acceptance criteria patterns:
  • Given / When / Then
  • Rule-based AC
  • Edge cases & negative scenarios
  • Traceability: requirement → AC → test
  • System basics:
    • Frontend
    • Backend
    • Database
  • What PO must understand about architecture
  • APIs:
    • REST basics
    • Request / response structure
    • Status codes
  • OpenAPI / Swagger:
    • Reading API documentation
  • Postman:
    • Manual API testing
    • Contract validation
  • Idempotency, retries, timeouts (PO perspective)
  • Why analytics is PO responsibility
  • Event-based analytics mindset
  • Tracking plan creation
  • Event naming & properties
  • Funnels:
    • Conversion
    • Drop-off
  • Retention & cohort logic
  • Metrics vs vanity metrics
  • Analytics-driven backlog decisions
  • Payments lifecycle:
    • Initiation
    • Authorization
    • Settlement
    • Reversal
  • Cards & accounts overview
  • Multi-currency products
  • Open Banking basics
  • Consent & data access
  • Failure scenarios:
    • Timeout
    • Partial success
    • Double execution
  • Compliance mindset for PO (KYC / AML overview)
  • Product vision & problem framing
  • Hypothesis-driven development
  • MVP vs MMP vs full release
  • Prioritization frameworks:
    • MoSCoW
    • Value vs effort
  • Roadmap vs delivery plan
  • Dependency management
  • Business vs tech communication
  • Saying “no” correctly
  • Conflict management
  • PO in meetings:
    • With business
    • With engineering
  • Demo & product review facilitation
  • Written communication standards
  • Realistic FinTech product case
  • Activities:
    • Problem definition
    • Process modeling
    • Backlog creation
    • API contract review
  • Analytics tracking plan
  • Deliverables:
    • Product vision
    • Backlog (epics + stories + AC)
    • Process diagrams
    • API review checklist
    • Analytics events map
  • Team-based execution
  • Mentor feedback loops
  • CV positioning:
    • BA vs PO vs TPO
  • Portfolio preparation
  • Interview scenarios:
    •  Product sense
    • Technical discussions
  • Real job expectations in Azerbaijan market
  • Career paths:
    • BA → PO
    • PO → Senior PO / PM