Chương 14: PRD, User Stories & Product Thinking

"Lan đã dùng AI viết PRD trong 2 giờ thay vì 3 ngày. Nhưng bài học thật sự: 'AI draft, tôi validate. Tôi hiểu user, AI hiểu format.'"
🎯 Mục tiêu
- Viết PRD cho TeamFlow với AI
- JTBD analysis (Jobs-To-Be-Done)
- User stories với Gherkin acceptance criteria
- Backlog grooming & RICE scoring
Phần 1: AI-Powered PRD (25 phút)
Lab: Generate PRD
bash
antigravity "@cm-planning Viết PRD cho TeamFlow:
Include:
1. Problem statement
2. Target users (3 personas)
3. Success metrics
4. Feature scope (Sprint 1-4)
5. Non-functional requirements
6. Risks & mitigations
7. Timeline
Format: Professional PRD template"Key Sections
markdown
## Problem Statement
Small teams (2-20) struggle with project visibility.
Tasks get lost, deadlines missed, no single source of truth.
## Success Metrics
- User onboarding: < 60 seconds to first task
- Daily active users: 50% of registered users
- Task completion rate: 70% within sprintPhần 2: JTBD Analysis (20 phút)
bash
antigravity "@cm-jtbd Phân tích Jobs-To-Be-Done cho TeamFlow:
3 user types: Developer, PM, Business Owner
For each:
- Functional job (what they DO)
- Emotional job (how they FEEL)
- Social job (how they're PERCEIVED)
- Competing solutions
- Switching triggers"Example Output
| Dimension | Developer | PM | Business Owner |
|---|---|---|---|
| Functional | Track my assigned tasks | See sprint progress | Understand project ROI |
| Emotional | Feel in control, not overwhelmed | Confidence in delivery | Peace of mind |
| Social | Be seen as reliable team member | Be seen as organized leader | Be seen as strategic |
| Competitors | GitHub Issues + Slack | Jira + spreadsheets | Weekly email updates |
| Switch trigger | "I missed another deadline" | "I can't see who's blocked" | "What are we even building?" |
Phần 3: User Stories & Acceptance Criteria (25 phút)
Story Format
markdown
As a [PM],
I want to [view sprint burndown chart],
So that [I can identify if we're on track or behind schedule].
Acceptance Criteria (Gherkin):
Scenario: Sprint on track
Given sprint has 20 tasks, 14 completed after 7/14 days
When PM views burndown chart
Then the actual line should be at or below the ideal line
And status badge shows "On Track" in green
Scenario: Sprint behind
Given sprint has 20 tasks, 5 completed after 7/14 days
When PM views burndown chart
Then the actual line should be above the ideal line
And status badge shows "Behind" in orangeLab: Generate Sprint 2 Stories
bash
antigravity "Write 8 user stories with Gherkin AC for TeamFlow Sprint 2:
Features: Comments, File Upload, Notifications, Real-time
Each story: 2-3 acceptance criteria scenarios"Phần 4: Backlog Grooming (15 phút)
RICE Scoring
| Feature | Reach | Impact | Confidence | Effort | RICE |
|---|---|---|---|---|---|
| Comments | 10 | 3 | 1.0 | 3 | 10.0 |
| File upload | 8 | 2 | 0.8 | 3 | 4.3 |
| Real-time | 10 | 3 | 0.7 | 5 | 4.2 |
| Notifications | 8 | 2 | 0.9 | 2 | 7.2 |
Priority order: Comments → Notifications → Real-time → File upload
Homework
- [ ] Complete PRD document
- [ ] 3 JTBD canvases
- [ ] 10 user stories with AC
- [ ] RICE-scored backlog
Chương tiếp: i18n — Sản Phẩm Cho Thế Giới →