Ưu tiên: Search > Dark mode > Real-time > Export PDF
RICE Gotchas
✗ Không inflate Reach để push feature mình thích
✗ Không gán Confidence 100% cho everything
✗ Effort phải tính cả testing, deployment, documentation
✗ Review scores với team - tránh bias cá nhân
WSJF (Weighted Shortest Job First)
WSJF từ SAFe framework, ưu tiên theo "cost of delay" - càng delay càng mất giá trị.
Formula
WSJF = Cost of Delay / Job Duration
Cost of Delay = User-Business Value + Time Criticality + Risk Reduction/Opportunity Enablement
Ví dụ WSJF
Feature
Business Value
Time Critical
Risk Reduction
CoD
Duration
WSJF
Priority
Security patch
5
8
9
22
1
22.0
1
New payment method
8
5
3
16
5
3.2
2
UI refresh
3
2
1
6
3
2.0
3
API v2
7
3
5
15
8
1.9
4
Ưu tiên: Security patch (WSJF cao nhất) → nhỏ, urgent, high risk reduction.
Khi nào dùng RICE vs WSJF
Aspect
RICE
WSJF
Best for
Product features, user-facing
Platform work, mixed priorities
Considers time urgency
Không
Có (Time Criticality)
Considers risk
Gián tiếp qua Confidence
Trực tiếp (Risk Reduction)
Simplicity
Đơn giản hơn
Cần training
Typical use
Product teams
SAFe/Agile at scale
MoSCoW Prioritization
MoSCoW đơn giản, dễ communicate với stakeholders. Đặc biệt hữu ích cho sprint/release planning.
Priority
Định nghĩa
% Effort
Rule
Must have
Không có = release fail
~60%
Non-negotiable
Should have
Quan trọng nhưng workaround tồn tại
~20%
Deliver nếu có capacity
Could have
Nice to have, improve experience
~15%
Cut first khi over capacity
Won't have
Biết cần nhưng không làm lần này
~5% buffer
Backlog cho future
Ví dụ MoSCoW cho Sprint
markdown
## Sprint 15 - E-commerce Checkout### Must Have (MVP - phải ship)- [ ] Process payment via VNPay
- [ ] Send order confirmation email
- [ ] Update inventory after purchase
### Should Have (important, not blocking)- [ ] Save card for future purchases
- [ ] Order tracking page
- [ ] Email receipt with PDF attachment
### Could Have (nice to have)- [ ] Apple Pay / Google Pay
- [ ] Gift wrapping option
- [ ] Estimated delivery date
### Won't Have (this sprint)- [ ] Subscription/recurring payments
- [ ] Multi-currency support
- [ ] Loyalty points integration
Available capacity per sprint:
Team size: 8 engineers
Sprint days: 10
Gross capacity: 80 person-days
Deductions:
Meetings & ceremonies: -10% = -8 days
On-call rotation: -5% = -4 days
Holidays/PTO planned: -5% = -4 days
Bug fixes & support: -15% = -12 days
Net capacity: 52 person-days
Allocation:
Features (new value): 60% = 31 days
Tech debt & improvements: 25% = 13 days
Bugs & maintenance: 15% = 8 days
Budget Proposal Template
markdown
## Engineering Budget Proposal - [Quarter/Year]### Executive Summary
[1-2 câu: tổng budget requested, key investments, expected outcomes]
### Budget Breakdown
| Category | Previous Q | Proposed Q | Change | Justification |
|----------|-----------|-----------|--------|--------------|
| People | $X | $X | +$X | Hire 1 senior dev cho [project] |
| Infrastructure | $X | $X | +$X | Scale for expected 2x traffic |
| Tools | $X | $X | $0 | No change |
| Training | $X | $X | +$X | Team certifications (Azure) |
| Contingency | $X | $X | $0 | Standard 7% buffer |
| **Total** | **$X** | **$X** | **+$X** | |
### Key Investments1.**[Investment 1]:** $X - Expected ROI: [outcome]
2.**[Investment 2]:** $X - Expected ROI: [outcome]
### Risks if Budget Not Approved- [Risk 1: delayed delivery of [project]]
- [Risk 2: increased incident rate without infra upgrade]
### Tracking Plan- Monthly budget review meeting
- Quarterly variance report
- Alert threshold: >10% over budget in any category
Tracking and Reporting Spend
Monthly Report Template
Category
Budget
Actual
Variance
%
Action
Cloud infra
$3,500
$3,800
+$300
+9%
Review auto-scaling config
Licenses
$2,200
$2,200
$0
0%
On track
Contractors
$5,000
$3,000
-$2,000
-40%
Delayed start, carry forward
Training
$1,200
$800
-$400
-33%
Conference postponed
Total
$11,900
$9,800
-$2,100
-18%
Under budget
Cost Optimization Quick Wins
Action
Potential Savings
Effort
Timeline
Reserved Instances (1yr)
30-40% compute
Low
This week
Right-size VMs
10-25%
Low
1-2 days
Auto-shutdown dev/test
50-70% non-prod
Low
1 day
Storage tier optimization
20-60% storage
Medium
1 sprint
Remove unused resources
5-15%
Low
1 day
Spot VMs for batch jobs
60-90% batch
Medium
1-2 sprints
Making the Case for Technical Investment
Framework: Problem → Impact → Solution → Ask
1. Problem (1 paragraph)
"Hệ thống hiện tại có X vấn đề gây ra Y impact"
2. Impact (số liệu cụ thể)
"Mất $Z/tháng vì downtime / slow performance / manual work"
"Team mất N hours/tuần vì tech debt"
3. Proposed Solution
"Invest [amount] trong [timeline] để đạt [outcome]"
4. Expected ROI
"Save [amount]/năm, payback trong [months]"
5. Risk of NOT doing
"Nếu không làm, [consequence] trong [timeframe]"
6. Ask
"[X budget] + [Y headcount] + [Z timeline]"
Ví dụ: Propose Database Upgrade
Problem:
Database response time tăng 300% trong 6 tháng.
3 incidents/tháng do connection pool exhaustion.
Impact:
- Downtime cost: $15K/incident x 3 = $45K/tháng
- Developer time on incidents: 40h/tháng = $4K
- Customer churn risk: 5% users affected
Proposed Solution:
Upgrade SQL Server tier + implement read replicas
+ Redis caching layer
Cost:
- Azure SQL upgrade: +$500/tháng
- Redis Cache: +$300/tháng
- Development: 2 devs x 1 month = $16K
Total Year 1: $25,600
ROI:
- Save $49K/tháng x 12 = $588K/năm
- ROI = ($588K - $25.6K) / $25.6K = 2,196%
- Payback: < 1 tháng
Recommendation: APPROVE - ROI cực cao, risk giảm ngay lập tức