Proc. 16 th International Conference on Statistical Sciences Peshawar, Pakistan – March 05-08, 2018, Vol. 32, pp. 77-88 REQUIREMENTS PRIORITIZATION: A COMPARISON BETWEEN TRADITIONAL AND AGILE (SCRUM AND FDD) Atif Ali 1 , Yaser Hafeez 2 , Syed Fakhar Abbas 3 and Amber Sarwar 4 University Institute of Information Technology, UAAR, Rawalpindi, Pakistan Email: 1 atif.alii@yahoo.com 2 yasir@uaar.edu.pk 3 fakhar.dps@gmail.com 4 ambersarwar@hotmail.com ABSTRACT Development of a software intensive system is done on the premise of some required/requested capabilities, termed as „requirement‟. The objective, for software application development, emphasizes on client's requirement, in light of set of characterized and comprehended standards. The set of requirements, when engineered legitimately, may uncover that a few requirements are of most extreme significance for user. Notwithstanding a set of requirements, might be those which are of minimum significance. Choosing the needs of requirements under certain criteria is done in prioritization phase of requirements engineering phase. This paper presents how requirements prioritization is applied in conventional software development approaches in contrast to Agile Software Development Methodologies (SCRUM and FDD). Actors, activities and exercises performed by them and artifacts created are taken as parameters of comparison. KEYWORDS Requirement Prioritization, Requirement Engineering, Agile, Scrum etc. 1. INTRODUCTION The term requirement, as restricted in The IEEE Standard Glossary of Software Engineering Terminology (1990), relates with the conditions or abilities a client needs for, solving a problem or accomplishment of a goal [1]. Set requirements, for software intensive system, indicate what to implement alongside depicting the general conduct of system, a property utilized as a part of the system or a trait of the system. Numerous researchers are working in this field anyway it is difficult to make use of right technique at right time. It is meant to execute security viewpoint since the start of programming i.e. requirement engineering phase [2] Requirements engineering then again, characterizes a set of exercises for gathering of software requirements, investigating and displaying them, through systematic approach [3]. In requirement engineering, prioritization is very important aspect and consider as a groundwork for other subsequent phases of SDLC [4]. Effective requirement 77