Agile Software Development practice-Summary

At the invitation of my friends, I am going to write a series of articles about the practice of agile software development, and also help friends who have not used Agile or only stay in books to visit the thrilling process of agile software development.

The so-called Agile, there are many introductions in books, I do not want to reinvent the wheel, anyway, as far as I understand, the essence of Agile is to face change, Agile this word, I first encountered in playing all kinds of games, the so-called "power" heroes, "agile" heroes, such as the Dark Amazon, such as World of Warcraft hunters, this profession often has a high degree of evasion, and can attack and defend Or Zhao Yun, the most typical of the three Kingdoms Kill, "kills and kills sparkly, can advance and retreat". For the project, I think this meaning is very similar, because it can be attacked and defended, facing change, so even if the demand changes, we need to "defend" and be able to hold it. If our project progress is insufficient, we can do some research, summary, code review and other work to fill our effort. This is "attack".

In general, as an Agile coach, I would like to talk about the following topics in Agile practice (all from our real team practices):

(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 Process/Release Plan

(8) Sprint Retrospective Meeting

For details, see the follow-up blog post.