Auto-sync: 2026-04-29 04:03
This commit is contained in:
66
wiki/concepts/T-Shaped-Skills.md
Normal file
66
wiki/concepts/T-Shaped-Skills.md
Normal file
@@ -0,0 +1,66 @@
|
||||
---
|
||||
title: "T-Shaped Skills"
|
||||
type: concept
|
||||
tags: [Skills, Agile, Business-Analysis]
|
||||
sources: [public-cloud-learning-sessions-applicable-business-analysis-techniques-20240109]
|
||||
last_updated: 2026-05-11
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
T 型技能(T-Shaped Skills)是一种人才技能模型,形容人才在某一领域具有深度专业能力(竖线),同时对相关领域具有广泛的理解和协作能力(横线)。
|
||||
|
||||
## Visual Representation
|
||||
|
||||
```
|
||||
广度(相关技能理解)
|
||||
──────────────────────────────
|
||||
│
|
||||
│ 深度(核心专业能力)
|
||||
│
|
||||
│
|
||||
```
|
||||
|
||||
## T 型技能的构成
|
||||
|
||||
### 竖线(Depth)—— 核心专业深度
|
||||
在某一领域达到专家水平:
|
||||
- 深度技术技能
|
||||
- 领域专业知识
|
||||
- 解决问题的能力
|
||||
|
||||
### 横线(Breadth)—— 相关技能广度
|
||||
对相关领域有基本理解和协作能力:
|
||||
- 业务流程理解
|
||||
- 跨职能沟通能力
|
||||
- 理解相邻领域的术语和约束
|
||||
|
||||
## Why T-Shaped in Agile Squads
|
||||
|
||||
在敏捷 Squad(特性团队)中,T 型技能弥合了业务与技术之间的鸿沟:
|
||||
|
||||
| 技能类型 | 在敏捷中的价值 |
|
||||
|---------|--------------|
|
||||
| 业务分析技能 | 理解业务需求,转化为技术方案 |
|
||||
| 技术技能 | 实现技术解决方案 |
|
||||
| 沟通协作技能 | 跨职能团队的顺畅协作 |
|
||||
|
||||
### 具体场景
|
||||
- **业务分析师 + T型技能**:不仅懂需求分析,还能理解技术约束和测试策略
|
||||
- **开发者 + T型技能**:不仅能写代码,还能理解业务背景和用户体验
|
||||
- **测试工程师 + T型技能**:不仅能测试,还能理解需求意图和代码结构
|
||||
|
||||
## Relationship to Other Concepts
|
||||
|
||||
- [[Business-Analysis]]:业务分析师的理想技能模型是 T 型技能
|
||||
- [[AgilePractices]]:敏捷 Squad 依赖 T 型技能人才实现跨职能协作
|
||||
- [[Requirements-Gathering]]:T 型技能帮助更好地收集和理解需求
|
||||
|
||||
## Key Quote
|
||||
|
||||
> "T-shaped skills are valuable in agile squads, combining core expertise with a broad understanding of related skills. Business analysis skills bridge the gap between business problems and technical solutions."
|
||||
|
||||
## Aliases
|
||||
- T 型技能
|
||||
- T型人才培养
|
||||
- 跨职能技能
|
||||
Reference in New Issue
Block a user