Prioritizing user stories: using value to users as a key criteria

Product development in agile is always at risk of favouring velocity and developer's skills.

Favouring velocity means that when it's time to select stories, the team will elect to do many short stories to keep velocity on the rise, or stable.

Favouring skills mean that easy implementation may be selected, or sometimes tricky solutions which will give the developper the satisfaction of solving a difficult problem.

The outcome of the story's execution and value to users is an important criteria, and I'd like to introduce you in this session to a technique that helps prioritize against two sets of criteria: technical difficulty and value to users.

Using Personas, a tool from product design which I will explain, and a simple grid, this technique makes prioritization incredibly easy - which then enables the team to focus on getting stories done, rather than figuring out which stories.

 
1 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Introduction: why prioritize on outcomes

Part 1: Introducing user personas and when and how to use them

This section will introduce user personas, with a brief overview of their value, their elaboration and where a team can source them if they don't have them. You will learn how personas are made, take a quick spin at crafting an ad-hoc persona and understanding first-hand the complexity of this exercise. I will conclude this section with an overview of their usefulness and relevancy at the various stages of product design and development.

I hold personas critical to developing user-valuable products, and will demonstrate why so you can walk out with a greater appreciation of their value to a development team in particular. 

Part 2: The prioritization grid and exercise

Using the freshly learned value and purpose of personas, we will look at applying them to prioritizing stories. This prioritization require technical evaluation along with an estimate of user value, so the product owner will have to conduct this exercise with his team, shifting part of the work from sprint planning to prioritization meeting. I will introduce the grid to use, the roles needed to conduct the prioritisation, and the process in order to enable you to replicate this with your team. A variant of the classic Business Prioritization grid, this grid embeds value to users as a key criteria for presentation, which requires an understanding of users hence the first part dedicated to personas.

Conclusion: what happens when this process is applied

Q&A

Learning Outcome

Participants will be equipped with a new way of prioritizing stories, and the method to do so as well as a solid framework of reasoning to encourage adoption and tips and tools to help practicing this method.

Using this approach, prioritizing becomes easier, and products benefit from aditional clarity by shifting the discussion to one of value to end users.

Target Audience

