Back to Details

decomposing-tasks

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Decomposing Tasks

任务拆解

Workflows

工作流程

  • Understand Scope: What is the full scope of work?
  • Identify Components: What are the major pieces?
  • Break Down: Split into 1-2 day tasks
  • Order: Define dependencies and sequence
  • Validate: Can each task be demo'd/tested?
  • 明确范围：工作的完整范围是什么？
  • 识别核心组件：主要组成部分有哪些？
  • 拆解任务：拆分为1-2天可完成的任务
  • 排序规划：定义依赖关系与执行顺序
  • 验证确认：每个任务是否可进行演示/测试？

Task Size Guidelines

任务规模指南

Too Big

过大的任务

  • "Build the authentication system"
  • Cannot be completed in 1-2 days
  • Cannot be tested independently
  • "构建认证系统"
  • 无法在1-2天内完成
  • 无法独立测试

Just Right

规模适中的任务

  • "Create login API endpoint"
  • "Add password validation"
  • "Implement JWT token generation"
  • "创建登录API endpoint"
  • "添加密码验证"
  • "实现JWT token生成"

Too Small

过小的任务

  • "Add semicolon"
  • "Rename variable"
  • Not worth tracking separately
  • "添加分号"
  • "重命名变量"
  • 单独跟踪无价值

Decomposition Strategies

任务拆解策略

Vertical Slicing

纵向拆分

Cut through all layers for one feature.
Feature: User Login
├── API endpoint (POST /login)
├── Input validation
├── Database query
├── JWT generation
├── Error handling
└── Integration test
为单个功能贯穿所有层级实现。
Feature: User Login
├── API endpoint (POST /login)
├── Input validation
├── Database query
├── JWT generation
├── Error handling
└── Integration test

Horizontal Slicing

横向拆分

Complete one layer at a time.
Database Layer
├── Users table
├── Sessions table
└── Indexes

API Layer
├── Login endpoint
├── Logout endpoint
└── Refresh endpoint
逐层完成所有相关内容。
Database Layer
├── Users table
├── Sessions table
└── Indexes

API Layer
├── Login endpoint
├── Logout endpoint
└── Refresh endpoint

SPIDR Method

SPIDR Method

  • Spike: Research/investigation task
  • Path: Main flow implementation
  • Interface: API/UI contract
  • Data: Storage and schemas
  • Rules: Business logic and validation
  • Spike：调研/调查任务
  • Path：主流程实现
  • Interface：API/UI契约
  • Data：存储与数据模型
  • Rules：业务逻辑与验证规则

Task Template

任务模板

markdown
undefined
markdown
undefined

Task: [Title]

Task: [Title]

Description: [What needs to be done]
Acceptance Criteria:
  • [Criterion 1]
  • [Criterion 2]
Dependencies: [What must be done first]
Estimate: [X hours/points]
undefined
Description: [What needs to be done]
Acceptance Criteria:
  • [Criterion 1]
  • [Criterion 2]
Dependencies: [What must be done first]
Estimate: [X hours/points]
undefined

Definition of Done

完成标准

Every task should have:
  • Code complete and reviewed
  • Tests written and passing
  • Documentation updated
  • Deployed to staging
每个任务需满足以下条件：
  • 代码完成并通过评审
  • 编写测试并全部通过
  • 相关文档已更新
  • 部署至Staging环境