project-management

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Project Management

项目管理

Overview

概述

Software project management methodologies, issue tracking systems, and team collaboration practices.

软件项目管理方法论、问题跟踪系统与团队协作实践。

Agile Methodologies

敏捷方法论

Scrum Framework

Scrum框架

┌─────────────────────────────────────────────────────────────────┐
│                        Scrum Framework                          │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Product      Sprint         Sprint          Sprint             │
│  Backlog   →  Planning   →   Execution   →   Review/Retro      │
│                   │              │                              │
│                   ▼              ▼                              │
│              Sprint         Daily Standup                       │
│              Backlog        (15 min)                           │
│                                                                 │
│  Roles:                                                         │
│  • Product Owner: Backlog priority, stakeholder voice           │
│  • Scrum Master: Process facilitation, impediment removal       │
│  • Development Team: Self-organizing, cross-functional          │
│                                                                 │
│  Artifacts:                                                     │
│  • Product Backlog: Prioritized feature list                    │
│  • Sprint Backlog: Committed sprint work                        │
│  • Increment: Potentially shippable product                     │
│                                                                 │
│  Events:                                                        │
│  • Sprint Planning: What & How for sprint                       │
│  • Daily Standup: Sync & impediments                           │
│  • Sprint Review: Demo to stakeholders                          │
│  • Sprint Retrospective: Process improvement                    │
└─────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│                        Scrum Framework                          │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  Product      Sprint         Sprint          Sprint             │
│  Backlog   →  Planning   →   Execution   →   Review/Retro      │
│                   │              │                              │
│                   ▼              ▼                              │
│              Sprint         Daily Standup                       │
│              Backlog        (15 min)                           │
│                                                                 │
│  Roles:                                                         │
│  • Product Owner: Backlog priority, stakeholder voice           │
│  • Scrum Master: Process facilitation, impediment removal       │
│  • Development Team: Self-organizing, cross-functional          │
│                                                                 │
│  Artifacts:                                                     │
│  • Product Backlog: Prioritized feature list                    │
│  • Sprint Backlog: Committed sprint work                        │
│  • Increment: Potentially shippable product                     │
│                                                                 │
│  Events:                                                        │
│  • Sprint Planning: What & How for sprint                       │
│  • Daily Standup: Sync & impediments                           │
│  • Sprint Review: Demo to stakeholders                          │
│  • Sprint Retrospective: Process improvement                    │
└─────────────────────────────────────────────────────────────────┘

Kanban Board

Kanban看板

┌──────────────┬──────────────┬──────────────┬──────────────┬──────────────┐
│   Backlog    │   To Do      │ In Progress  │   Review     │    Done      │
│              │   (WIP: 5)   │   (WIP: 3)   │   (WIP: 2)   │              │
├──────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │
│ │ Feature  │ │ │ Bug fix  │ │ │ API      │ │ │ Login    │ │ │ Auth     │ │
│ │ Request  │ │ │ #123     │ │ │ endpoint │ │ │ page     │ │ │ module   │ │
│ └──────────┘ │ └──────────┘ │ │ @alice   │ │ │ @bob     │ │ └──────────┘ │
│ ┌──────────┐ │ ┌──────────┐ │ └──────────┘ │ └──────────┘ │ ┌──────────┐ │
│ │ Tech     │ │ │ Refactor │ │ ┌──────────┐ │              │ │ Database │ │
│ │ Debt     │ │ │ auth     │ │ │ Tests    │ │              │ │ migration│ │
│ └──────────┘ │ └──────────┘ │ │ @charlie │ │              │ └──────────┘ │
│              │              │ └──────────┘ │              │              │
└──────────────┴──────────────┴──────────────┴──────────────┴──────────────┘

Key Principles:
• Visualize work
• Limit Work In Progress (WIP)
• Manage flow
• Make policies explicit
• Implement feedback loops
• Improve collaboratively

┌──────────────┬──────────────┬──────────────┬──────────────┬──────────────┐
│   Backlog    │   To Do      │ In Progress  │   Review     │    Done      │
│              │   (WIP: 5)   │   (WIP: 3)   │   (WIP: 2)   │              │
├──────────────┼──────────────┼──────────────┼──────────────┼──────────────┤
│ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │ ┌──────────┐ │
│ │ Feature  │ │ │ Bug fix  │ │ │ API      │ │ │ Login    │ │ │ Auth     │ │
│ │ Request  │ │ │ #123     │ │ │ endpoint │ │ │ page     │ │ │ module   │ │
│ └──────────┘ │ └──────────┘ │ │ @alice   │ │ │ @bob     │ │ └──────────┘ │
│ ┌──────────┐ │ ┌──────────┐ │ └──────────┘ │ └──────────┘ │ ┌──────────┐ │
│ │ Tech     │ │ │ Refactor │ │ ┌──────────┐ │              │ │ Database │ │
│ │ Debt     │ │ │ auth     │ │ │ Tests    │ │              │ │ migration│ │
│ └──────────┘ │ └──────────┘ │ │ @charlie │ │              │ └──────────┘ │
│              │              │ └──────────┘ │              │              │
└──────────────┴──────────────┴──────────────┴──────────────┴──────────────┘

