Sprint Planning & Refinement
DeliverySprint planning và refinement thực tế: Definition of Ready, story splitting, capacity, sprint goal, risk, dependencies và QA readiness.
Đăng nhập để đánh dấu kỹ năng và theo dõi tiến độ.
Roadmap — Cách học và đạt kỹ năng
Sprint Planning & Refinement là gì?
Refinement làm rõ work trước sprint: split, AC, risk, dependency, estimate. Sprint planning chọn sprint goal và cam kết thực tế dựa trên capacity. Nếu planning dùng để khám phá requirement từ đầu, sprint sẽ bắt đầu bằng confusion.
Definition of Ready template
| Check | Good standard | Example |
|---|---|---|
| Goal | User/business outcome clear. | Reduce failed invite support tickets. |
| AC | Happy path, edge cases and data rules. | Invalid email, duplicate invite, permission denied. |
| Design/data | Mockups, API/data sources, analytics noted. | Invite status from events table. |
| Dependencies | External blockers identified. | Email provider webhook needed. |
| Estimate confidence | Team understands enough to size. | Spike done; story split under 3 days. |
Refinement agenda 60 phút
| Time | Activity | Output |
|---|---|---|
| 0-10 | Review goal and evidence | Shared context. |
| 10-25 | Walk through user flow and AC | Behavior clarified. |
| 25-40 | Identify risks, dependencies, unknowns | Open questions with owners. |
| 40-50 | Split stories | Small deliverable slices. |
| 50-60 | Estimate and DoR check | Ready/Not Ready decision. |
Case study: checkout payment sprint
Bad planning: “Implement payment gateway” in one sprint. Better refinement: split into create payment request, handle success callback, pending state polling, failure handling, duplicate callback audit.
- Sprint goal: allow customers to complete payment safely without double charge.
- Tradeoff: release MoMo first, defer saved cards.
- Risk: callback timeout; spike before commitment.
Pitfalls
- Planning by filling capacity instead of choosing a sprint goal.
- Accepting stories without AC or owner for open questions.
- Overcommitting because holidays, support work and incidents are ignored.
- Splitting by frontend/backend only, leaving no user-visible value.
Definition of done
- Sprint has one clear goal.
- Committed items meet Definition of Ready.
- Risks and dependencies are explicit.
- Tradeoffs are understood by PM, Engineering and QA.
Thảo luận & tài liệu thêm 0
Chia sẻ kinh nghiệm, đặt câu hỏi, hoặc đính kèm tài liệu/YouTube giúp người khác học kỹ năng này.