Back to Details

task-planning

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Task Planning

任务规划

When to use this skill

何时使用此技能

  • 피처 개발: 새 기능을 작은 태스크로 분할
  • Sprint Planning: 스프린트에 포함할 작업 선정
  • Backlog Grooming: 백로그 정리 및 우선순위 설정
  • 功能开发：将新功能拆分为小型任务
  • Sprint规划：选择纳入迭代的工作
  • 待办事项梳理：待办事项整理与优先级设定

Instructions

操作指南

Step 1: User Story 작성 (INVEST)

步骤1：编写User Story（遵循INVEST原则）

INVEST 원칙:
  • Independent: 독립적
  • Negotiable: 협상 가능
  • Valuable: 가치 있음
  • Estimable: 추정 가능
  • Small: 작음
  • Testable: 테스트 가능
템플릿:
markdown
undefined
INVEST原则:
  • Independent: 独立的
  • Negotiable: 可协商的
  • Valuable: 有价值的
  • Estimable: 可估算的
  • Small: 体量小的
  • Testable: 可测试的
模板:
markdown
undefined

User Story: [제목]

User Story: [标题]

As a [사용자 유형] I want [기능] So that [가치/이유]
As a [用户类型] I want [功能] So that [价值/理由]

Acceptance Criteria

验收标准

  • Given [상황] When [행동] Then [결과]
  • Given [상황] When [행동] Then [결과]
  • Given [상황] When [행동] Then [결과]
  • Given [场景] When [操作] Then [结果]
  • Given [场景] When [操作] Then [结果]
  • Given [场景] When [操作] Then [结果]

Technical Notes

技术说明

  • API endpoint: POST /api/users
  • Database: users 테이블
  • Frontend: React component
  • API endpoint: POST /api/users
  • Database: users 表
  • Frontend: React component

Estimation

估算

  • Story Points: 5
  • T-Shirt: M
  • Story Points: 5
  • T-Shirt: M

Dependencies

依赖项

  • User authentication must be completed first
  • 需先完成用户认证

Priority

优先级

  • MoSCoW: Must Have
  • Business Value: High

**예시**:
```markdown
  • MoSCoW: Must Have
  • 业务价值: 高

**示例**:
```markdown

User Story: User Registration

User Story: 用户注册

As a new visitor I want to create an account So that I can access personalized features
As a 新访客 I want 创建账户 So that 我可以访问个性化功能

Acceptance Criteria

验收标准

  • Given valid email and password When user submits form Then account is created
  • Given duplicate email When user submits Then error message is shown
  • Given weak password When user submits Then validation error is shown
  • Given successful registration When account created Then welcome email is sent
  • Given 有效的邮箱和密码 When 用户提交表单 Then 账户创建成功
  • Given 重复的邮箱 When 用户提交 Then 显示错误提示
  • Given 弱密码 When 用户提交 Then 显示验证错误
  • Given 注册成功 When 账户创建完成 Then 发送欢迎邮件

Technical Notes

技术说明

  • Hash password with bcrypt
  • Validate email format
  • Send welcome email via SendGrid
  • Store user in PostgreSQL
  • 使用bcrypt对密码进行哈希加密
  • 验证邮箱格式
  • 通过SendGrid发送欢迎邮件
  • 将用户数据存储到PostgreSQL

Estimation

估算

  • Story Points: 5
  • Story Points: 5

Dependencies

