|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# 1. 沟通管理计划
|
|
|
|
|
|
|
|
|
|
|
|
| 沟通内容 | 频度 | 沟通方式 | 产出物 |
|
|
|
|
|
|
| :----------------------: | :--: | :------------------------: | :--------------------------------------------------: |
|
|
|
|
|
|
| 选题 | 1 | 交互式（团队讨论） | 产品使命、口号、策略 |
|
|
|
|
|
|
| 产品定义设计 | 1 | 交互式（团队讨论） | 产品的定义(包括产品的名称、发布时间、目标客户等信息) |
|
|
|
|
|
|
| 人员分配情况 | 3 | 交互式（团队讨论） | 任务分配表 |
|
|
|
|
|
|
| 产品原型设计 | 1 | 交互式（团队讨论） | 眼镜原型图设计、配套APP原型 |
|
|
|
|
|
|
| 产品用户故事 | 1 | 交互式（团队讨论） | 产品核心功能文件 |
|
|
|
|
|
|
| 产品功能实现 | 5 | 交互式（功能实现小组讨论） | 功能算法 |
|
|
|
|
|
|
| 产品测试 | 4 | 交互式（团队讨论） | 产品测试结果 |
|
|
|
|
|
|
| 交流方法 | 1 | 交互式（团队讨论） | 传递信息的技术与方法 |
|
|
|
|
|
|
| 信息收集和文件归档的结构 | 1 | 交互式（团队讨论） | 金山文档项目文件 |
|
|
|
|
|
|
|
|
|
|
|
|
# 2. 风险管理计划
|
|
|
|
|
|
<table align="center">
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td rowspan="2">风险名称</td>
|
|
|
|
|
|
<td colspan="5">所属维度</td>
|
|
|
|
|
|
<td rowspan="2">风险说明</td>
|
|
|
|
|
|
<td rowspan="2">影响程度</td>
|
|
|
|
|
|
<td rowspan="2">对工作量的影响</td>
|
|
|
|
|
|
<td rowspan="2">对进度和成本的影响</td>
|
|
|
|
|
|
<td rowspan="2">优先权</td>
|
|
|
|
|
|
<td rowspan="2">跟踪频率</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>资源</td>
|
|
|
|
|
|
<td>项目管理</td>
|
|
|
|
|
|
<td>外部因素</td>
|
|
|
|
|
|
<td>技术</td>
|
|
|
|
|
|
<td>进度</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>（根据严重性等级由低至高从1-5）中选择数值</td>
|
|
|
|
|
|
<td>（根据严重性等级由低至高从1-5）中选择数值</td>
|
|
|
|
|
|
<td>（根据严重性等级由低至高从1-5）中选择数值</td>
|
|
|
|
|
|
<td>（数值越小，优先权越高）</td>
|
|
|
|
|
|
<td>（根据严重性等级由低至高从1-5）中选择数值</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>需求变化风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>需求已经成为项目基准，但需求还在继续变化，最终因无法满足需求而导致任务失败</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>1</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>需求定义风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>需求定义欠佳，而进一步的定义会扩展项目范畴，或导致软件性能下降</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>2</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>产品定义含混风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>产品定义含混的部分比预期需要更多的时间</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>计划风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>计划是优化的，是"最佳状态"，但计划不现实，只能算是"期望状态"，可能导致任务失败</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>1</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>计划设计风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>涉足不熟悉的产品领域，花费在设计和实现上的时间比预期的要多</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>组织管理风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>低效的项目组结构降低生产率，或者缺乏必要的规范，导致工作失误与重复工作。</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>人员关系风险</td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>开发人员之间关系不佳，导致决策缓慢，导致沟通不畅、设计欠佳、接口出现错误和额外的重复工作，影响全局</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>人员技术风险</td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>某些人员需要更多的时间适应还不熟悉的软件工具和环境</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>6</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>开发工具风险</td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>开发工具不如期望的那样有效，开发人员需要时间创建工作环境或者切换新的工具</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>第三方工作风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>非技术的第三方的工作(预算批准、设备采购批准、法律方面的审查、安全保证等)时间比预期的延长</td>
|
|
|
|
|
|
<td>2</td>
|
|
|
|
|
|
<td>1</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>客户需求风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>客户没有或不能参与规划、原型和规格阶段的审核，导致需求不稳定和产品生产周期的变更</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>客户依赖风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>客户对于最后交付的产品不满意，要求重新设计和重做</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>1</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>产品功能风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>开发额外的不需要的功能(镀金)，延长了计划进度</td>
|
|
|
|
|
|
<td>2</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>产品兼容风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>严格要求与现有系统兼容，需要进行比预期更多的测试、设计和实现工作</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>产品设计风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>一些必要的功能无法使用现有的代码和库实现，开发人员必须使用新的库或者自行开发新的功能</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>代码集成风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>分别开发的模块无法有效集成，需要重新设计或制作</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>过程正规程度风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td>太不正规(缺乏对软件开发策略和标准的遵循)，导致沟通不足，质量欠佳，甚至需重新开发</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
<td>1</td>
|
|
|
|
|
|
<td>5</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
<tr>
|
|
|
|
|
|
<td>过程沟通风险</td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td></td>
|
|
|
|
|
|
<td>√</td>
|
|
|
|
|
|
<td>大量的纸面工作导致进程比预期的慢</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
<td>2</td>
|
|
|
|
|
|
<td>4</td>
|
|
|
|
|
|
<td>6</td>
|
|
|
|
|
|
<td>3</td>
|
|
|
|
|
|
</tr>
|
|
|
|
|
|
</table>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
