Product Owner : Requirement Prioritization Techniques 

                                        Requirement prioritization is used in Software product management for determining which requirements of the product should be included in a certain release. Requirements are also prioritized to minimize risk during development so that the most important or high-risk requirements are implemented first. Requirement’s prioritization is used to define the ordering or schedule for executing requirement based on their priority or importance with respect to stakeholders’ viewpoints. There are different Prioritization Techniques used in for this

MOSCOW – Must Have , Should Have, Could Have, Would Have

Ranking – Providing Numerical Ranking for the Requirements

KANO Analysis – This is based on satisfaction of the stakeholders

                  Basic Factors – Dissatisfiers

                  Performance Factors : - Satisfiers

                  Excitement Factors : - Delighters

User Story Mapping

                      Arranges as a Map of user stories based on the releases and planning with stakeholders and End to end clarity on the Product by this process.

There are many more Techniques are available requirement Prioritization Binary Search Tree, AHP(Analytic hierarchy process), Hundred Dollar, Minimal Spanning Tree, Data Mining And machines, Numerical Assignments , Bubble sorts are some among them.