Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Scrum Product Ownership: Balancing Value from the Inside Out Paperback – March 2, 2013
|New from||Used from|
All Books, All the Time
Read author interviews, book reviews, editors picks, and more at the Amazon Book Review. Read it now
Frequently bought together
Customers who bought this item also bought
About the Author
Bob Galen is President and Principal Agile Coach (CSC) at RGCG, LLC; a technical consultancy focused towards increasing agility and craftsmanship within their clients’ software projects and teams. He has over 30 years of experience as a software developer, tester, project manager and leader. Bob regularly consults, writes, and is a popular speaker on a wide variety of software development topics. He can be reached at email@example.com
If you buy a new print edition of this book (or purchased one in the past), you can buy the Kindle Edition for FREE. Print edition purchase must be sold by Amazon. Learn more.
For thousands of qualifying books, your past, present, and future print-edition purchases now lets you buy the Kindle edition for $2.99 or less. (Textbooks available for $9.99 or less.)
Discover books for all types of engineers, auto enthusiasts, and much more. Learn more
Top customer reviews
What I Liked:
* The author provides many references throughout the book. In fact Appendix C has 22 desk references.
* There are many stories and contributions from Agile practitioners and authors.
* The author talks early on (Chapter 2) about the breadth of the Product Owner role and the fact there is one person who owns the overall responsibility, but there can by many others assisting in various activities.
* One of the best discussions on quality in an Agile project that I have ever read and how the Product Owner can influence quality (Chapter 6).
* An entire section dedicated to “Product Ownership at Scale”. The section about using Agile release trains was interesting but the author’s discussion about using Scrum of Scrums as a scaling model is pure gold.
What I Didn’t Like:
I have no complaints. I did see some reviews on Amazon that complained about typos and lack of proofreading, but nothing stood out to me. I also don’t understand giving someone a one star review about sentence fragments, but apparently it’s a burning issue for some folks.
“You don’t test in quality. By the time you get to testing, it’s too late. Your quality has already been instantiated into your code. Instead, your build quality into your DNA and work habits by individually adopting some of these core values:” (page 54)
I really love the concept that a Product Owner is a part of the team. They share success/failure together. When you read this book, I would suggest that you do NOT compare with other books or other definitions. You'd better focus on what you can learn from the book, focus on how it can help you in building a better product, having a better team.
However, some last chapters I do not understand since I have not had a chance to work in the "scale". Nonetheless, I am happy to give 5 stars. I feel lucky to read this book.
Bob also continually explains "why" which adds another layer of depth and understanding to the material that I often find lacking in other professional texts. It is a very easy read but readers should have some basic background on the Agile methodology and Scrum concepts before jumping into this.
I have recommended this book to my manager and peers, and everyone has been impressed by this book. I believe that any member of a team that is or plans to practice Scrum would benefit greatly from this book since it so clearly conveys the complexity and criticality of the role that every team member needs to understand and respect in order for Scrum to work! I also don't believe that it is possible for "one" person to fulfill the PO role (which I consider to be the engine of Scrum), which is why it is important for all team members to understand it.
Also, there is no other book out there like this one.
Especially, the view on the role of PO is great. POs should not throw the stories over the wall. :)