Playful and thought-provoking, The Art of Business Value explores what business value means, why it matters, and how it should affect your software development and delivery practices. More than any other IT delivery approach, DevOps (and Agile thinking in general) makes business value a central concern. This book examines the role of business value in software and makes a compelling case for why a clear understanding of business value will change the way you deliver software.
This book will make you think deeply about not only what it means to deliver value but also the relationship of the IT organization to the rest of the enterprise. It will give you the language to discuss value with the business, methods to cut through bureaucracy, and strategies for incorporating Agile teams and culture into the enterprise. Most of all, this book will startle you into new ways of thinking about the cutting-edge of Agile practice and where it may lead.
Regular price: $21.90
Buy Now with 1 Credit
Buy Now for $21.90
Customer ReviewsMost Helpful
By Matthew Greene on 14-07-2018
Collection of unfinished thoughts
Narration was good but the story rambled and continually contradicted itself for the amusement of the author. If you are looking for a book to help you deal with or understand business value, you should keep looking. This book not only doesn't answer the question, it also questions the very premise of trying to answer the question. It rambles on for chapter after chapter and never offers any sage wisdom. It is the functional equivalent of "bla bla bla" and offers no solutions. All its thought paths are dead- ends. I hope Mr. Schwartz writes another book on business value post the epiphany he seems to be looking for.
1 of 1 people found this review helpful
By Srikanth Ramanujam on 17-05-2018
Worth a couple of articles at best -- do not buy
This is probably one of the first negative reviews that I am writing on any book. Only in the last two chapters there is some discussions on what business value could be. That material there is probably worth only a couple of blog posts or articles - I felt disappointed in buying a book for it. Well, I could return the book and get a refund, but I did keep it as a memory of the lack of "value" - that is great teacher.
Mark Schwarz clearly from the book moans about Scrum and the role of the Product Owner. I get it, PO role is poorly constructed in most organizations. But his book is filled with confirming his misunderstandings of meta process frameworks. He expects Scrum and Large Scale Scrum to define what "value" is. "Value" is in the eyes of the beholder. Scrum/LeSS neither defines "value" nor defines "product management" nor defines "software development practices" not defines "release management practices" -- there are several models, frameworks and practices covering those. They neither make a claim that they are the answer to these practices.
For eg. Amazon values their customers but not their employees so much. SouthWest loves their customers, but their employees even more. And someone like Uber values neither its employees, its customers, its contracted drivers, but only focuses on itself - making money.
I would strongly suggest that Mark pull this book out from the store, go back to his basics and start learning "Scrum" again.