核心原则：
• 可视化工作流程
• 限制在制品数量（WIP）
• 管理工作流转
• 明确工作规则
• 建立反馈循环
• 持续协作改进

User Stories

用户故事

markdown

undefined

markdown

undefined

User Story Format

用户故事格式

As a [type of user] I want [goal/desire] So that [benefit/value]

作为[某类用户] 我希望[达成目标/实现需求] 以便[获得收益/实现价值]

Example

示例

As a registered user I want to reset my password via email So that I can regain access to my account if I forget my password

作为注册用户我希望通过邮箱重置密码以便在忘记密码时重新访问我的账户

Acceptance Criteria (Given-When-Then)

验收准则（Given-When-Then）

Given I am on the login page When I click "Forgot Password" And I enter my registered email And I click "Send Reset Link" Then I should receive an email with a password reset link And the link should expire after 24 hours

假设我在登录页面当我点击"忘记密码" 并且输入我的注册邮箱然后点击"发送重置链接" 那么我应该收到包含密码重置链接的邮件并且该链接应在24小时后过期

INVEST Criteria

INVEST准则

□ Independent - Can be developed separately □ Negotiable - Details can be discussed □ Valuable - Delivers user/business value □ Estimable - Can be sized □ Small - Fits in a sprint □ Testable - Has clear acceptance criteria

undefined

□ 独立性 - 可独立开发 □ 协商性 - 细节可讨论 □ 价值性 - 为用户/业务带来价值 □ 可估算性 - 可评估工作量 □ 小型化 - 可在一个Sprint内完成 □ 可测试性 - 具备明确的验收准则

undefined

Story Points & Estimation

故事点与估算

markdown

undefined

markdown

undefined

Fibonacci Scale

斐波那契估算尺度

1 - Trivial (< 1 hour) 2 - Simple (few hours) 3 - Straightforward (half day) 5 - Medium complexity (1-2 days) 8 - Complex (3-5 days) 13 - Very complex (1+ week) 21 - Epic (break it down!)

1 - 极简单（< 1小时） 2 - 简单（数小时） 3 - 直观（半天） 5 - 中等复杂度（1-2天） 8 - 复杂（3-5天） 13 - 非常复杂（1周以上） 21 - 史诗级任务（需要拆分！）

Planning Poker

规划扑克

Product Owner presents story
Team discusses & asks questions
Each member secretly selects estimate
All reveal simultaneously
Discuss outliers
Re-vote if needed
Reach consensus

产品负责人介绍用户故事
团队讨论并提出疑问
每位成员秘密选择估算值
所有人同时亮出估算结果
讨论差异较大的估算值
如有需要重新投票
达成共识

Velocity Calculation

速度计算

Sprint 1: 32 points completed Sprint 2: 28 points completed Sprint 3: 35 points completed Average Velocity: 31.7 points/sprint

---

Sprint 1：完成32个故事点 Sprint 2：完成28个故事点 Sprint 3：完成35个故事点平均速度：31.7个故事点/Sprint

---

Issue Tracking

问题跟踪

GitHub Issues

markdown

undefined

markdown

undefined

Issue Template: Bug Report

问题模板：Bug报告

name: Bug Report about: Report a bug to help us improve labels: bug, needs-triage

name: Bug Report about: 提交Bug报告以帮助我们改进产品 labels: bug, needs-triage

Description

问题描述

A clear description of the bug.

清晰描述Bug内容。

Steps to Reproduce

复现步骤

Go to '...'
Click on '...'
Scroll down to '...'
See error

前往"..."
点击"..."
滚动到"..."
查看错误

Expected Behavior

预期行为

What should happen.

应该发生的情况。

Actual Behavior

实际行为

What actually happens.

实际发生的情况。

Environment

环境信息

OS: [e.g., macOS 14.0]
Browser: [e.g., Chrome 120]
Version: [e.g., 2.1.0]

操作系统：[例如：macOS 14.0]
浏览器：[例如：Chrome 120]
版本：[例如：2.1.0]

Screenshots

截图

If applicable, add screenshots.

如有需要，添加截图。

Additional Context

补充说明

Any other relevant information.


```markdown

其他相关信息。


```markdown

Issue Template: Feature Request

问题模板：功能请求

name: Feature Request about: Suggest a new feature labels: enhancement

