When it was first published in 2009, Scrum Product Ownership was the first book to address the Product Owner role in detail It was a breakthrough guide in how to drive high quality and customer value, while maintaining a singular focus on agile delivery principles Fast forward to 2013 and much has changed Scrum and the other agile methods are dominating the mainstream and new success stories seem to be forthcoming daily However, there are still challenges and many surround the Product Owner role scaling Scrum, sustaining quality, delivering and measuring value, providing team leadership, being a part of organizational transformation, and simple survival are all still in play In other words, the role is still just plain HARD The Second Edition of Scrum Product Ownership is being delivered to help with today s challenges It has practical advice, real world tactics, and stories It provides a framework of ideas to help today s Product Owners and their teams to better Deliver the Goods However, it remains true to its heritage of guiding you towards becoming a GREAT Product Owner from the Inside Out....
|Title||:||Scrum Product Ownership: Balancing Value from the Inside Out|
|Publisher||:||RGCG, LLC Auflage 2 2 M rz 2013|
|Number of Pages||:||252 Seiten|
|File Size||:||663 KB|
|Status||:||Available For Download|
|Last checked||:||21 Minutes ago!|
Scrum Product Ownership: Balancing Value from the Inside Out Reviews
Ich war auf der Suche nach etwas Detailwissen für die Rolle des Product Owners und hatte eigentlich keine sinnvolle deutsche Literatur zu dem Thema gefunden. Meist gab es nur das allgemeine BlaBla zu SCRUM und POs.Dieses Buch steigt schon etwas tiefer in die Materie ein und bietet einem auch ein paar Hilfen für den PO. Wenn man jedoch etwas tiefer in die Materie einsteigen will, z.B. etwas mehr über Kennzahlen in Scrum-Projekten wissen will, bleibt es doch recht oberflächlich. In diesem Beispiel das Übliche BlaBla zu Burndowncharts.Naja...
Bob Galen’s “Scrum Product Ownership” is one of the best, if not the best book that focuses on the role of the Product Owner. It’s comprehensive, educational, and does a wonderful job showing the importance and challenges of the Product Owner role in Scum.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.Quotes:“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)
As a new product owner with a long background in development as well as domain expertise for my product, I had high hopes for this. And it's delivered somewhat, giving me a decent overview of the requirements and tasks of the role. But it's extremely poorly edited, both for simple copy errors (misspellings, grammar, etc.) and for flow. It could benefit from a new edition that fixes these core problems and perhaps expresses the ideas more concisely.
My project recently adopted Scrum practises and the Product Owner role; however, beyond a one-day introduction to the Agile methodology and aggressive self-study, we didn't have a solid foundation on Scrum or Agile. I am assuming the Product Owner role in a surrogate context since our project is for an external client that has no Agile or Scrum background, but is keen to follow our lead. As a result, I was somewhat anxious about being effective in this role. I have been following Bob's blogs and articles for quite some time and upon seeing this book, I did not hesitate for a second to purchase it because I have always found his advice to be practical and logical and deep. I am incredibly grateful that I did because it gave me both the "big picture" and practical guidance on being an effective PO that I was desperately seeking. My book now has about 30 post-it tabs to mark pages that I consider key gems and at one point I was marking every other page and came to realize I simply need to read the book several times to help keep everything in memory. Ultimately one needs to be on a project and live through the experiences and specific team nuances to determine how to adopt your Scrum practices most effectively, but this book was invaluable in setting the stage for me and is continually used as a reference when I run into a "practice" issue and think, "what would Bob do"? I also really appreciated the real-world examples provided throughout the book since they provide guidance from a different, and again very practical, perspective.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.
The book gives me a true inside the "product owner" role. The author focuses on the "Ownership", on the building product. He writes based on the real experience. A practical guide rather than boring definition stuff.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.
Overall a pretty good book with a lot of advice to try out and experiment with. There are however a couple practices that are not in line with the Scrum Guide (Sprint(s) Zero, Hardening Sprint(s), canceling planning, canceling the entire sprint just because the dev team is struggling, etc) and the author is not equally consistent in emphasizing that.