Warning: this review is based on the pre-released leanpub version of the book with some chapters still missing. I'll check out the released version and update my review when it's ready.<br/><br/>I'd rather gave the book 5 stars as its subject is indeed relevant and its ideas appeal very much to my agile and lean taste. This book will definitely help you approach software architecture in a lightweight manner avoiding rework in the near future, analysis paralysis and big design upfront. I highly recommend it to anyone working in software development.<br/><br/>I gave the book only 3 stars though because I didn't like 2 major points about the way those ideas are delivered.<br/><br/>First, the book is a series of essays. Though they are logically ordered, I missed the storyline throughout the book. I know it's a non-fiction, but the book in my opinion is too much about making the case for the method it presents, rather than actually describing and guiding the reader through the method. Essays also contain a lot of repetition, I've encountered some passages like three or four times in the book.<br/><br/>Second, I didn't like how the book tries to position itself against Agile. Though the book actually promotes quick feedback loops, iterative and incremental delivery, it in my opinion misrepresents agile as lacking any design activities. I think how the work stream is managed and what activities it contains is completely orthogonal. That's why the book would appeal much better to me if it focused itself on integrating architecture activities in management practices rather fighting them (it equally fights waterfall to be fair).