technical-program-manager

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Technical Program Manager

技术项目经理（Technical Program Manager）

When to Use

适用场景

Coordinate a multi-team technical initiative with shared milestones
Map dependencies, critical path, and integration points
Maintain RAID log (risks, actions, issues, decisions)
Run launch readiness or go/no-go reviews
Produce weekly program status for leadership or steering committee
Resolve cross-team blockers without owning the technical design

协调具有共享里程碑的多团队技术计划
梳理依赖关系、关键路径和集成点
维护RAID日志（风险、行动、问题、决策）
开展发布就绪检查或上线/不上线评审
为领导层或指导委员会生成每周项目状态报告
在不负责技术设计的前提下解决跨团队障碍

When NOT to Use

不适用场景

Write BRDs, user stories, or process maps →
```
business-analyst
```
Choose canary vs blue-green or write cutover runbooks →
```
deployment-strategist
```
Implement pipelines, GitOps, or on-call →
```
devops
```
Own data platform roadmap or data governance →
```
data-manager
```

Author service RFCs or code →

senior-software-engineer

fullstack-software-engineer

Platform product roadmap for IDP →
```
platform-engineer
```
Architecture decisions, ADRs, design review →
```
senior-system-architecture
```
Strategy, business case, operating model →
```
business-consultant
```
Technical discovery, solution architecture, RFP response authoring →
```
solutions-architect
```

撰写BRD、用户故事或流程地图 →
```
business-analyst
```
选择金丝雀部署或蓝绿部署方案，或编写切换运行手册 →
```
deployment-strategist
```
实施流水线、GitOps或值班机制 →
```
devops
```
负责数据平台路线图或数据治理 →
```
data-manager
```

撰写服务RFC或代码开发 →

senior-software-engineer

、

fullstack-software-engineer

IDP平台产品路线图规划 →
```
platform-engineer
```
架构决策、ADR编写、设计评审 →
```
senior-system-architecture
```
战略规划、业务案例、运营模型设计 →
```
business-consultant
```
技术调研、解决方案架构设计、RFP响应撰写 →
```
solutions-architect
```

Related skills

相关技能

Need	Skill
Release strategy and rollback design	`deployment-strategist`
Pipeline and environment operations	`devops`
Requirements and business cases	`business-analyst`
UX scope and design handoff	`product-designer`
Engineering design and RFCs	`senior-software-engineer`
Data program roadmaps	`data-manager`
Security/compliance program gates	`compliance-engineer` , `cybersecurity`
System architecture and ADRs	`senior-system-architecture`
Strategy and business case	`business-consultant`
Incident ops: SEV, on-call, postmortems	`incident-management-engineer`
Board resolutions, entity, corporate closing	`corporate-counsel`
Launch and stakeholder messaging	`communication-lead`
Developer training program rollout	`developer-education-lead`
Exec/VIP and community customer escalations	`community-executive-escalations-program-manager`
Data center design and facility execution	`data-center-design-execution-lead`
Multi-site DC portfolio planning and steering	`data-center-portfolio-planning-execution-lead`
M&A diligence, signing, closing coordination	`transaction-manager`
Coordinated vulnerability disclosure program	`technical-program-manager-security-cvd`
Customer solution design and delivery handoff package	`solutions-architect`

需求	对应技能
发布策略与回滚设计	`deployment-strategist`
流水线与环境运维	`devops`
需求梳理与业务案例编写	`business-analyst`
UX范围界定与设计交付	`product-designer`
工程设计与RFC撰写	`senior-software-engineer`
数据项目路线图规划	`data-manager`
安全/合规项目管控	`compliance-engineer` 、 `cybersecurity`
系统架构与ADR制定	`senior-system-architecture`
战略规划与业务案例设计	`business-consultant`
事件运维：严重事件、值班、事后复盘	`incident-management-engineer`
董事会决议、实体事务、公司收尾	`corporate-counsel`
发布与相关方消息传递	`communication-lead`
开发者培训计划推广	`developer-education-lead`
高管/VIP及社区客户升级处理	`community-executive-escalations-program-manager`
数据中心设计与设施执行	`data-center-design-execution-lead`
多站点数据中心组合规划与管控	`data-center-portfolio-planning-execution-lead`
并购尽职调查、签署、收尾协调	`transaction-manager`
协调漏洞披露项目	`technical-program-manager-security-cvd`
客户解决方案设计与交付包移交	`solutions-architect`

Core Workflows

核心工作流

1. Program charter

1. 项目章程

Define before execution:

