Requirements Engineering for Agile Product Owners: Hunting value with structured conversations

Hunting value through conversations. This is a skill that helps Product Owners when working with stakeholders, analysts and requirements engineers. Start with identifying your project partners, and use the 7 Product Dimensions (user, interface, activities, data, control, environment and quality attributes) to uncover correct requirements for your product. Understand how you can use it to focus on value, deliver value and optimise value.

Unfortunately all too often, many Product Owners do much of their work alone. We want the participants to experience the power of the conversation structured to hunt value through a specifically designed dojo, and we want to create better awareness of good requirements engineering practices. This session is intended to help Product Owners and Business Analysts create better requirements and to help them have richer and more powerful conversations. The session is based on the work of Ellen Gottesdiener and Mary Gorman’s “Discover to Deliver” as well as the work of James Shore and Diana Larsen’s Agile Fluency Model.

 
 

Outline/structure of the Session

Learn about 7 Product Dimensions and the how to engineer better requirements through structured conversations.

 Hunting value through conversations. This is a skill that helps Product Owners when working with stakeholders, analysts and requirements engineers. Start with identifying your project partners, and use the 7 Product Dimensions (user, interface, activities, data, control, environment and quality attributes) to uncover correct requirements for your product. Understand how you can use it to focus on value, deliver value and optimise value.

Unfortunately all too often, many Product Owners do much of their work alone. We want the participants to experience the power of the conversation structured to hunt value through a specifically designed dojo, and we want to create better awareness of good requirements engineering practices. This session is intended to help Product Owners and Business Analysts create better requirements and to help them have richer and more powerful conversations. The session is based on the work of Ellen Gottesdiener and Mary Gorman’s “Discover to Deliver” as well as the work of James Shore and Diana Larsen’s Agile Fluency Model.

The session will be delivered in a format of an interactive workshop.
PART ONE: 7 PRODUCT DIMENSIONS (45min)


CONNECTION 1: Pop-up Question–What motivates your product partners (business partners, customer partners, technology partners) when they review and use your product.
CONCEPT 1: Quick teach introducing the 7 product dimensions (user, interface, activities, data, control, environment, quality attributes). Explain (very briefly) the highlights of the Agile Fluency Model (focus on value, deliver value, optimise value) and explain how the 7 dimensions are seen at different angles depending on a team’s fluency/proficiency.
CONCRETE PRACTICE 1: Work with the 7 product dimensions and the Agile Fluency Model to identify elements of a structured conversation about value (this is a guided exercise).
CONCLUSION 1: Relate the 7 dimensions to your product (quick writing exercise)

PART TWO: VALUE HUNTING CONVERSATIONS (45min)

CONNECTION 2: Explore (generate ideas for) a backlog for your (real) product
CONCEPT 2: Quick teach, practical elements of requirements engineering conversations related back to the 7 dimensions.
CONCRETE PRACTICE 2: 3 person dojos (and feedback rounds), to practice value hunting conversations with coach, product owner and observer
CLOSING 2: How will you start this conversation back home?

Learning Outcome

Learning Outcomes:

1. Identify and analyse 7 product dimensions for doing full Agile requirements engineering.

2. Explore a new skill for creating structured conversations about Agile requirements engineering.

3. Practice structured conversations in a conversational dojo.

Target Audience

Product Owners, Requirements Engineers, Analysts, Scrum Masters, Coaches

Requirements

Rounds seating, a projector and fllpcharts are all that's required.

Participants who bring backlog which they can share publicly from one of their own products will be able to work with it, and gain the most benefit.  However, we will also provide a backlog from a case study to participants who can't share their own backlog.

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Fincy Yousuff
    By Fincy Yousuff  ~  1 year ago
    reply Reply

    Hello Steve and Pavel,

    A very interesting topic and well structured too. 

    I see that you had presented this topic at "OOP 2016" too. Do you happen to have a short video of the same? This is just to take a look at your presentation style. Any other talk's video will also do.

    Also, as you are planning to help participants understand the concept through an interactive workshop, could you please change the type of session to "Workshop". I feel that Workshops would be generally preferred by audience rather than a 90 minute talk :) What do you think?

    Hoping to hear from you soon!

    Thanks and Regards,

    Fincy

    • Steve Holyer
      By Steve Holyer  ~  1 year ago
      reply Reply

      Hi Fincy,


      Thanks for your message and your helpful comments.

      I will be presenting this talk (solo) at OOP 2016 in February next year. So there's no video yet.

      Pavel and I presented this session together two weeks ago for the first time, but alas there was no video.

      I posted clips of me delivering the keynote address at last year's Scrum Gathering South Africa with the proposal. 

      You will find video of Pavel making his excellent Agile Economics talk at the Agile Africa conference this year here (I believe he will also be delivering this talk at Agile India): https://www.youtube.com/watch?v=cteAb9Ap7_4

      And there is a video of me presenting another talk (Real Options) here: https://www.youtube.com/watch?v=LYGE-JYZZHY

      Best Regards,
      Steve

       

  • Anish Cheriyan
    By Anish Cheriyan  ~  1 year ago
    reply Reply

    Hi Steve and Pavel,

    Thanks for the topic submission.  The perspective of doing requirement engineering 7 product dimensions (user, interface, activities, data, control, environment, quality attributes) is interesting.

    Please request you to add the slides. Curious to know if you have already used these methods in your projects, you have been associated with. Are you planning to provide some cases.

     

    Thanks and Regards

    Anish

    • Steve Holyer
      By Steve Holyer  ~  1 year ago
      reply Reply

      Hi Anish,


      I use this both in my training classes and in my projects. I can provide examples. 

      Pavel and I have run the first presentation of this topic two weeks ago at Scrum Gathering South Africa.  I can provide those slides, but they will go through several revisions and several more test runs before Agile India.

      Best Regards,

      Steve