Product Owner và Backlog Management

Product Owner Role Deep Dive

PO Responsibilities

Strategic:
- Product vision
- Roadmap
- Stakeholder management
- Business value maximization

Tactical:
- Backlog management
- Prioritization
- Refinement
- Acceptance criteria

Day-to-day:
- Answer team questions
- Clarify requirements
- Accept/reject work
- Attend ceremonies

PO Anti-Patterns

1. Proxy PO (không quyết được)
2. Committee PO (nhiều PO)
3. Part-time PO (không focus)
4. Absent PO (không available)
5. Micromanager PO
6. Order-taker PO (chỉ ghi yêu cầu)

User Story

Format

As a [type of user],
I want [some goal]
So that [some reason/benefit]

Ví dụ:
As a registered customer,
I want to save products to a wishlist,
So that I can buy them later.

As an admin,
I want to export user data to CSV,
So that I can analyze it in Excel.

INVEST Criteria

I - Independent: Không phụ thuộc story khác
N - Negotiable: Không phải contract cố định
V - Valuable: Có giá trị cho user
E - Estimable: Có thể estimate
S - Small: Fit trong 1 sprint
T - Testable: Có thể verify

Acceptance Criteria

Format: Given-When-Then

Story: User login

Acceptance Criteria:
1. Given I am on login page
   When I enter valid credentials
   Then I am redirected to dashboard

2. Given I am on login page
   When I enter invalid password
   Then I see error "Invalid credentials"

3. Given I enter wrong password 3 times
   When I try again
   Then my account is locked for 30 minutes

4. Given I am on login page
   When I click "Forgot password"
   Then I see password reset flow

Story Splitting

Ví dụ: User Story "Search products"

Too big (13 points): 
"As a user, I want to search products"

Split by workflow:
- Search by keyword (3)
- Search with filters (5)
- Search suggestions (3)
- Search history (2)

Split by data:
- Search products only (3)
- Search products + categories (5)
- Search all content (8)

Split by platform:
- Desktop search (5)
- Mobile search (5)
- API search (3)

Story Mapping

User Activities (backbone):
Browse → Search → Add to Cart → Checkout → Pay → Confirm

Tasks (walking skeleton):
Browse: 
- View homepage
- View category
- View product detail

Search:
- Search bar
- Filters
- Sort

MVP line (draw horizontal):
- All "Browse" tasks
- Basic "Search"
- Basic "Add to Cart"
- Simple checkout

Then add:
- Advanced search
- Recommendations
- Multiple payment
- etc.

Backlog Management

Backlog Structure

Epic (large feature)
├── Feature 1
│   ├── User Story 1.1
│   ├── User Story 1.2
│   └── User Story 1.3
├── Feature 2
│   ├── User Story 2.1
│   └── User Story 2.2
└── Feature 3
    └── ...

Ví dụ:
Epic: "E-commerce Platform"
├── Feature: User Management
│   ├── Story: User registration
│   ├── Story: User login
│   └── Story: Password reset
├── Feature: Product Catalog
│   ├── Story: Product listing
│   └── Story: Product detail
└── Feature: Shopping Cart
    ├── Story: Add to cart
    └── Story: Remove from cart

Prioritization

MoSCoW Method

Must have: Critical, non-negotiable
Should have: Important, not critical
Could have: Nice to have
Won't have: Not this time

Ví dụ (cho MVP):
Must:
- User registration
- Product listing
- Add to cart

Should:
- Search
- Filters

Could:
- Wishlist
- Reviews

Won't (now):
- Social features
- Advanced analytics

Weighted Shortest Job First (WSJF)

WSJF = Cost of Delay / Job Size

Cost of Delay = User Value + Time Criticality + Risk Reduction

Ví dụ:
Story A: Value=8, Time=5, Risk=3, Size=3
WSJF = (8+5+3)/3 = 5.3

Story B: Value=5, Time=5, Risk=2, Size=1
WSJF = (5+5+2)/1 = 12

→ B first (higher WSJF)

Kano Model

1. Must-be: Có thì không khen, thiếu thì chê
   Ví dụ: Login works

2. Performance: Càng tốt càng hài lòng
   Ví dụ: Faster load time

3. Attractive: Có thì wow, không thì không sao
   Ví dụ: Voice search

4. Indifferent: Không ai quan tâm
   Ví dụ: Feature nobody uses

5. Reverse: Có lại gây khó chịu
   Ví dụ: Too many notifications

Refinement (Grooming)

Khi: Weekly, 1-2 giờ
Attendees: PO, SM, some Dev

Mục đích:
- Clarify stories
- Add AC
- Estimate
- Split if needed
- Re-order

Output:
- Next sprint stories ready
- 2-3 sprints refined ahead

Definition of Ready (DoR):
- Story format clear
- Acceptance criteria defined
- Estimated
- Small enough
- Dependencies known
- Testable

Roadmap

Product Roadmap

Now (0-3 months):
- MVP features
- Core user journeys

Next (3-6 months):
- Enhanced features
- User feedback items

Later (6-12 months):
- Advanced capabilities
- Innovation

Ví dụ E-commerce:
Q1: Basic shopping
- Product catalog
- Cart
- Checkout
- Payment (basic)

Q2: User experience
- User accounts
- Wishlist
- Reviews
- Search filters

Q3: Scale
- Multiple payment methods
- Shipping integration
- Inventory

Q4: Growth
- Recommendations
- Marketing tools
- Analytics

Roadmap Formats

1. Timeline roadmap
   - Gantt-style
   - Risk: Commitments

2. Theme-based roadmap
   - Focus on outcomes
   - Flexible timing

3. Now-Next-Later
   - Simple, honest
   - Recommended

4. Goal-based roadmap
   - OKR-aligned
   - Outcome-focused

Stakeholder Management

Stakeholder Mapping

Power/Interest Grid:

High Power, High Interest:
- Manage closely
- CTO, Head of Product

High Power, Low Interest:
- Keep satisfied
- CFO, Legal

Low Power, High Interest:
- Keep informed
- Regular users, Support

Low Power, Low Interest:
- Monitor
- Peripheral teams

Communication Plan

Weekly:
- Sprint progress email
- Team updates

Sprint:
- Sprint Review demo
- Feedback collection

Monthly:
- Product metrics
- Roadmap updates

Quarterly:
- Strategy review
- OKR planning

Ad-hoc:
- Major decisions
- Critical issues

Metrics

Product Metrics

Value Metrics:
- DAU/MAU ratio
- Feature adoption
- Conversion rate
- Revenue per user

Quality Metrics:
- NPS (Net Promoter Score)
- CSAT
- Churn rate
- Retention

Delivery Metrics:
- Time to market
- Feature cycle time
- Predictability

OKRs

Objective: Improve user experience
Key Results:
- Increase NPS from 40 to 55
- Reduce support tickets by 30%
- Increase feature adoption by 25%

Objective: Scale infrastructure
Key Results:
- Support 10x traffic
- Reduce page load to < 2s
- Achieve 99.99% uptime

Bài tập thực hành

Hãy viết user stories và prioritize backlog!