Subsequent chapters devoted Personom and User story, despite the undoubted merits also seem slightl

Title and book cover promises a healthy dose of knowledge from different agile methodologies, supported by practice. Does the author kept that promise? We tried to find out, sometimes with difficulty wading through reading.
The most important drawback of the book is its organization and uneven level - where Scrum is described e filing honestly and in fact can be chapters devoted to it a lot to learn, it's the initial e filing chapters and the "shortcut" on the other Agile methodologies leave much to be desired, giving the impression of hasty and unfinished.
Let's start from the beginning. "Chapter 2: Waterfall". This raises the question why the author mentions only this one method of preparation, aside from incremental and iterative methods? Persons reading this book and do not have more knowledge in the field of software engineering may have the impression that software production is a choice between Waterfall and Agile, the Agile is presented as the only right option. Are people involved in Agile not heard of others outside waterfall model? Do you also consciously avoid the subject, knowing that the comparison with other methods of Agile does not give such spectacular applications as a superficial description of the model of cascade? e filing In the book, the answer to that we find.
"Chapter 3: Agile" - nothing new to present the well-described methods and principles of Agile. Thoughtful and powerful left unsatisfied e filing chapter 3.4 Comparison of Agile and traditional. Several graphs without giving any sources of data and no comment. There is another question, why is this necessary, you do not need to explain that the reliability information in this way is negligible.
"Chapter 4: Family e filing of Agile methods" - another disappointment e filing and uneven level. Browsing the contents we hoped to find out something specific about the less popular Agile methods, such as interesting, but little e filing documented Crystal. What do we get? Little more than the first edge of search result e filing on Google. Chapter 4 gives the impression of an ill and unfinished, several e filing of the agile methods are described so briefly e filing and selectively, that is not entirely clear what purpose this chapter is actually. In addition, e filing the title of the book foreshadowed the theory and practice of Agile methods - so far (almost 100 page), this practice as a cure.
Chapters 5 and 6 saves total value of the item. Description and analysis of Scrum Scrum Guide, despite not revealing the nature and number of misunderstandings, a good description of the method and its principles. After reading the chapters Scrum appears the impression that it is for the author should focus, instead of moving many other topics, the value for the whole publication remains inscrutable. That's what we believe is missing, then deeper analysis method Scrum, threats and risks associated with this approach, the links between the processes of software development, and the elements of Scrum like. Components of this knowledge are scattered between the lines almost the entire book, disappearing among the sea of unnecessary information. Meeting these topics in one place would facilitate reading and understanding the realities of introducing Agile to the organization, in addition eliminate information e filing chaos occurring in many places of publication. e filing Chapters 5 and 6, a good part of the book, the only comment on the contents of this suggestion expand briefly raised threads.
"Chapter 7: Problems e filing with the requirements" and subsequent disappointment. Superficial, selective treatment of the subject which is one of the biggest challenges IT. Once again the question arises, why start a topic that never ends? Moreover, reliance on the data source (Chaos Report) from more than 10 years and older did not improve the accuracy of the information. The purpose of this "chapter" (hard to talk about chapter - 3 pages of text including graphics) remains a mystery. There is a lack of proposals, analysis, recommendation ... So why?
"Chapter 8: Vision". e filing Intention to indicate the validity of the vision is laudable, but not knowing the term "vision of the project" and its importance for the projects on the impression torn out of context. What is the vision of the Agile methodologies and implementation of projects? Some readers probably a guess, based on your existing knowledge. Others will remain with the lack of answers to this question.
Subsequent chapters devoted Personom and User story, despite the undoubted merits also seem slightly chaotic and out of context. Amazement is a section "10.2: Comparison with IEEE 830" - one page of text "comparison" without any information about the contents of IEEE 830 and a clear reference to that to which the author tries without success to compare the User Story. This raises the question, are you sure the author knows the contents e filing of IEEE 830 ...
Chapter 11 refers to the estimation. And again reveals a superficial approach to the subject. Why replace the method of function points without sufficient description of operating principles, applications and risks? Agile Estimating described