1. External & Quantitative Techniques
    1. The Kano Model
      1. Customers’ Satisfaction with our product’s features depends on the level of Functionality that is provided
        1. from total satisfaction to total dissatisfaction
        2. Investment, Sophistication or Implementation
      2. Features can be classified into four categories
        1. Performance
          1. intuitively
        2. Must-be
          1. expected
        3. Attractive
          1. positive reaction
        4. Indifferent
          1. no difference
      3. You can determine how customers feel about a feature through a questionnaire
        1. how the customers feel if they have the feature
        2. if they did not have the feature.
        3. table: I like it I expect it I am neutral I can tolerate it I dislike it
      4. prioritization: Must-Be > Performance > Attractive > Indifferent
    2. Quality Function Deployment
      1. focus on product features viewed from different angles ( the customer and the company)
        1. decision matrix
          1. house of quality.
      2. Identify customers’ wants and needs
      3. Identify the “Voice of the Customer”
      4. Identify the How’s (The Voice of the Company)
      5. Relationship between “Voice of the Customer” and “Voice of the Company”
      6. Generate Priorities
      7. Examine Priorities
      8. QFD matrix
    3. Outcome-driven Innovation (ODI) framework
      1. people buy products and services to get some job done
      2. build a list of desired outcomes
      3. ask customers to score each outcome
        1. how important it is
        2. the degree to which it is satisfied on a scale of 1 to 10
      4. graph: Importance/Satisfaction
    4. Buy a Feature
      1. Innovation game
        1. A set of features
        2. Each buyer gets a budget of play money to spend on features
        3. Each feature is priced according to some measure of cost
        4. Each player’s budget should be between a third to half of the total cost for all features
        5. The game ends when the money runs out or when players have bought all the features they’re interested in
      2. Let's play
        1. Individually
        2. Collaboratively
  2. External & Qualitative techniques
    1. Story Mapping
      1. There’s a horizontal axis that represents usage sequence;
        1. User stories (or “tasks”) are placed along this axis, in the sequence in which they are performed by the user;
      2. The vertical axis stands for criticality;
        1. User stories (or “tasks”) are arranged vertically as to how important they are (from top to bottom);
      3. Create a vertical line to separate groups of stories from others;
    2. MoSCoW
      1. Must have
        1. critical and must be included into the product
      2. Should have
        1. requirements are important but not crucial for the release
      3. Could have
        1. these requirements are desirable but not necessary for the release
      4. Won’t have
        1. the least-critical or even not aligned with the product strategy
    3. Prune the Product Tree
      1. innovation game from Luke Hohmann
        1. shaping the product’s direction towards market needs, but also understanding if some product areas are being left behind
      2. Let's Use
        1. Draw a large tree
          1. limbs - core product areas
          2. branches - currently available features
        2. Ask customers/stakeholders to place their desired features on the tree, thus defining its next phase of growth
    4. Speed Boat
      1. final innovation game
        1. identifying which are the least liked features in the product
      2. create a “let it all out” kind of session with customers
      3. Let's use
        1. Draw a boat
          1. speed boat
          2. is the product
          3. it’s being held back by some anchors
          4. are the features that customers feel frustrated with;
          5. how much faster we estimate the boat could move without anchors
    5. RICE. Some notes about prioritization
      1. https://www.xmind.net/m/tLEFpj/
    6. WSJF from SAFe. Let's prioritize right way!
      1. https://www.xmind.net/m/ism9Dc/
  3. Internal & Quantitative Techniques
    1. Financial analysis
      1. Goals
        1. New Revenue
        2. Incremental Revenue
        3. Retained Revenue
          1. income that’s not lost because customer churn is reduced
        4. Cost Savings
        5. answer the questions
          1. How much of today’s money will we have after X amount of time, if we invest in this project?
          2. What’s the return on this project in percentage terms?
          3. How long will it take to earn back this investment?
    2. Net Present Value (NPV)
      1. How much of today’s money will we have after X amount of time, if we invest in project A or project B?
        1. https://en.wikipedia.org/wiki/Present_value
    3. Internal Rate of Return (IRR)
      1. How quickly an investment will increase in value
      2. IRR is defined as the interest rate at which the NPV is equal to zero.
    4. Discounted Payback Period
      1. how long it will take to get back the investment
    5. Ian McAllister’s Framework
      1. Define the important themes for the product or business
      2. Prioritize and resource the themes
      3. Generate project ideas
      4. Estimate each project’s potential impact
      5. Estimate each project’s costs
      6. Prioritize project within each theme
    6. Impact on Business Goal
      1. AARRR
        1. Subtopic 1
    7. Value vs. Risk
      1. Risk
        1. Schedule risk
        2. Cost risk
        3. Functionality risk
        4. balance
          1. High-risk/High-value first
          2. Low-risk/High-value second
          3. Low-risk/Low-value
          4. High-risk/Low-value
    8. Value vs. Cost
      1. ROI-like analysis
        1. try to maximize value delivery over time
          1. high-value, low-cost items
          2. high-value, high-cost items
    9. Scorecard
      1. prioritize features over a set of criteria that have been negotiated with stakeholders
    10. Theme Screening
      1. focus on evaluating themes and features in relative terms
        1. according baseline
  4. Internal & Qualitative Techniques
    1. Classification Ranking
      1. for very small and internal projects
      2. each feature is classified into some category, and then a ranking is produced
        1. 1-2-3-4-5
        2. High-Medium-Low
    2. Systemico Model
      1. to prioritize entirely in terms of Value to the customer and view that process as something that is systemic and holistic
        1. Product requirements are made visible in terms of how they address user goals and engagement levels.
      2. two-dimensional grid
        1. User Goals
          1. Why some functionality is necessary
        2. User Engagement
          1. Core
          2. to satisfy users’ basic needs
          3. baseline
          4. Use
          5. to increase the product’s usability
          6. Engage
          7. to have more interaction with the product
          8. Explore
          9. to build a stronger connection between the user and the product
    3. Impact Mapping
      1. https://www.xmind.net/m/VCsS9v/
    4. Stacked Ranking
      1. backlog is based on conversations and talks with stakeholders
    5. Feature Buckets
      1. 4 buckets
        1. Metrics Movers
        2. Customer Requests
        3. Delight
          1. innovative features
        4. Strategic
        5. balanced product release should include features from all of these buckets
    6. KJ Method
      1. 8-step process
        1. Determine a Focus Question
        2. Organize the Group
        3. Put Opinions (or Data) onto Sticky Notes
        4. Put Sticky Notes on the Wall
        5. Group Similar Items
        6. Naming Each Group
        7. Voting for the Most Important Groups
        8. Ranking the Most Important Groups
    7. ARRRR Mapping
      1. Metrics for PO and not only: HEART, AARRRT, Daily Revenue
        1. https://www.xmind.net/m/8ykSRD/
  5. Sources
    1. https://foldingburritos.com/product-prioritization-techniques/
    2. https://habr.com/ru/company/hygger/blog/351238/
    3. https://pt.slideshare.net/tarangbaxi/prioritization-techniques-for-agile-teams
  6. Why
    1. create successful products that bring value to our customers and to the business
    2. to find balance between business and Dev Team