The First Guide to Scrum-Based Agile Product Management In Agile Product Management with Scrum, leading Scrum consultant Roman Pichler uses real-world examples to demonstrate how product owners can create successful products with Scrum. He describes a broad range of agile product management practices, including making agile product discovery work, taking advantage of emergent requirements, creating the minimal marketable product, leveraging early customer feedback, and working closely with the development team. Benefitting from Pichler's extensive experience, you'll learn how Scrum product ownership differs from traditional product management and how to avoid and overcome the common challenges that Scrum product owners face. Coverage includes Understanding the product owner's role: what product owners do, how they do it, and the surprising implications Envisioning the product: creating a compelling product vision to galvanize and guide the team and stakeholders Grooming the product backlog: managing the product backlog effectively even for the most complex products Planning the release: bringing clarity to scheduling, budgeting, and functionality decisions Collaborating in sprint meetings: understanding the product owner's role in sprint meetings, including the dos and don'ts Transitioning into product ownership: succeeding as a product owner and establishing the role in the enterprise This book is an indispensable resource for anyone who works as a product owner, or expects to do so, as well as executives and coaches interested in establishing agile product management.
This book is a disaster. It has nothing related to Product Management but instead talks almost exclusively of a new role called Product Owner. Reading above this books obvious crowbarring of yet another business role into the purity of Agile (a common corporate failing nowadays), it’s a poor attempt at trying to define a single product-focussed combination of Team Lead & Project Manager. If my years in business have taught me anything; finding such a superhuman that combines several competing disciplines and personality traits is a tough and extremely rare find. Define away, but good luck ever finding someone who’d be great at this conjured up role. I love Agile development and have evangelized on the topic for many years. The Agile Manifesto is a pure and ideal set of directives that play exceptionally well into the role of development and business people in the creation loop. This awful book is the most evidence I’ve read of an ideology well implemented that’s turned into a buzzword that is now being used as a hammer for any ‘problem’ (even some problems that don’t exist) in business.
Even after carefully studying the Product Owner role from many angles, this book taught me a lot about this role. For example, among many other things, Roman Pichler did a great job describing many relationships, and of course, focused on the many relationships that the Product Owner has, both with the development teams, the rest of the organization (management, departments, etc.) and, the customers. To accomplish this, Roman describes the organizational contexts so that a Product Owner can establish the right relationships and address the critical aspects of the role effectively. If one wants to extend critical PO skills beyond this book, consider Jeff Patton’s User Story Mapping and Eric Reis’s The Lean Startup. Those will provide an amazingly great core set of knowledge. To extend to larger projects with a true scrum framework, consider the coming book by Craig Larman and Bas Vodde, Large-Scale Scrum: More with LeSS (if you want a large number of details, consider their book Scaling Lean and Agile Development and it’s companion. These are two of the best books I've seen on scrum and in particular, scaling effectively).
As a new Product Owner transitioning into the role, this book was recommended to me as an intro to PO in Agile. I read it when I first started out, and absorbed probably about 15-20% of the content. A lot of it is quite high-level and assumes familiarity with Agile development and product management. I like that the book focuses on the PO role pretty much exclusively, but I'm in the process of re-reading it to see if there are more insights that I can apply to my role, now that I've been working as a PO for several months. I feel like this is a good resource book, but for me I will likely need to revisit it as I grow with this role.
If you are a new product owner or would like to quickly get an idea what product owner role is all about - this is the book for you. This also means that if you already know a lot about agile/scrum and product ownership, this might be too basic for you.
For me, this book is a good and quick refresher. Recommended!
A book not only for Product Owners, even though it focuses on their role. Readers with other roles in an organisation will also gain valuable insights in the responsibilities and tools a PO uses. Meetings and Artefacts are briefly explained and antipatterns shown.
The book is no introduction to agile, a base knowledge about Scrum is absolutely required.
کتاب بسیار خوبیه برای کسایی که نقش مالک محصول رو دارند. خطاهای سادهای که انجام میدیم ولی تاثیرات بزرگ و تلخی دارند. نقطه ضعف کتاب استفاده نکردن از تصویر بود به نظرم. بهتر بود در جاهایی مثل Release Burndown بیشتر انرژی میگذاشت و علاوه بر توضیحات به خواننده کمک میکرد که بهتر متوجه بشه. پیشنهاد میکنم در زمان خوندن کتاب کلمات کلیدی رو یادداشت کنید و برای درک بهتر خودتون هم جستجو کنید.
Nice overview of Agile Product Management, maybe a bit too shallow, high level and simplistic. It is a really good source of information for someone who is interested in Agile Product Management. I expected a bit more in-depth overview.
This book is meant for product owners who are new into this field. The book will explain various aspects of the product owner role without going to deep into various techniques. Readers should have knowledge of scrum before reading this book to get the most out of it. I would only recommend this book to people who are new to the role of product owner and to those who want to know how this role should be filled in.
какая-то максимально никчемная книга, сорри. всё описано чрезвычайно поверхностно, в духе "надо делать как надо, а как не надо делать не надо", ноль конкретики, ноль примеров, и за это издательство миф берет 750 рублей, семьсот пятьдесят, мать их рублей, я хуею. стыдно должно быть за такую дрянь деньги просить.
It is a book worth reading, even if you are already working as a Product Owner
Roman starts his book describing the characteristics of a Product Owner, the Product Owner interactions with the team, ScrumMaster and stakeholders, writes some words about scaling the role in large project environments, and concludes the first chapter noting common mistakes taken when staffing the Product Owner role. Next he writes in detail about the first and essential task a Product Owner has to do - creating the product vision. Then he describes the main task of a Product Owner - working with the product backlog. After writing about release planning topics, Roman explains the collaboration of the Product Owner in the sprint events. He closes with some useful hints how to become a great Product Owner.
I already have worked as a Product Owner the time reading this book. So most of the provided information was already known to me. But it was still worth reading the book, even that I was familiar with most of the information given. Indeed, there still were some eye-openers.
It is a book worth reading, even if you are already working as a Product Owner. For those who are new to the role, I recommend reading the book.
This book is the latest and greatest intro to the role of the “Product owner” as the product manager is called in the most common of agile methods, Scrum. Written by one of the leading Scrum consultants out there this book gives you a good sense of what the product owner role is all about and all the tools you need to do the role. I use 'KANBAN' on all of my collabration software from Asana and Trello. Strongly recommend this improve user experience, working with programmers, new users and focusing attention on building the product while stripping features that will likely not help the product
Excellent book that doesn't just teach how to execute the Product Owner role efficiently, ensuring products being created are actually loved by the customer and users, but it also explains what's required to get good at it, how to go about it and what an ideal product owner candidate looks like. And the content can be easily understood by just about anyone.
I must say, there's really not that much information out there when it comes to Agile Product Management as I initially expected. I mean, there is some, but I quickly ruled out most of what I found anyway on reasons related more to authors advertising their own products more than really putting valuable info out there.
The book however is not one of those. I mean, it advertises the author but by proving what he actually knows. Although there's a whole lot that I suspect could be said about Product Management, the book sums it up in a nice way.
I really like the fact that it lists common mistakes from the field. I think I learned more from them than the actual theory, as it should be the case (duuh!)
I always recommend people to read more than one book on any topic and this is definitely also the case. And among those books that I recommend for a Product Manager or Product Owner, this should also have its own place.
Very good basic book, most likely too basic for intermediate-level professionals, however it does help brush up on some fundamentals aspects of the product management role. Got me to rethink the best way to conduct sprint reviews, and provided personally interesting improvement ideas on various other initiatives. I love Roman Pichler for his down-to-earth, easy to follow style, the author provides well-structured, digestible chunks of information that would help any aspiring or first-time PO/PMs.
Though author has done a fabulous job detailing the various facets of product management in an agile context, he's only scratched the surface of many of the underlying concepts. As someone who already works in a Scrum environment, I was expecting a more comprehensive coverage on applying agile techniques using scrum. That said, if you are somone transitioning into scrum from old product management practices such as waterfall, you will find this book useful.
Krótkie ale dość treściwe spojrzenie na Scrum oczami Product Ownera. Widzę 2 zastosowania tej ksiażki - dla początkujących jako wprowadzenie przed zagłębieniem się w poszczególne tematy albo dla odświeżenia od czasu do czasu żeby sobie przypomnieć prawdy tak oczywiste że aż o nich zapominamy w codziennej bieżączce.
Angielski -prosty. Czas czytania: 5:30 ale w pracy na open space więc w domowym zaciszu pewnie trzeba odjąć godzinę.
A great book whether you are just starting out or have years of experience in POs role. It gives tips and describes the activities the role performs. However, it doesn't go into detail about certain things.
It provides solid advice to Product Managers, or anybody else, who are transitioning to the Product Owner role and the difference they can expect to see using Scrum. I view it as the supplemental reference because it doesn't sufficiently cover all processes.
Unique guidance composing scrum principles and product management in a lean approach. I loved the common mistakes section of each chapter which emphasizes antipatterns or myths. I totally recommend the new product owners/managers reading this book before stepping into their first product. And remember to follow Roman Pichler's official site where he is serving precise articles and original templates.
A great resource for everyone eager to understand the role of product owner either for aiming at exercising it themselves or for providing support to their colleagues in triumphing in this role for the benefit of the organization. What I miss due to the small format are more practical situations highlighting the qualities of this role, which are covered in the common mistakes that remain valuable even if not that much detailed.
This book is focused to the Product Owner role in a Scrum framework. It can act as a survival guide for Product Owners in their first steps and flag some of the most common pitfalls. Given it can be read in a couple of hours, I highly recommend it to everyone who is still uncomfortably with their new role.
The title sets a rather high benchmark which the book fails to achieve. The book is specifically targeted towards Product Owners (that new role in Agile, which everyone aspires to be) and does a good job at delineating that aspect only. Liked the common pitfalls at the end of each chapter. It's a good read to shape you to take on the role.
Good for beginner POs to get a big picture of what the role is about. It gives tips and describes the activities the role performs. However, it doesn't go into detail about certain things that I wanted to know more about, like how to create a product backlog, and what grooming the backlog means.
I think this book is great however it refers to many other books such as User stories applied and Agile estimating and planning by Mike Cohn, it doesn’t dive into much detail in any topic but provides pointers, if you buy this book by its own you might not get much value but still is a short and good book.
Clasic and imperdible book about product owner rol
This is one of the classical and impressible book for all scrum master, product owner or agile coach that want to learn more about product owner role. Roman Pitcher is without a dubt one of the world references in Agile Product Development