Project Review Project Team Evaluation Manual

Author: Norman L. Kerth
Publisher:
Publish Date: Not available
Features: "Project Retrospectives: A Handbook for Team Reviews" describes in detail how to create a special set of activities to be implemented at the end of each project, which requires us to pause and reflect before starting the next project. This process 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 an important step in improving the software process! I say this because a well-executed retrospective can help team members understand the need for improvement and motivate them to change how they work. This change must be designed by the entire team, because only the team 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, a process that belongs to the team and can be utilized, celebrated, modified, or abandoned. Most importantly, it allows the team to repeatedly review itself after every project.