name: Feature Request about: 建议新功能 labels: enhancement

Problem Statement

问题陈述

What problem does this solve?

该功能解决了什么问题？

Proposed Solution

提议的解决方案

How should this work?

该功能应如何工作？

Alternatives Considered

考虑过的替代方案

Other approaches you've thought about.

你想到的其他实现方式。

Additional Context

补充说明

Mockups, examples, or references.

undefined

原型图、示例或参考资料。

undefined

GitHub Projects (v2)

yaml

undefined

yaml

undefined

Project configuration

fields:

name: Status type: single_select options:
- Backlog
- Ready
- In Progress
- In Review
- Done
name: Priority type: single_select options:
- 🔴 High
- 🟡 Medium
- 🟢 Low
name: Sprint type: iteration duration: 2 weeks
name: Estimate type: number
name: Team type: single_select options:
- Frontend
- Backend
- DevOps

views:

name: Kanban Board type: board group_by: Status
name: Sprint Backlog type: table filter: Sprint = @current sort: Priority
name: Roadmap type: roadmap date_field: Target Date

undefined

fields:

name: Status type: single_select options:
- Backlog
- Ready
- In Progress
- In Review
- Done
name: Priority type: single_select options:
- 🔴 High
- 🟡 Medium
- 🟢 Low
name: Sprint type: iteration duration: 2 weeks
name: Estimate type: number
name: Team type: single_select options:
- Frontend
- Backend
- DevOps

views:

name: Kanban Board type: board group_by: Status
name: Sprint Backlog type: table filter: Sprint = @current sort: Priority
name: Roadmap type: roadmap date_field: Target Date

undefined

Linear Workflow

Linear 工作流

yaml

undefined

yaml

undefined

Linear project structure

teams:

name: Engineering key: ENG workflows:
- Backlog → Todo → In Progress → In Review → Done

cycles:

duration: 2 weeks
auto_archive: true

labels:

bug
feature
improvement
tech-debt

priorities:

Urgent
High
Medium
Low
No Priority

teams:

name: Engineering key: ENG workflows:
- Backlog → Todo → In Progress → In Review → Done

cycles:

duration: 2 weeks
auto_archive: true

labels:

bug
feature
improvement
tech-debt

priorities:

Urgent
High
Medium
Low
No Priority

Linear CLI usage

linear issue create --title "Add OAuth support" --team ENG --priority high linear issue list --team ENG --state "In Progress" linear cycle current

---

linear issue create --title "Add OAuth support" --team ENG --priority high linear issue list --team ENG --state "In Progress" linear cycle current

---

Sprint Planning

Sprint规划

Sprint Planning Meeting

Sprint规划会议

markdown

undefined

markdown

undefined

Sprint Planning Agenda (2-4 hours)

Sprint规划会议议程（2-4小时）

Part 1: What (1-2 hours)

第一部分：做什么（1-2小时）

Review sprint goal
Product Owner presents prioritized backlog
Team asks clarifying questions
Select stories for sprint commitment

回顾Sprint目标
产品负责人展示优先级排序的待办事项
团队提出澄清问题
选择要承诺的Sprint故事

Part 2: How (1-2 hours)

第二部分：怎么做（1-2小时）

Break stories into tasks
Identify dependencies
Assign initial owners
Validate capacity vs commitment

将用户故事拆分为任务
识别依赖关系
初步分配负责人
验证团队容量与承诺的工作量是否匹配

Sprint Goal Template

Sprint目标模板

"By the end of this sprint, users will be able to [specific capability], enabling [business value]."

"在本次Sprint结束时，用户将能够[具体能力]，从而实现[业务价值]。"

Capacity Planning

容量规划

Team Size: 5 developers Sprint Length: 2 weeks (10 working days) Meetings/Ceremonies: 1 day equivalent PTO/Holidays: 2 days Buffer (bugs, support): 10%

Available Capacity: (5 × 10 - 5 - 2) × 0.9 = 38.7 person-days Historical Velocity: ~35 story points

undefined

团队规模：5名开发人员 Sprint时长：2周（10个工作日）会议/仪式：相当于1天的时间休假/节假日：2天缓冲时间（Bug修复、支持工作）：10%

可用容量：(5 × 10 - 5 - 2) × 0.9 = 38.7人天历史速度：约35个故事点

undefined

Definition of Done

完成定义（DoD）

markdown

undefined

markdown

undefined

Definition of Done (DoD)

完成定义（DoD）

Code Complete

代码完成

Review Complete

评审完成

Code review approved by 2+ team members
No blocking comments unresolved
Security considerations reviewed

代码通过2名以上团队成员评审并批准
无未解决的阻塞性评论
已考虑安全因素

Testing Complete

测试完成

