- 关 键 词：
- activities
Introduction
简介
Purpose目的
Significant insight can be gained by analyzing a software development project and identifying which processes, activities, and characteristics were successful and which were not. The primary goal of a project retrospective (also called a post-mortem, debriefing, or post-project review) is to learn lessons and make process improvements that can help planning and execution on future projects. This learning occurs by raising significant positive and negative issues, identifying root causes, and recommending improvements, typically through a retrospective meeting. This document describes a procedure for conducting a project retrospective.
通过分析软件开发项目并识别哪些过程，活动和特征的成功与否可以获得对项目深刻的认识。项目回顾（也称为事后析误、报告分析，或结项评审）的主要目的是吸取经验教训并改进过程，使之有助于未来项目的计划和执行。这个过程往往通过提出重要的正面和负面问题、找出问题根源，提出改进建议，特别是举行回顾会的方式进行。本文将阐述执行项目回顾的过程。
Each project should hold a retrospective at the end of its lifecycle. For projects of more than six months duration, mid-project reviews can also be useful. Retrospectives can be held at major milestones or at the end of release cycles.
每个项目都应在结束时进行回顾。对周期超过六个月的项目，中期回顾也很有帮助。回顾会可以在项目的重要里程碑处或发布结束时进行。
Work Aids辅助工件
Retrospective Planning WorksheetRetrospective Summary Report Template回顾计划工作单回顾总结报告模版
References参考文献
1. Kerth, Norman L. Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House Publishing, 2001.
2. Wiegers, Karl, and Johanna Rothman. “Looking Back, Looking Ahead,” Software Development, vol. 9, no. 2 (February 2001), pp. 65-69.
Roles角色
简介
Purpose目的
Significant insight can be gained by analyzing a software development project and identifying which processes, activities, and characteristics were successful and which were not. The primary goal of a project retrospective (also called a post-mortem, debriefing, or post-project review) is to learn lessons and make process improvements that can help planning and execution on future projects. This learning occurs by raising significant positive and negative issues, identifying root causes, and recommending improvements, typically through a retrospective meeting. This document describes a procedure for conducting a project retrospective.
通过分析软件开发项目并识别哪些过程，活动和特征的成功与否可以获得对项目深刻的认识。项目回顾（也称为事后析误、报告分析，或结项评审）的主要目的是吸取经验教训并改进过程，使之有助于未来项目的计划和执行。这个过程往往通过提出重要的正面和负面问题、找出问题根源，提出改进建议，特别是举行回顾会的方式进行。本文将阐述执行项目回顾的过程。
Each project should hold a retrospective at the end of its lifecycle. For projects of more than six months duration, mid-project reviews can also be useful. Retrospectives can be held at major milestones or at the end of release cycles.
每个项目都应在结束时进行回顾。对周期超过六个月的项目，中期回顾也很有帮助。回顾会可以在项目的重要里程碑处或发布结束时进行。
Work Aids辅助工件
Retrospective Planning WorksheetRetrospective Summary Report Template回顾计划工作单回顾总结报告模版
References参考文献
1. Kerth, Norman L. Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House Publishing, 2001.
2. Wiegers, Karl, and Johanna Rothman. “Looking Back, Looking Ahead,” Software Development, vol. 9, no. 2 (February 2001), pp. 65-69.
Roles角色
| Role角色保留地址 http://www.qqread.com/erp/33/z881143004.html进入讨论组讨论。
相关图文阅读
频道图文推荐
健 康 咨 询
时 尚 咨 询
 相关专题
讨论组问题推荐站内各频道最新更新文档站内最新制作专题热门关键字导读站内频道文章精选新闻资讯操作系统桌面开发数据库 |
