Introduction:
In the agile development model, Sprint Retrospective Meeting is also an essential link, which usually occurs at the end of each Sprint, and its main role is to make the current iteration of a periodic summary, both good and bad aspects aspects, then we can avoid weaknesses in the next iteration, so this is a healthy development team is also good.
Method to realize:
Generally, we are the team to complete the Sprint Retrospective Meeting by the Round Table, there will be a corresponding people (usually people take turns in accordance with the project team name sequence) Record the Meeting Minutes. We generally be Retrospective from the following aspects.
(1) how the development team efficiency
(2) how the development team
(3) whether the smooth progress of the project curve
(4) how to develop team leading and trailing ends of the division of labor
How (5) Test Team defect reporting rate
(6) development cycle has not been a serious factor in the Block.
(7) There is no demand-side uncertainty leads Rework
(8) There is no imbalance in the distribution of tasks, resulting in an individual who is too busy or too busy.
Of course, the team only because of various factors, once collated these good / bad aspects, we should use special place to record them, the best way to store these records is certainly Wiki, because it's easy to read, of course with some documents is also possible to record, but you have to have a unified specification for the file name, the key is: Once the summary down, team leader must lead the team to implement as much as possible, and not only remember where no one , that would be meaningless.
I am here to give us a record of the last Sprint Retrospective Meeting of.
to sum up:
Must be very seriously Sprint Retrospective Meeting, because it is very important, as Confucius says: "Learning without thought is labor lost, thought without learning is perilous" to learn is to do the same project must comply with this principle, because the only constant Sprint reflection summarize the situation, in order to avoid weaknesses, so the team more healthy development forward. And execution is very important, to consider the prestige and quality of the team leader.
This article comes from " parallel lines cohesion " blog, http://supercharles888.blog.51cto.com/609344/1262685
Reproduced in: https: //www.cnblogs.com/JoannaQ/p/3251410.html