Agile Systems Engineering 1st Edition

This book contains an incredible amount of useful and practical information on how to do Agile MBSE, made only possible by the number of years of relevant experience and engineering practices of the author. If I had to extract only one sentence, it would be this one: "Modeling is Essential for Agile Systems Engineering". Based on my own experience with several poorly executed agile projects, I must recognize that complex Agile projects (using for instance SAFe) that do not use modeling will eventually "fail". Obviously, for companies that have a lot of resources and can waste their money, the failure may be different from a smaller company (that may simply disappear), but eventually their project will cost them a lot of money and time and resources and will be unmanageable and unmaintainable.

Good book, not the most understandable, was going to use it in my systems engineering classes.

This book is very well written, very informative and an excellent reference for my job!

Best book on the subject of MBSE/SysML. Great, well written introduction the subjects of MBSE, SysML and Agile.

The 8 chapters in this book present descriptions of the activities required in an AGIL Model Based Systems Engineering product development project in a logical well thought out sequence. Examples in each chapter are well chosen.

Must have forall System Engineers. Plenty of useful information for application of Agile Principles

Excellent Reference Book!

Agile Systems Engineering is both an interesting and useful book for systems engineers. Bruce Douglass makes an excellent case that the combination of agile and model based systems engineering practices can help systems engineers deal with the speed and complexity of the world they face today. A couple of things stood out to me in reading this book: 1) its target audience is systems engineers; he specifically addresses specification and design at the system level with the end products being those key artifacts that are handed to discipline-specific engineers; 2) this is a book for practioners; the book is chock full of useful guidance such as how to incrementally define and evaluate requirements; how to develop an executable architecture; and even low level things such as how to organize a model; 3) The chapter on “Agile Systems Architectural Analysis and Trade Studies is excellent. He clearly articulates a method and then shows its use on increasingly complex problems. In addition, the samples shown in the book are at just the right level to allow the reader to gain and understanding without being swamped in detail. It gets one’s blood flowing wanting to apply the information! This book is not a reference manual on SysML nor on agile methods. Rather it is an excellent resource for how to do systems engineering using the combination of MBSE and agility.