This book has bought a period of time, but recently, it is really a long, the book is not thick, about 300 pages, but it feels a lot after reading. This book does not teach you specific modeling technology, such as UML, mode, etc. Important section. Then expand various products in the agile modeling, and the combination of XP, XP. For myself, the biggest gain of reading this book is not aware of some techniques, but understands a truth. In the software development process, the master of "degree" is important, from the traditional heavy software development process to now Agile development, the most important thing is not test driver, not pairing programming, the most important thing is the redefinition of "degrees" in software development, and seeks balance between excessive excessive excessive. We often use "excessive design", "too many documents", etc., there is no one to master the "degree", and these things are not faulty, the opposite is that they cannot be replaced. The mastery of "degrees" directly extends to "suitable", "there is no best, only better", according to its own project size, team composition, administrative organization, find the process suitable for yourself. Otherwise you are now "agile" now, but it is still facing the risk of out of control.
"It's just", "I must be reversed", it is really an ideal in balance point. Only adjust the direction in software development, although not the most correct direction, but warranty we don't deviate too far.
