Project Review Cases

A company started an Agile development project starting in late June 2015, ending in mid-August, bringing in more than 60 developers, testers and managers, and on August 31, 2015, the consultant as moderator led the team's more than 10 core personnel, A systematic review of the whole project was carried out, and the whole review process was summarized as follows:

1 The consultant spent 1 hours explaining how to review the project. This paper emphasizes the purpose, method, steps and precautions of the review, and gives some summary examples of the company. The meeting rules were established for this summary meeting:

(1) The matter is not human;

(2) not allowed to digress;

(3) Limit the time for each person to speak;

(4) Everyone has to speak;

(5) To find the shortcomings, but also to find the advantages;

(6) ...

2 Consultants first summarize and analyze the existing measurement data, including the total workload, the workload of various types of personnel, the number of defects, the cost of the project. The data that surprised the team members were two, the total cost of the whole project was about $2.57 million, and the cost of discovering each bug was $1636. Do not look at the data, did not expect the company's investment in the whole project is so big, did not expect to find the cost of defects so high.

3 invited members of the meeting to evaluate the final outcome of the project, the success level of the project was divided into 5 levels, the participation of 16 people, 11 people gave 4 points of evaluation, 5 people gave 3 points.

4 The Consultant guides you through all the outputs produced throughout the development process, identifying the experiences and lessons learned in the process of producing the output for each type of output.

5 Consultants guide you through all the impressive things that have taken place throughout the development process, thus summarizing the relevant lessons from these things.

Everyone is impressed by the significant setbacks that have taken place and the interesting anecdotes of the members of the project group that are prominent personalities. Each stage of the occurrence of the matter, have been a corresponding summary.

6 Consultants guide you through the process of project development of emotional fluctuations in the curve, from which to analyze why everyone happy, why depressed.

7 in order to ensure that the full speech, the simple 20 minutes of non-management meetings, ask the project manager and other middle and senior staff to leave the field, we have more reflection on the issue of project management.

8 at the end of the conference, we reflect on the advantages and improvements of this summary:

(1) Pre-session metrics data is not well prepared.

(2) The atmosphere is not easy.

(3) Time is a bit long.

(4) A large conference room should be found without group discussion.

(5) Records should be collated in a timely manner to facilitate eventual agreement.

(6) should be a personal summary, then the group summary, the final summary of the whole project together.

(7) The issue has been actively discussed.

(8) Communication meetings without managers are more effective.

9 after the meeting, the recorder system collated the advantages and improvements, all of which covered: requirements, design, coding, integration, testing, defect repair, project initiation, project completion, documentation, product demonstrations, development planning, project tracking control, stand-up meetings, Kanban, team building, project logistics, etc. Accumulated 103 found, of which 34, the improvement Point 69.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Project Review Cases