依赖项

  • Email service integration (#123)
  • 邮件服务集成（#123）

Priority

优先级

  • MoSCoW: Must Have
undefined
  • MoSCoW: Must Have
undefined

Step 2: Epic → Story → Task 분해

步骤2：Epic → Story → Task 拆分

markdown
undefined
markdown
undefined

Epic: User Management System

Epic: 用户管理系统

Story 1: User Registration

Story 1: 用户注册

  • Points: 5
  • Tasks:
    • Design registration form UI (2h)
    • Create POST /api/users endpoint (3h)
    • Implement email validation (1h)
    • Add password strength checker (2h)
    • Write unit tests (2h)
    • Integration testing (2h)
  • Points: 5
  • Tasks:
    • 设计注册表单UI（2小时）
    • 创建POST /api/users接口（3小时）
    • 实现邮箱验证（1小时）
    • 添加密码强度检查器（2小时）
    • 编写单元测试（2小时）
    • 集成测试（2小时）

Story 2: User Login

Story 2: 用户登录

  • Points: 3
  • Tasks:
    • Design login form (2h)
    • Create POST /api/auth/login endpoint (2h)
    • Implement JWT token generation (2h)
    • Add "Remember Me" functionality (1h)
    • Write tests (2h)
  • Points: 3
  • Tasks:
    • 设计登录表单（2小时）
    • 创建POST /api/auth/login接口（2小时）
    • 实现JWT令牌生成（2小时）
    • 添加"记住我"功能（1小时）
    • 编写测试（2小时）

Story 3: Password Reset

Story 3: 密码重置

  • Points: 5
  • Tasks:
    • "Forgot Password" UI (2h)
    • Generate reset token (2h)
    • Send reset email (1h)
    • Reset password form (2h)
    • Update password API (2h)
    • Tests (2h)
undefined
  • Points: 5
  • Tasks:
    • "忘记密码"UI（2小时）
    • 生成重置令牌（2小时）
    • 发送重置邮件（1小时）
    • 重置密码表单（2小时）
    • 更新密码API（2小时）
    • 测试（2小时）
undefined

Step 3: MoSCoW 우선순위

步骤3：MoSCoW 优先级划分

markdown
undefined
markdown
undefined

Feature Prioritization (MoSCoW)

功能优先级划分（MoSCoW）

Must Have (Sprint 1)

Must Have（迭代1）

  • User Registration
  • User Login
  • Basic Profile Page
  • 用户注册
  • 用户登录
  • 基础个人资料页面

Should Have (Sprint 2)

Should Have（迭代2）

  • Password Reset
  • Email Verification
  • Profile Picture Upload
  • 密码重置
  • 邮箱验证
  • 头像上传

Could Have (Sprint 3)

Could Have（迭代3）

  • Two-Factor Authentication
  • Social Login (Google, GitHub)
  • Account Deletion
  • 双因素认证
  • 社交登录（Google、GitHub）
  • 账户删除

Won't Have (This Release)

Won't Have（当前版本不包含）

  • Biometric Authentication
  • Multiple Sessions Management
undefined
  • 生物识别认证
  • 多会话管理
undefined

Step 4: Sprint Planning

步骤4：Sprint规划

markdown
undefined
markdown
undefined

Sprint 10 Planning

迭代10规划

Sprint Goal: Complete user authentication system
Duration: 2 weeks Team Capacity: 40 hours × 4 people = 160 hours Estimated Velocity: 30 story points
Sprint目标: 完成用户认证系统
时长: 2周 团队产能: 40小时 × 4人 = 160小时 预估速度: 30 story points

Selected Stories

选中的Story

  1. User Registration (5 points) - Must Have
  2. User Login (3 points) - Must Have
  3. Password Reset (5 points) - Must Have
  4. Email Verification (3 points) - Should Have
  5. Profile Edit (5 points) - Should Have
  6. JWT Refresh Token (3 points) - Should Have
  7. Rate Limiting (2 points) - Should Have
  8. Security Audit (4 points) - Must Have
Total: 30 points
  1. 用户注册（5 points）- Must Have
  2. 用户登录（3 points）- Must Have
  3. 密码重置（5 points）- Must Have
  4. 邮箱验证（3 points）- Should Have
  5. 个人资料编辑（5 points）- Should Have
  6. JWT刷新令牌（3 points）- Should Have
  7. 请求频率限制（2 points）- Should Have
  8. 安全审计（4 points）- Must Have
总计: 30 points

Sprint Backlog

Sprint待办事项

  • User Registration (#101)
  • User Login (#102)
  • Password Reset (#103)
  • Email Verification (#104)
  • Profile Edit (#105)
  • JWT Refresh Token (#106)
  • Rate Limiting (#107)
  • Security Audit (#108)
  • 用户注册（#101）
  • 用户登录（#102）
  • 密码重置（#103）
  • 邮箱验证（#104）
  • 个人资料编辑（#105）
  • JWT刷新令牌（#106）
  • 请求频率限制（#107）
  • 安全审计（#108）

Definition of Done

完成定义（Definition of Done）

  • Code written and reviewed
  • Unit tests passing (80%+ coverage)
  • Integration tests passing
  • Documentation updated
  • Deployed to staging
  • QA approved
undefined
  • 代码编写并通过评审
  • 单元测试通过（覆盖率80%以上）
  • 集成测试通过
  • 文档已更新
  • 部署到预发布环境
  • QA审核通过
undefined

Output format

输出格式

태스크 보드 구조

任务看板结构

Backlog → To Do → In Progress → Review → Done

Backlog:
- 우선순위별 정렬
- Grooming 완료된 스토리

To Do:
- Sprint에 선택된 작업
- 담당자 할당됨

In Progress:
- WIP Limit: 2 per person
- 진행 중인 작업

Review:
- Code review 대기
- QA 테스트 중

Done:
- DoD 충족
- 배포 완료
Backlog → To Do → In Progress → Review → Done

Backlog:
- 按优先级排序
- 已完成梳理的Story

To Do:
- 选中纳入Sprint的工作
- 已分配负责人

In Progress:
- WIP限制：每人最多2项
- 正在进行的工作

Review:
- 等待代码评审
- 正在进行QA测试

Done:
- 符合完成定义
- 已完成部署

Constraints

约束条件

필수 규칙 (MUST)

必须遵循的规则（MUST）

  1. 명확한 AC: Acceptance Criteria 필수
  2. 추정 완료: 모든 스토리에 포인트 할당
  3. 의존성 파악: 선행 작업 명시
  1. 明确的验收标准：必须制定Acceptance Criteria
  2. 完成估算：所有Story都需分配Story Points
  3. 识别依赖项：明确标注前置工作

금지 사항 (MUST NOT)

禁止事项（MUST NOT）

  1. 너무 큰 스토리: 13+ points는 분할
  2. 모호한 요구사항: "개선한다", "최적화한다" 금지
  1. Story体量过大：超过13 points的Story必须拆分
  2. 模糊的需求描述：禁止使用“优化”“改进”等模糊表述

Best practices

最佳实践

  1. INVEST 원칙: 좋은 사용자 스토리 작성
  2. Definition of Ready: 스프린트 시작 전 준비 완료
  3. Definition of Done: 명확한 완료 기준
  1. 遵循INVEST原则：编写高质量的用户故事
  2. 就绪定义（Definition of Ready）：Sprint开始前确保所有工作准备就绪
  3. 完成定义（Definition of Done）：制定明确的完成标准

References

参考资料

Metadata

元数据

버전

版本

  • 현재 버전: 1.0.0
  • 최종 업데이트: 2025-01-01
  • 호환 플랫폼: Claude, ChatGPT, Gemini
  • 当前版本: 1.0.0
  • 最后更新: 2025-01-01
  • 兼容平台: Claude, ChatGPT, Gemini

태그

标签

#task-planning
#user-stories
#backlog
#sprint-planning
#agile
#project-management
#task-planning
#user-stories
#backlog
#sprint-planning
#agile
#project-management

Examples

示例

Example 1: Basic usage

Example 1: 基础用法

<!-- Add example content here -->
<!-- 添加示例内容 -->

Example 2: Advanced usage

Example 2: 进阶用法

<!-- Add advanced example content here -->
<!-- 添加进阶示例内容 -->