Objective and measurable outcomes (not output lists)
Scope: teams, systems, in/out
Timeline: phases, hard dates, external dependencies
Roles: DRI per workstream, escalation path
Success metrics and definition of done

See
references/program_charter.md
for charter template.

在执行前定义以下内容：

目标与可衡量成果（而非输出列表）
范围：涉及团队、系统、包含/排除项
时间线：阶段、硬性日期、外部依赖
角色：每个工作流的DRI、升级路径
成功指标与完成定义

项目章程模板请参考
references/program_charter.md
。

2. Work breakdown and dependencies

2. 工作分解与依赖关系梳理

Decompose into workstreams (each with one DRI)
List deliverables per workstream with dates
Build dependency graph (finish-to-start; flag circular deps)
Identify critical path and buffer on that path only
Mark integration milestones (API freeze, env parity, dress rehearsal)

See
references/dependency_risk.md
for dependency types and RAID format.

将项目分解为多个工作流（每个工作流对应一名DRI）
列出每个工作流的交付物及日期
构建依赖关系图（完成到启动模式；标记循环依赖）
识别关键路径并仅在该路径上设置缓冲时间
标记集成里程碑（API冻结、环境一致性、模拟演练）

依赖类型与RAID格式请参考
references/dependency_risk.md
。

3. Operating rhythm

3. 运营节奏

Cadence	Audience	Purpose
Weekly	Workstream DRIs	Blockers, date slips, dependency asks
Biweekly	Sponsors / leads	Scope, risk, decision needs
Pre-launch	Launch council	Readiness checklist

One source of truth for status (doc or tracker—not duplicate spreadsheets)
Decisions logged with owner and date; no re-litigating closed calls

See
references/status_reporting.md
for status template.

频次	受众	目的
每周	工作流DRI	障碍排查、日期延误、依赖请求
每两周	项目发起人/负责人	范围调整、风险评估、决策需求
发布前	发布委员会	就绪检查清单

状态信息单一可信来源（文档或跟踪工具——避免重复使用电子表格）
决策需记录负责人与日期；已关闭的决策不再重新讨论

状态报告模板请参考
references/status_reporting.md
。

4. Risk and issue management

4. 风险与问题管理

Risk: may happen → mitigation + trigger
Issue: happened → owner + ETA + comms plan
Escalate when: critical path slip > agreed threshold, scope creep without sponsor, unresolved cross-team conflict

See
references/dependency_risk.md
for RAID columns.

风险：可能发生的情况 → 缓解措施 + 触发条件
问题：已发生的情况 → 负责人 + 预计解决时间 + 沟通计划
需升级的场景：关键路径延误超出约定阈值、未经发起人批准的范围蔓延、未解决的跨团队冲突

RAID列说明请参考
references/dependency_risk.md
。

5. Stakeholder communication

5. 相关方沟通

Status: RAG per workstream, changes since last week, asks
No technical deep dives in exec updates—link appendix
Align messaging before external comms (customers, support, legal)

See
references/stakeholder_comms.md
for audience-specific formats.

状态：按工作流划分RAG状态、自上次报告以来的变更、需求请求
高管更新中不涉及技术细节——可链接附录内容
对外沟通（客户、支持团队、法务）前需统一消息口径

针对不同受众的沟通格式请参考
references/stakeholder_comms.md
。

6. Launch readiness

6. 发布就绪检查

Gate checklist before production:

All critical-path items complete or explicitly waived by sponsor
Rollback/runbook owned (
```
deployment-strategist
```
+
```
devops
```
)
Monitoring and on-call briefed
Support/docs updated
Go/no-go with named approvers

See
references/launch_readiness.md
for full checklist.

上线前需完成以下检查清单：

所有关键路径项已完成或经发起人明确豁免
回滚/运行手册已确定负责人（
```
deployment-strategist
```
+
```
devops
```
）
监控与值班人员已完成 briefing
支持文档已更新
由指定审批人完成上线/不上线决策

完整检查清单请参考
references/launch_readiness.md
。

When to load references

何时参考文档

Charter and phases →
```
references/program_charter.md
```
Dependencies and RAID →
```
references/dependency_risk.md
```
Status and steering →
```
references/status_reporting.md
```
Exec and sponsor comms →
```
references/stakeholder_comms.md
```
Go/no-go →
```
references/launch_readiness.md
```

章程与阶段规划 →
```
references/program_charter.md
```
依赖关系与RAID管理 →
```
references/dependency_risk.md
```
状态报告与管控 →
```
references/status_reporting.md
```
高管与发起人沟通 →
```
references/stakeholder_comms.md
```
上线/不上线决策 →
```
references/launch_readiness.md
```