Documentation Complete

文档完成

Deployment Ready

部署就绪

Feature flag configured (if needed)
Database migrations tested
Monitoring/alerts configured
Merged to main branch

---

已配置功能开关（如需要）
数据库迁移已测试
已配置监控/告警
代码已合并到主分支

---

Retrospectives

回顾会议

Retrospective Formats

回顾会议格式

markdown

undefined

markdown

undefined

Mad/Sad/Glad

愤怒/难过/开心

┌─────────────────┬─────────────────┬─────────────────┐ │ Mad 😠 │ Sad 😢 │ Glad 😊 │ ├─────────────────┼─────────────────┼─────────────────┤ │ Constant scope │ Missed sprint │ Great team │ │ changes │ goal │ collaboration │ │ │ │ │ │ Unclear │ Technical debt │ Shipped major │ │ requirements │ growing │ feature │ └─────────────────┴─────────────────┴─────────────────┘

┌─────────────────┬─────────────────┬─────────────────┐ │ 愤怒 😠 │ 难过 😢 │ 开心 😊 │ ├─────────────────┼─────────────────┼─────────────────┤ │ 需求范围频繁变更 │ 未达成Sprint目标 │ 团队协作顺畅 │ │ │ │ │ │ 需求不明确 │ 技术债务累积 │ 发布了核心功能 │ └─────────────────┴─────────────────┴─────────────────┘

Start/Stop/Continue

开始/停止/保持

┌─────────────────┬─────────────────┬─────────────────┐ │ Start 🟢 │ Stop 🔴 │ Continue 🔵 │ ├─────────────────┼─────────────────┼─────────────────┤ │ Pair programming│ Long meetings │ Daily standups │ │ │ │ │ │ Sprint demos │ Scope creep │ Code reviews │ │ │ │ │ │ Documentation │ Last-minute │ Knowledge │ │ │ changes │ sharing │ └─────────────────┴─────────────────┴─────────────────┘

┌─────────────────┬─────────────────┬─────────────────┐ │ 开始 🟢 │ 停止 🔴 │ 保持 🔵 │ ├─────────────────┼─────────────────┼─────────────────┤ │ 结对编程 │ 冗长的会议 │ 每日站会 │ │ │ │ │ │ Sprint演示 │ 需求蔓延 │ 代码评审 │ │ │ │ │ │ 文档完善 │ 临时变更需求 │ 知识分享 │ └─────────────────┴─────────────────┴─────────────────┘

4 Ls: Liked, Learned, Lacked, Longed For

4L：喜欢、学到、缺少、渴望

Sailboat: Wind (helps), Anchors (slows), Rocks (risks)

帆船模型：风力（助力）、锚点（阻碍）、礁石（风险）

undefined

undefined

Action Items Template

行动项模板

markdown

undefined

markdown

undefined

Sprint 23 Retrospective Action Items

Sprint 23回顾会议行动项

Action	Owner	Due	Status
Set up automated E2E tests	@alice	Sprint 24	🟡 In Progress
Document API endpoints	@bob	Sprint 24	⬜ Not Started
Schedule architecture review	@carol	Next week	✅ Done

行动项	负责人	截止时间	状态
搭建自动化E2E测试	@alice	Sprint 24	🟡 进行中
编写API接口文档	@bob	Sprint 24	⬜ 未开始
安排架构评审会议	@carol	下周	✅ 已完成

Metrics to Track

跟踪指标

Sprint burndown consistency
Bug escape rate
Deployment frequency
Lead time for changes

---

Sprint燃尽图一致性
Bug逃逸率
部署频率
变更前置时间

---

Metrics & Reporting

指标与报告

Key Metrics

核心指标

markdown

undefined

markdown

undefined

DORA Metrics

DORA指标

Deployment Frequency: How often code deploys to production
Lead Time for Changes: Commit to production time
Change Failure Rate: % of deployments causing failures
Time to Restore: How long to recover from failures

部署频率：代码部署到生产环境的频率
变更前置时间：从代码提交到部署到生产环境的时间
变更失败率：导致故障的部署占比
恢复时间：从故障恢复的时长

Sprint Metrics

Sprint指标

Velocity: Story points completed per sprint
Sprint Burndown: Work remaining over time
Escaped Defects: Bugs found after release
Planned vs Delivered: Commitment accuracy

速度：每个Sprint完成的故事点数
Sprint燃尽图：剩余工作量随时间的变化
逃逸缺陷：发布后发现的Bug数量
计划交付率：承诺工作量与实际完成量的匹配度

Team Health

团队健康度

Team satisfaction surveys
Turnover rate
Knowledge sharing sessions
Technical debt ratio

---

团队满意度调查
人员流动率
知识分享会议次数
技术债务比率

---