Experience the power of structured conversation for hunting value. Product Owners develop this skill to work with stakeholders, analysts and requirements engineers (when the project has them) to hunt – and capture – the value that their product can deliver. Identify your project partners, and use 7 Product Dimensions to uncover requirements for your project. Understand how you can use that to focus on value, deliver value and optimise value. With brief instructional moments, this session provides a dojo structure for you to develop your skill.
Target Audience: Product owners, analysts, requirements engineers
Prerequisites: Basic agile knowledge is recommended but not required
You will learn:
- Identify 7 product dimensions for doing full Agile requirements engineering.
- Explore a new skill for creating structured conversations about Agile Requirements Engineering.
- Practice structured conversations in a conversational dojo.
I will link the work of Ellen Gottesdiener and Mary Gorman in “Discover to Deliver” (they presented at OOP2013) and the 7 Product Dimensions (user, interface, activities, data, control, environment, quality Attributes) to the work of James Shore and Diana Larsen on the Agile Fluency Model (focus on value, deliver value, optimise value) to introduce new tools to product owners for facilitating better conversations about Agile Requirements and their priorities.
This session is intended to help product owners (POs) do better requirements engineering when they don't have the help of a requirements engineering team, and also to help POs and requirements engineers have richer and more useful conversations when requirements engineering is available on a project.
A significant part of this session will be a dojo on developing the skills required to conduct value hunting structured conversations.
In a recent trial run (as part of a day long PO workshop) participants were amazed at the dojo experience and what structured conversations offered. Unfortunately all too often, many POs do much of their work alone (certainly not how that is intended to work). I want the participants to experience the power of the conversation specifically structured to hunt value, and we want to create better awareness of good requirements engineering practice and how they are used to collaborate fully with people.