Agile Software Development Practice: a summary

At the invitation of my friend, I am prepared to write a group of articles on Agile software development practices, but also to help the vast number of people who have not used agile or just stay on the book content to visit the Agile software development of this thrilling process.

The so-called agile, there are many books on the introduction, I do not want to repeat the invention of the wheel, anyway, on my understanding, the essence of agile is to change, the word agile, the first time I encountered is in playing a variety of games, the so-called "power" heroes, "agile" heroes, such as the dark Amazon, such as the World of Warcraft hunter, This kind of profession often has very high Dodge, and can attack can guard, or say Three Kingdoms kill inside the most typical Zhao "flash kill to Kill to shine, can enter the ability to return", for the project, I think this meaning is very similar, because can attack can be guarded, change-oriented, so even if the demand change, we need to "shou", can hold, if our project progress is insufficient, We can do some research, summary, code review and so on to fill our effort, this is "attack".

In general, I would like to say the following topics in agile practice (all from the practice of our real team):

(1) Sprint Setup Meeting

(2) Sprint Story Point Etimation

(3) Sprint Task Split

(4) Sprint Status Track

(5) Team Management

(6) Code Review Process

(7) Release plan

(8) Sprint Retrospective Meeting

(9) Daily/weekly Status

See the following posts in detail

This article from the "Cohesion of parallel Lines" blog, please be sure to retain this source http://supercharles888.blog.51cto.com/609344/1261087