Task Scheduling and Claiming
Before formal coding, confirm "who will do it" and "when it will be completed."
Core Process
任务拆解完成 → 工时评估 → 任务认领 → 确定迭代目标
1. Effort Estimation
Estimation Methods
| Method |
Applicable Scenario |
| Experience-based estimation |
Tasks with similar experience |
| Three-point estimation |
Tasks with high uncertainty |
| Delphi method |
Complex tasks involving multi-person collaboration |
Three-point estimation formula
期望时间 = (乐观 + 4×最可能 + 悲观) / 6
Output Template
| Task ID |
Task Name |
Estimated Effort (person-days) |
Complexity |
Risk Points |
| T-001 |
Frontend popup development |
2 |
Medium |
Third-party component compatibility |
2. Task Claiming
Claiming Principles
- Skill matching: prioritize assigning to members with relevant experience
- Load balancing: avoid assigning too many tasks to one person
- Tech stack relevance: frontend tasks → frontend engineers, backend tasks → backend engineers
Claiming Record Template
| 任务ID | 任务名称 | 认领人 | 计划开始 | 计划完成 | 状态 |
|--------|----------|--------|----------|----------|------|
| T-001 | xxx开发 | 张三 | D+1 | D+3 | 待开始 |
3. Determine Iteration Goals
Sprint Planning Output
## Sprint N (YYYY-MM-DD ~ YYYY-MM-DD)
### 迭代目标
[一句话描述本次冲刺的核心目标]
### 承诺任务
| 任务ID | 任务名称 | 负责人 | 预估工时 |
|--------|----------|--------|----------|
| T-001 | xxx | 张三 | 2人天 |
### 阻塞风险
- [风险点1及应对方案]
Usage Scenarios
- After requirement decomposition is completed, it is necessary to enter the development planning phase
- Iteration kickoff meeting (Sprint Planning)
- Task assignment and scheduling among team members
Key Deliverables
- Task Effort Estimation Sheet
- Task Claiming Checklist
- Sprint Goals and Commitments
