223 lines
8.0 KiB
JSON
223 lines
8.0 KiB
JSON
{
|
|
"knowledgeAreas": [
|
|
{
|
|
"id": "KA01",
|
|
"name": "项目整合管理",
|
|
"nameEn": "Project Integration Management",
|
|
"chapter": 4,
|
|
"order": 1,
|
|
"color": "#6366F1",
|
|
"description": "包括识别、定义、组合、统一和协调各项目管理过程组的各种过程和活动",
|
|
"processCount": 7,
|
|
"tailoringFactors": [
|
|
{
|
|
"title": "项目生命周期",
|
|
"description": "本项目合适的项目生命周期？项目生命周期应包括哪些阶段？"
|
|
},
|
|
{
|
|
"title": "开发生命周期",
|
|
"description": "对特定产品、服务或成果而言，什么是合适的开发生命周期和开发方法？预测型或适应型方法是否适当？如果使用适应型方法，开发产品是该采用增量还是迭代的方式？混合型方法是否为最佳选择？"
|
|
},
|
|
{
|
|
"title": "管理方法",
|
|
"description": "考虑到组织文化和项目的复杂性，哪种管理过程最有效？"
|
|
},
|
|
{
|
|
"title": "知识管理",
|
|
"description": "在项目中如何管理知识以营造合作的工作氛围？"
|
|
},
|
|
{
|
|
"title": "变更",
|
|
"description": "在项目中如何管理变更？"
|
|
},
|
|
{
|
|
"title": "治理",
|
|
"description": "有哪些监控机构、委员会和其他干系人该参与项目治理？对项目状态报告的要求是什么？"
|
|
},
|
|
{
|
|
"title": "经验教训",
|
|
"description": "在项目期间及项目结束时，应收集哪些信息？历史信息和经验教训是否适用于未来的项目？"
|
|
},
|
|
{
|
|
"title": "效益",
|
|
"description": "应该在何时以何种方式报告效益，是在项目结束时还是在每次迭代或阶段结束时？"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "KA02",
|
|
"name": "项目范围管理",
|
|
"nameEn": "Project Scope Management",
|
|
"chapter": 5,
|
|
"order": 2,
|
|
"color": "#8B5CF6",
|
|
"description": "确保项目包含且只包含成功完成项目所需的全部工作",
|
|
"processCount": 6
|
|
},
|
|
{
|
|
"id": "KA03",
|
|
"name": "项目进度管理",
|
|
"nameEn": "Project Schedule Management",
|
|
"chapter": 6,
|
|
"order": 3,
|
|
"color": "#EC4899",
|
|
"description": "管理项目按时完成所需的各个过程",
|
|
"processCount": 6,
|
|
"tailoringFactors": [
|
|
{
|
|
"title": "生命周期方法",
|
|
"description": "哪种生命周期方法最适合制订详细的进度计划？"
|
|
},
|
|
{
|
|
"title": "资源可用性",
|
|
"description": "影响资源可持续时间的因素是什么（如可用资源与其生产效率之间的相关性）？"
|
|
},
|
|
{
|
|
"title": "项目维度",
|
|
"description": "项目复杂性、技术不确定性、产品新颖度、速度或进度跟踪（如挣值、完成百分比）如何影响预期的控制水平？"
|
|
},
|
|
{
|
|
"title": "技术支持",
|
|
"description": "是否采用技术来制定、记录、传递、接收和存储项目进度模型的信息以及是否易于获取？"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "KA04",
|
|
"name": "项目成本管理",
|
|
"nameEn": "Project Cost Management",
|
|
"chapter": 7,
|
|
"order": 4,
|
|
"color": "#10B981",
|
|
"description": "规划、估算、预算、融资、筹资、管理和控制成本的各过程",
|
|
"processCount": 4,
|
|
"tailoringFactors": [
|
|
{
|
|
"title": "知识管理",
|
|
"description": "组织是否拥有易于使用的、正式的知识管理体系和财务数据库并要求项目经理使用？"
|
|
},
|
|
{
|
|
"title": "估算和预算",
|
|
"description": "组织是否拥有正式或非正式的，与成本估算和预算相关的政策、程序和指南？"
|
|
},
|
|
{
|
|
"title": "挣值管理",
|
|
"description": "组织是否采用挣值管理来管理项目？"
|
|
},
|
|
{
|
|
"title": "敏捷方法的使用",
|
|
"description": "组织是否采用敏捷或适应型方法管理项目？这对成本估算有什么影响？"
|
|
},
|
|
{
|
|
"title": "治理",
|
|
"description": "组织是否拥有正式或非正式的审计和治理政策、程序和指南？"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "KA05",
|
|
"name": "项目质量管理",
|
|
"nameEn": "Project Quality Management",
|
|
"chapter": 8,
|
|
"order": 5,
|
|
"color": "#F59E0B",
|
|
"description": "把组织的质量政策应用于规划、管理、控制项目和产品质量要求",
|
|
"processCount": 3,
|
|
"tailoringFactors": [
|
|
{
|
|
"title": "政策合规与审计",
|
|
"description": "有哪些质量政策和程序？使用哪些质量工具、技术和模板？"
|
|
},
|
|
{
|
|
"title": "标准与法规合规性",
|
|
"description": "是否存在必须遵守的行业质量标准？需要考虑哪些政府、法律或法规方面的制约因素？"
|
|
},
|
|
{
|
|
"title": "持续改进",
|
|
"description": "如何管理项目中的质量改进？在组织层面还是单个项目层面管理？"
|
|
},
|
|
{
|
|
"title": "干系人参与",
|
|
"description": "项目环境是否有利于与干系人及供应商合作？"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "KA06",
|
|
"name": "项目资源管理",
|
|
"nameEn": "Project Resource Management",
|
|
"chapter": 9,
|
|
"order": 6,
|
|
"color": "#3B82F6",
|
|
"description": "识别、获取和管理所需资源以成功完成项目",
|
|
"processCount": 6,
|
|
"tailoringFactors": [
|
|
{
|
|
"title": "多元化",
|
|
"description": "团队的多元化背景是什么？"
|
|
},
|
|
{
|
|
"title": "物理位置",
|
|
"description": "团队成员和实物资源的物理位置在哪里？"
|
|
},
|
|
{
|
|
"title": "行业特定资源",
|
|
"description": "所在行业需要哪些特殊资源？"
|
|
},
|
|
{
|
|
"title": "团队成员的获得",
|
|
"description": "如何获得项目团队成员？项目团队成员是全职还是兼职？"
|
|
},
|
|
{
|
|
"title": "团队管理",
|
|
"description": "如何管理项目团队建设？组织是否有管理团队建设的工具或是否需要创建新工具？是否存在有特殊需求的团队成员？是否需要为团队提供有关多元化管理的特别培训？"
|
|
},
|
|
{
|
|
"title": "生命周期方法",
|
|
"description": "项目采用哪些生命周期方法？"
|
|
}
|
|
]
|
|
},
|
|
{
|
|
"id": "KA07",
|
|
"name": "项目沟通管理",
|
|
"nameEn": "Project Communications Management",
|
|
"chapter": 10,
|
|
"order": 7,
|
|
"color": "#06B6D4",
|
|
"description": "确保项目信息及时且恰当地规划、收集、生成、发布、存储、检索、管理、控制、监督和最终处置",
|
|
"processCount": 3
|
|
},
|
|
{
|
|
"id": "KA08",
|
|
"name": "项目风险管理",
|
|
"nameEn": "Project Risk Management",
|
|
"chapter": 11,
|
|
"order": 8,
|
|
"color": "#EF4444",
|
|
"description": "规划风险管理、识别风险、开展风险分析、规划风险应对、实施风险应对和监督风险的各个过程",
|
|
"processCount": 7
|
|
},
|
|
{
|
|
"id": "KA09",
|
|
"name": "项目采购管理",
|
|
"nameEn": "Project Procurement Management",
|
|
"chapter": 12,
|
|
"order": 9,
|
|
"color": "#84CC16",
|
|
"description": "从项目团队外部采购或获取所需产品、服务或成果",
|
|
"processCount": 3
|
|
},
|
|
{
|
|
"id": "KA10",
|
|
"name": "项目相关方管理",
|
|
"nameEn": "Project Stakeholder Management",
|
|
"chapter": 13,
|
|
"order": 10,
|
|
"color": "#F97316",
|
|
"description": "识别影响或受项目影响的人员、团体或组织，分析其期望和影响，制定管理策略",
|
|
"processCount": 4
|
|
}
|
|
]
|
|
}
|