Earlier, the software industries followed intense traditional software processes to prepare software. But as the time passes by, everything changed. Withstanding the requirements changes or clients requests with the traditional software process is difficult. For this reason, many software industries have moved from traditional to agile software process. Agile has the ability to adapt to frequently changing requirements in which prioritization of these requirements plays a major role. The analysis aims to fulfill the gaps while prioritizing requirements. The literature survey gave an idea about the existing methods in prioritizing requirements and their gaps. Some of the existing methods are MoSCoW, Validated Learning, Business Value base, Walking Skeleton. The above methods had their own approach for prioritizing the requirements, but they were not able to resolve the Stakeholder Conflict (the stakeholder opinion). The extensive survey ended up in discovering approaches which caninclude Stakeholder Conflict. The work is done in four different contexts. They are: WhaleRank optimization based Ranking, Improved Scrum through Staging priority and Cyclomatic Complexity.