as most books on the topic, lacks on data and citations for the statements done, and is only aplicable for certain kind of companies, but completely ignores others such as software factories.
The author walks a very thin line when comparing story points to ideal days that doesn't make much sense given the explanation he provides. Additionally there are cases where he contradicts when he says or changes his stance on something (for example going from relative to absolute value for a given metric).
Ļoti koncentrēta informācijas ziņā grāmata. Tiek doti visi nepieciešamie pamati agile plānošanai un darbu novērtējumiem - gan kā vērtēt stāstījuma punktos vai ideālajās dienās, kā noteikt plānoto izstrādes ātrumu (velocity), kā saplānot iterāciju un relīzi. Katra nodaļa it kā būvē māju tālāk uz iepriekšējām nodaļām un dotās informācijas. Man patika, ka informācija ir skaidri izklāstīta, bez liekvārdības, bet arī ne pārāk sausi. Ļoti palīdz arī kā pēdējā nodaļa iekļautais "reālais" projekts, ar plānošanas sesijām, projekta apjoma aprakstiem, plāniem utt. Par labu grāmatai saka arī tas, ka man uzreiz gribējās pārskatīt iepriekšējā projekta gaitu (ko es arī uzsāku darīt), identificējot kļūdas (kuru bija daudz) un mēģinot atrast risinājumus, kā arī uzreiz ķerties pie jauna projekta plānošanas, iemēģinot piedāvātos risinājumus. No vienas puses žēl, ka šī grāmata neatnāca pie manis ātrāk, no otras - jau esot ar kļūdainu praksi, vieglāk saskatīt, kā ir pareizi un kā tas varētu strādāt.
This is one of the older books, on Agile that I hadn't read until recently- it is a new area for me. I have a fair deal of catching up to do here. The interest for me, here is a bit unusual- I do wonder, what feature planning entails. I am not sure if this is the right book for this. Recommended.
Wonderful book for any member of agile team interested in reasoning behind most popular estimation, prioritization and planning techniques as well as recommendations of proven practices from one of the most recognized Agile evangelist - Mike Cohn. Book is very well written, structured and easy to read. It accompanied with metaphors and anecdotes for better understanding of described topics. Last chapter written in form of fiction which summarizes all key points mentioned in the book on the example of agile team from mythical company. This book is must for product owners and scrum masters.
Buen material introductorio a la planeación y estimación del desarrollo de productos de software. Recomendable para aquellos que no tengan mucha idea o vengan del mundo de las estimaciones de proyectos no relacionados a software
Um bom guia tanto pra quem ainda não tá acostumado com o conceito ágil de desenvolvimento, como pra quem tá habituado mas sofre por não entender por que uma coisa acaba sendo feita do jeito X e não Y. Tem bastante explicação dos motivos de cada cerimônia e dos processos relacionado ao planejamento do projeto. O final tem uma narrativa fictícia de uma release sendo feita que ilustra bem a maioria dos conceitos apresentados no livro. Achei que fechou bem, reforçando e relembrando ao leitos os pontos discutidos de uma maneira mais prática.
Estimation is a tricky part of Agile process, and there is much misunderstanding about it. The book goes through estimation process in details. A big lesson is focusing on implementing concepts is more important than sticking with specific practices. It concludes with a realistic study case that summarizes most of concepts.