product owners, agile coaches, scrum masters

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Joel Tosi
    By Joel Tosi  ~  2 years ago
    reply Reply

    Hi Sophie,

        Could you please help me understand what the two exercises of the workshop are?  Is the first creating personas and the second is prioritizing based on personas?

    Best,

    Joel

    • Sophie Freiermuth
      By Sophie Freiermuth  ~  2 years ago
      reply Reply

      Hi Joel

      I've updated the description to answer your question. 

      Thanks,

      Sophie

  • Jerry Rajamoney
    By Jerry Rajamoney  ~  2 years ago
    reply Reply

    Hi,

    Thanks for the topic. The "Part 1: Introducing user personas to the process " - Is this is something Jeff Pattern used to do? Are you going to refer the same?

    Also, "The prioritization grid and exercise" -> Can you please provide some more details or an external link to have a look at?

    Thanks

    • Sophie Freiermuth
      By Sophie Freiermuth  ~  2 years ago
      reply Reply

      Hi Jerry

      Personas are a classic design tool that Jeff indeed has spoken a lot about. I still find them underused, misunderstood and unappreciated though, and endeavour myself to inform on their value as they are very helpful to the design process.

      In regards to your question about the grid, that's the entire point of the presentation. I've updated the copy to detail further this.

      Thanks for your input,

      Sophie

       


  • Liked ShriKant Vashishtha
    keyboard_arrow_down

    ShriKant Vashishtha - Distributed Agile Patterns

    60 mins
    Talk
    Intermediate

    Way back in 2008, when I started working in Agile, there was enough material available on Scrum and. However when it came to distributed aspect of it, people were still struggling with it. Based on working for years in this fashion, I realised that communication, trust, transparency and innovation are the core fundamental values towards successful distributed Agile implementation.

    In other words, as most of the problems were caused by softer aspects of skills (misunderstanding, miscommunication, non-availability of people, mistrust etc), humanizing the distributed team experience looked like the key for successful distributed Agile implementation.

    Based on working with distributed teams over the years, we discovered some distributed Agile patterns. Some of them got blogged from time to time. Those already available in form of blogs are as follows:

    The session is to share the these patterns and more (when to go for distributed Agile and when not etc)

  • 45 mins
    Talk
    Advanced

    Good engineering practices and fail-fast, iterative, low-ceremony processes help achieve team level agility. They are necessary but not sufficient to scale agility across the IT organization. In this talk, I'll address what else is needed and why. In particular, I'll address:

    1. Why plan-driven IT projects are a bad idea why we need value-driven projects instead
    2. Why a matrix org is a bad idea for IT and why we need cross-functional teams instead
    3. Why IT budgeting needs to change from being project-based to being team-capacity based
  • Liked Pooja Uppalapati
    keyboard_arrow_down

    Pooja Uppalapati / Ravindra Chebiyam - Scaling Agile in a Mainframe Product Development Organization

    20 mins
    Experience Report
    Intermediate

    Agile transformation in any organization will go through myriad of challenges that involves people, existing organization culture, technology/domain etc. Instead of seeing these challenges as obstacles, if you view them as opportunities to grow and improve, transformation will be more impactful and long-lasting. If neglected, the very same obstacles would severely damage the motivation and trust of employees.

    In this experience report we would like to walk you through the agile transformation journey in a Mainframe product development enterprise by unraveling the challenges and the remediation steps that has helped us in keeping this journey alive. Specifically we would like to touch upon 

    1. Self-organizing teams
      • Resistance to change
      • Culture shift
    2. HR
      • Lack of role clarity and
      • Effective R&R in agile space
    3. Agile Engineering Practices adopted in Mainframe product development
      • Unit test automation
      • Continuous Integration

    Along the presentation we’ll highlight few anti-patterns and the effects of ignoring them.

  • Sneha Kadam
    Sneha Kadam
    Business Analyst
    ThoughtWorks
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    After revolutionizing the automobile industry, Lean principles have been successfully applied to different knowledge areas including software development. This workshop is intended to master Lean concepts like Waste, Push&Pull systems, systems thinking, Kaizen etc. & practicing cross-functional collaboration, self-organisation and safe-fail experimentation! In this interactive game, the participants will work in a small production lines, experiencing problems and applying Lean practices to overcome them.

  • Liked Vijay Bandaru
    keyboard_arrow_down

    Vijay Bandaru - Lean and Kanban Implementation from Trenches

    Vijay Bandaru
    Vijay Bandaru
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    I was part of a Large Scale Agile transformation in my organization and I was one of the Agile coaches there. As part of transformation we have created LeanOps teams to manage the technical debt, production incidents with a focused concentration. This article covers the following:

     

    - Why the trasnformation required?

    - What are the structural changes implemented?

    - LeanOps inception

    - Lean Ops working Model

    - Challenges with the LeanOps

    - How we addressed those challenges?

    - Goal oriented approach

    - Q & A

  • Liked Michael Harris
    keyboard_arrow_down

    Michael Harris - Agile Competency Development For Enterprises

    45 mins
    Talk
    Intermediate

    For agile to work at scale in enterprises, there needs to be clarity around the hierarchy (or lack of hierarchy) of roles across teams and products to ensure sound governance and, perhaps more importantly, to offer career (and salary!) progression.  This presentation will propose a competency-based approach for the development of skills and competencies of the workforce, and thus creating a sustainable transformation in an enterprise. We will include experiences of implementing those components of the proposed model that have already been tried and tested.  Feedback will be sought from the participants.

  • Liked Alexey Pikulev
    keyboard_arrow_down

    Alexey Pikulev - “Help Me Do It Myself!” Growing a self-organization by using the Montessori Method

    Alexey Pikulev
    Alexey Pikulev
    Unusual Concepts
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    “Help Me Do It Myself!” Montessori is an innovative, child-centered approach to education, developed a century ago by Dr. Maria Montessori who was struck by how avidly the children absorbed knowledge from their surroundings. The goal of the Montessori method is to foster a child’s natural inclination to learn, where Montessori teachers guide rather than instruct, linking each student with activities that meet his interests, needs, and developmental level. But is this method only suitable for children?

    In this talk, I will demonstrate how to apply the Montessori education method in growing self-organized teams. We’ll discuss what Leaders may find useful and how to adapt this methodology in the day to day work of your organization.

  • Shiva Krishnan
    Shiva Krishnan
    Agile Coach
    AgileFaqs
    schedule 2 years ago
    Sold Out!
    45 mins
    Experience Report
    Intermediate

    My journey as an agile coach has been a great learning experience.

    In this session i intend to share some key learnings that contribute to effective coaching.

    I have aggregated my presentation under the following topics:

    • Coaching with Compassion vs coaching for compliance - why it is important to understand the team's needs instead of running the coach's transformation agenda. How do we involve teams in the transformation?
    • The coach’s mindset defines his/ her coaching - Many times coaches are not able to identify team problems due to their own biases. How can a coach be aware of such biases and overcome them?
    • Making your coaching visible - A common failure in transformations is that coaches are unable to make their progress visible. We will look at some interesting techniques to make  coaching progress visible
    • Involving stakeholders -How do we involve stakeholders other that the teams? why is it important?
    • Coach for a coach - Every coach needs a mentor . How do we effectively utilize mentors? what role do they play in a coach's growth?
    • Celebrating success - We often fail to talk about our successes and acknowledge teams. How did we do this in our organization?

    In each topic i will be sharing my experience, learnings and techniques that i used to overcome challenges.