Project Review: Project Team Evaluation Manual

Author: [USA] Kels, written by, translated by Zheng Liping, Song Jianyun
Publisher:
Publish Date: 2003-01-01
Features: "Project Retrospectives: A Handbook for Team Members" provides a detailed description of how to create a special activity procedure to be implemented at the end of each project, which requires us to pause and reflect before starting the next project. This procedure has various names, such as post-mortem analysis or postpartum diagnosis, but I prefer to call it a retrospective, which is quite important for our software practices. In fact, I believe it is a key step in improving the software process! This is because a well-executed retrospective can help team members understand the necessity of improvement and motivate them to change how they work. This change must be designed by the entire team, as only the team knows how to confirm, organize pending issues, and determine the priority of solving these problems. Completing these changes will help the team become the masters of the software development process, a process that belongs to the team, which can be utilized, praised, modified, or abandoned. What is most important is that it enables the team to review again and again after every project.