Project Review - Project Team Evaluation Manual

Author: [USA] Kels, written by, translated by Zheng Liping, Song Jianyun
Publisher:
Publishing Time: Not available
Features: "Project Retrospectives: A Handbook for Team Members" details how to create a special activity procedure to be implemented at the end of each project, requiring a moment of reflection 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 truly knows how to confirm, organize pending issues, and determine the priority of solving them. Completing these changes will help the team become the masters of the software development process—one that belongs to the team, can be utilized, celebrated, modified, or abandoned. Most importantly, it allows the team to repeatedly evaluate after every project.