Auto-sync: 2026-04-29 04:03
This commit is contained in:
48
wiki/concepts/BOSCARD.md
Normal file
48
wiki/concepts/BOSCARD.md
Normal file
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: "BOSCARD"
|
||||
type: concept
|
||||
tags: [Business-Analysis, Requirements, Project-Management]
|
||||
sources: [public-cloud-learning-sessions-applicable-business-analysis-techniques-20240109]
|
||||
last_updated: 2026-05-11
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
BOSCARD 是一个用于定义复杂新工作的结构化框架,通过八个维度全面澄清项目背景和关键要素。
|
||||
|
||||
## BOSCARD 八要素
|
||||
|
||||
| 字母 | 要素 | 含义 |
|
||||
|------|------|------|
|
||||
| **B** | Background | 背景——为什么需要这项工作? |
|
||||
| **O** | Objectives | 目标——我们希望实现什么? |
|
||||
| **S** | Scope | 范围——包含什么?不包含什么? |
|
||||
| **C** | Constraints | 约束——时间、预算、技术等限制条件 |
|
||||
| **A** | Assumptions | 假设——我们认为哪些前提条件是成立的? |
|
||||
| **R** | Risks | 风险——可能出错的因素有哪些? |
|
||||
| **R** | Roles | 角色——谁负责什么? |
|
||||
| **D** | Deliverables | 交付物——最终产出是什么? |
|
||||
|
||||
## Key Quote
|
||||
|
||||
> "If you can get scope tied down early on and agreed, that's priceless."
|
||||
|
||||
范围(Scope)的早期锁定和达成共识是无价的——这正是 BOSCARD 的核心价值所在。
|
||||
|
||||
## Application Scenario
|
||||
|
||||
BOSCARD 特别适用于:
|
||||
- 新项目的立项定义
|
||||
- 复杂需求的澄清会议
|
||||
- 变更请求的评估
|
||||
- 跨团队协作的初始对齐
|
||||
|
||||
## Relationship to Other Concepts
|
||||
|
||||
- [[Business-Analysis]]:BOSCARD 是业务分析的核心技法之一
|
||||
- [[Stakeholder-Wheel]]:BOSCARD 通常在识别干系人之后使用
|
||||
- [[Requirements-Gathering]]:BOSCARD 定义的范围指导后续的需求收集
|
||||
|
||||
## Aliases
|
||||
- BOSCARD Technique
|
||||
- 复杂工作定义框架
|
||||
Reference in New Issue
Block a user