Shulou(Shulou.com)06/03 Report--

Introduction:

In the agile development model, Sprint Retrospective Meeting is also an essential part, it usually occurs at the end of each Sprint, its main role is to make a phased summary of the current iteration cycle, including the good aspects and the bad aspects, and then we can enhance the strengths and avoid weaknesses in the next iteration, so it is also good for the healthy development of a team.

Implementation method:

Generally speaking, our project team completes the Sprint Retrospective Meeting through the round table, and there will be corresponding people (usually the project team will take turns according to the name sequence) to record the Meeting Minutes. We generally carry out Retrospective from the following aspects.

(1) how efficient is the development team?

(2) how does the development team work together?

(3) whether the project progress curve is stable or not.

(4) what is the division of labor between the front end and the back end of the development team

(5) what is the defect reporting rate of the test team?

(6) are there any serious Block factors in the development cycle.

(7) are there any ambiguities in demand that lead to Rework

(8) is there any imbalance in the allocation of tasks, resulting in individuals being too busy or too idle?

Of course, each factor is due to the team, once we have sorted out these good / bad aspects, we should use a special place to record them, the best way to store these records must be Wiki, because it is easy to read, of course, it is possible to record with some documents, but you must have a unified specification for the file name, and the most important thing is: once summed up Team leader must lead team to implement it as much as possible, not just leave it there without anyone watching, so it loses its meaning.

Here I give you a Retrospective Meeting record of our last Sprint.

Summary:

Sprint Retrospective Meeting must be taken very seriously, because it is very important, as Confucius said: "learning without thinking is labor lost, thinking without learning is perilous." this is the case with learning, and the project must also abide by this principle, because only by constantly reflecting on and summing up the situation of Sprint, can the team develop its strengths and circumvent its weaknesses and make the team develop more healthily. And execution is very important, which takes into account the prestige and quality of team leader.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.