Explore, Evaluate, Confirm Product Needs with Structured Conversations
•
4 likes•1,507 views
Collaborate to discover and deliver valued products using structured conversations: Your agile team needs a holistic understanding of the most valuable product needs to deliver—just-in-time and just enough. Ellen shares how product partners—customers, business and technology stakeholders—engage in structured conversations to explore, evaluate and confirm product needs. Hear about essential practices you can use in your daily work that blend value‐based decision‐making, a testing mindset, and disciplined analysis. You will see how front‐loading verification and validation when discovering product needs fuels collaboration, saves development time and is instrumental to delivering a high quality product. [Presented in NYC, 01-October-2012 at Skillsmatter's the Agile BDD Exchange in New York City]
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Explore, Evaluate, Confirm Product Needs with Structured Conversations
Similar to Explore, Evaluate, Confirm Product Needs with Structured Conversations (20)
Recently uploaded
Recently uploaded (20)
Explore, Evaluate, Confirm Product Needs with Structured Conversations
- 1. Explore, Evaluate & Confirm Product Needs with Structured Conversations Copyright © 2012 EBG Consulting, Inc. Ellen Gottesdiener www.ebgconsulting.com www.DiscoverToDeliver.com © EBG Consulting, 2012 www.ebgconsulting.com 1
- 2. 2 Explore, Evaluate & Confirm Product Needs with Structured Conversations Copyright © 2012 EBG Consulting, Inc. All rights reserved. We at EBG Consulting are pleased to share the practices and experiences described in this presentation with you. This presentation is for the viewer’s personal use. No copies, in part or in whole, including but not limited to, hard copy, print, photocopy or any electronic media, may be made or used without express written permission of EBG Consulting, Inc. Thank you for honoring the copyright. © EBG Consulting, 2012 www.ebgconsulting.com 2
- 3. Ellen Gottesdiener Founder & Principal Consultant, EBG Consulting Facilitator, trainer, mentor, agile coach, conf. advisor Certified Professional Facilitator, Certified Scrum Master IIBA® BABOK®: expert reviewer; contributor to agile extension Author: articles, blog, books Twitter: @ellengott, #bddxny Blog: ebgconsulting.com/blog eNewsletter: Success with Requirements © EBG Consulting, 2012 www.ebgconsulting.com 3
- 4. structured concepts conversation holistic product wrap needs © EBG Consulting, 2012 www.ebgconsulting.com 4
- 5. concepts © EBG Consulting, 2012 www.ebgconsulting.com 5
- 6. © EBG Consulting, 2012 www.ebgconsulting.com 6
- 7. product © EBG Consulting, 2012 www.ebgconsulting.com 7
- 8. ends and means © EBG Consulting, 2012 www.ebgconsulting.com 8
- 9. partners © EBG Consulting, 2012 www.ebgconsulting.com 9
- 10. © EBG Consulting, 2012 www.ebgconsulting.com 10
- 11. value decisions benefits costs risks dependencies © EBG Consulting, 2012 www.ebgconsulting.com 11
- 12. vision © EBG Consulting, 2012 www.ebgconsulting.com 12
- 13. plan © EBG Consulting, 2012 www.ebgconsulting.com 13
- 14. views © EBG Consulting, 2012 www.ebgconsulting.com 14
- 15. views want need requirement © EBG Consulting, 2012 www.ebgconsulting.com 15
- 16. holistic product needs © EBG Consulting, 2012 www.ebgconsulting.com 16
- 17. 7 product dimensions © EBG Consulting, 2012 www.ebgconsulting.com 17
- 18. product options Alternatives, choices, possibilities… to achieve a goal or solve a problem for its stakeholders. Adapted from: Gottesdiener, Software Requirements Memory Jogger © EBG Consulting, 2012 www.ebgconsulting.com 18
- 19. user Users interact with the product © EBG Consulting, 2012 www.ebgconsulting.com 19
- 20. interface The product interfaces to users, systems, and devices © EBG Consulting, 2012 www.ebgconsulting.com 20
- 21. action The product provides capabilities for users © EBG Consulting, 2012 www.ebgconsulting.com 21
- 22. data The product includes a repository of data and useful information © EBG Consulting, 2012 www.ebgconsulting.com 22
- 23. control The product enforces constraints © EBG Consulting, 2012 www.ebgconsulting.com 23
- 24. environment The product conforms to physical properties and technology platforms © EBG Consulting, 2012 www.ebgconsulting.com 24
- 25. quality attribute The product has certain properties that qualify its operation and development © EBG Consulting, 2012 www.ebgconsulting.com 25
- 26. beyond stories © EBG Consulting, 2012 www.ebgconsulting.com 26
- 27. structured conversation © EBG Consulting, 2012 www.ebgconsulting.com 27
- 28. © EBG Consulting, 2012 www.ebgconsulting.com 28
- 29. shared understanding of needs © EBG Consulting, 2012 www.ebgconsulting.com 29
- 30. “The most efficient and effective method of conveying info to and within the development team is face-to-face conversation…” The Agile Manifesto © EBG Consulting, 2012 www.ebgconsulting.com 30
- 31. product backlog © EBG Consulting, 2012 www.ebgconsulting.com 31
- 32. structured conversation © EBG Consulting, 2012 www.ebgconsulting.com 32
- 33. explore each D © EBG Consulting, 2012 www.ebgconsulting.com 33
- 34. evaluate each D © EBG Consulting, 2012 www.ebgconsulting.com 34
- 35. assemble options © EBG Consulting, 2012 www.ebgconsulting.com 35
- 36. confirm to learn © EBG Consulting, 2012 www.ebgconsulting.com 36
- 37. confirm representation acceptance criteria feature, scenarios epic MMF, acceptance story criteria list story, Given-When-Then, scenaris data exampls, planguage © EBG Consulting, 2012 www.ebgconsulting.com 37
- 38. acceptance test context of system what will be tested result © EBG Consulting, 2012 www.ebgconsulting.com 38
- 39. explore validate execute verify Adapted from: Agile Alliance Functional Testing Tools Open Space Workshop 2007 © EBG Consulting, 2012 www.ebgconsulting.com 39
- 40. collapse the “v” © EBG Consulting, 2012 www.ebgconsulting.com 40
- 41. define validate validate verify © EBG Consulting, 2012 www.ebgconsulting.com 41
- 42. wrap © EBG Consulting, 2012 www.ebgconsulting.com 42
- 43. Discover to Deliver™ The product partners continually collaborate to the evolving product. 7 Product Dimensions. The partners options for the They identify and cohesive chunks of high-value options and allocate them to plans at all views. © EBG Consulting, 2012 www.DiscoverToDeliver.com Copyright © 2012 by EBG Consulting Inc. www.ebgconsulting.com 43
- 44. www.DiscoverToDeliver.com Coupon Code: BDD01LN 25% off book thru 12 Oct 2012 © EBG Consulting, 2012 www.ebgconsulting.com 44
- 45. EBG’s agile services New Training Solutions Discovering Product Needs for Agile Delivery and Discover to Deliver: Agile Analysis Practices www. ebgconsulting.com - info@ebgconsulting.com © EBG Consulting, 2012 www.ebgconsulting.com 45
- 46. email ellen@ebgconsulting.com twitter ellengott more agile ebgconsulting.com/agile.pdf about EBG www.ebgconsulting.com d2d www.DiscoverToDeliver.com © EBG Consulting, 2012 www.ebgconsulting.com 46
Editor's Notes
- This slide is Mandatory. Do not delete. Introduce the Speaker(s) [#] [Information]
- Vision, goals, objectives (SMART)
- xx
- … “ fair return or equivalent in goods, services, or money for something exchanged.”* (noun) Determine or assign value; estimate the value of; to hold dear (verb) Perceived benefit, such that buyers will exchange time, money or some resources, and incur some cost (money, time, or other) ENDS not means Value: perceived benefit Stakeholders: beneficiaries of value Note: different stakeholders have different value Requirements (features): functionality and quality attributes of a product Business value is the desired ends Requirements are the means MULIPTLE VOICES fro VALUE Business (sponsor paying for product development) Customer: Buyer (chooser and user) Subcategory: Influencers Technology: Builder and Supporter
- Vision, goals, objectives (SMART)
- Interwoven activities of discover and delivery
- communicate directly - no surrogates knowledgeable, decision makers
- You define acceptance criteria to verify and validate candidate solution. The structured conversation isn’t over until the partners confirm their shared expectations for the candidate solution. This confirmation enhances the partners’ understanding of the product options. You use acceptance criteria (also called conditions of satisfaction or doneness criteria ) to verify and validate the candidate solution. Acceptance criteria provide concrete, unambiguous, measureable means to confirm that the candidate solution’s outcomes are correct. Acceptance criteria guide development and testing. You define acceptance criteria during discovery as a way to elicit and clarify product needs. This same acceptance criteria is used during delivery to guide development and testing to verify you are correctly building the candidate solution. The candidate solution is a speculation or investment proposal you believe will achieve business value. Therefore, you continually validate its actual results against business objectives. During discovery, actual results from prior deliveries are considered as you evaluate product options. During delivery, demonstrations and user acceptance testing validate your candidate solution is ready for release.
- Requirements are explore via examples Examples validate tests Tests execute examples Tests verify requirements
- Going down left side: vision, goals, user reqs, SW reqs, system design At bottom: build code. Going up rt side – verify – unit testing, integration, system testing, not till top – UAT. Gee would will take a long time to get to UAT click As we elicit, validate. Think like tester, how would we test this little piece of req. really different, really powerful. Gets to core of tamped down req
- Confirm to Learn The structured conversation isn’t over until the partners confirm their shared expectations for the candidate solution. This confirmation enhances the partners’ understanding of the product options. You use acceptance criteria (also called conditions of satisfaction or doneness criteria ) to verify and validate the candidate solution. Acceptance criteria provide concrete, unambiguous, measureable means to confirm that the candidate solution’s outcomes are correct. Acceptance criteria guide development and testing. You define acceptance criteria during discovery as a way to elicit and clarify product needs. This same acceptance criteria is used during delivery to guide development and testing to verify you are correctly building the candidate solution. The candidate solution is a speculation or investment proposal you believe will achieve business value. Therefore, you continually validate its actual results against business objectives. During discovery, actual results from prior deliveries are considered as you evaluate product options. During delivery, demonstrations and user acceptance testing validate your candidate solution is ready for release.