- File Size: 10237 KB
- Print Length: 276 pages
- Publisher: EBG Consulting, Inc.; 1 edition (January 6, 2014)
- Publication Date: January 6, 2014
- Sold by: Amazon Digital Services LLC
- Language: English
- ASIN: B00HQHZD8E
- Text-to-Speech: Enabled
- Word Wise: Not Enabled
- Lending: Not Enabled
- Amazon Best Sellers Rank: #679,722 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
Discover To Deliver: Agile Product Planning and Analysis Kindle Edition
See the Best Books of the Month
Want to know our Editors' picks for the best books of the month? Browse Best Books of the Month, featuring our favorite new books in more than a dozen categories.
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.
Customers who bought this item also bought
Would you like to tell us about a lower price?
Top customer reviews
This book, therefore, provides some extremely valuable advice on this extremely important topic. The authors describe how you need to approach the process of launching and sustaining a project or product as an iterative process of discovery and adjustment, not a non-stop moon mission, whether it turns out that going to the moon is a good idea or not. The book is filled with examples and insights that show that the authors have successfully traveled down this windy, unpredictable road themselves, and with their clients. And they have a lot of tactical advice on how to make the journey more successfully. Their discussion about how to adjust, as you go, your approach to creating a "structured conversation" is especially important.
What they don’t get to really is the hard stuff. Their approach of the 7 product areas is OK to help guide the conversation (I personally think it mixes problem space & solution space and punts with “Quality Attribute”, but that is me) but the decisions are made outside of the conversation. All the conversation appears to do is report out the work done off screen. Which persona is more important to make happy first? Well, that decision was done by work outside of the conversation. What function should we support more fully, well that analysis was done outside of the conversation. It appears to me that this book is aiming only at the transfer of decisions from the business to the development team.
Now that is a fine and important thing to do. However, it kind of punts on the “discover” part of the title. I guess if you read the title as, “After I have discovered it, here is how I get it to be delivered” works a bit better. Even then, the planning aspect of net present value, skill availability, competing portfolio stuff isn’t part of the plan.
That said, Gottesdiener and Gorman are very good at having that transfer conversation and this book is a good helping people remember the things that are easy to forget when a shinny new feature is beckoning to be built.
Having identified "requirements" as a problem area in retrospective after retrospective, we tried to think of experiments to better understand stakeholders' desires before we started coding. My own teammates started thinking, "Maybe what we need is a business analyst?" We learned about techniques such as Story Mapping, and realized there was a range of skills around understanding what our customers need in their software product. We started learning from Ellen's and Mary's work on Agile BA. We formed a Requirements Community of Practice to experiment with the 7 product dimensions and structured conversations.
And now we have Discover to Deliver as a resource! The book lays out useful techniques such as structured conversations, and explores key problem areas such as data. The authors illustrate many useful practices via real-world case studies and examples. Graphics help convey the concepts behind the many useful ideas.
This book works for Agile practitioners in a variety of roles, including testers, BAs, programmers, and managers. It presents information in different ways, so that readers with different learning styles can understand. Tools with which readers can experiment are included, such as facilitated workshops and product vision. If you're a BA on an agile team, read this book today. If you work on an agile team that lacks a BA, or has a BA, read this book today. Better yet, have your entire team read this book together, and start experimenting with Agile product planning and analysis practices that will help you delight your customers.
Most recent customer reviews
* The conversational style makes it easy to read.
* The structure allows you to locate the information you need...Read more