System Requirements the Agile Way

Requirement engineering evolved are not new today but are over decades and has become fundamental instrument in computer science. Requirement engineering is the most important thing in software engineering and development. It is the most important area of software development life cycle. The System Requirement Specification is the base for the software project in classic software methodologies, As Managing requirements is not an easy task, Producing high quality software products meeting the stakeholders requirements is a major challenge in software engineering. Dynamically changing environments make changes to requirements in the software development process an inevitable task. Poor requirements and changes to requirements are major elements that cause software project failures. Requirements management and Agile developments are current areas of study. Many authors have written on requirements changes, however, most recent literature has not specifically studied an empirical approach to requirements management in an Agile-Scrum development process. This review explores requirements changes in an Agile-Scrum process. Agile methodologies focus on functional requirements This research intends to demonstrate how the application of the Agile-Scrum methodology produces software that meets user needs. If the traditional notions of requirements change are correct, then using the Agile-Scrum should deliver less functionality in a fixed-length development project. Aim of this review paper is also to present the limitations of requirement engineering phases in agile practices and the issues and challenges in implementation of agile practices. Agile methodology allows changes to requirements even late into the project with minimal impact on software functionality and quality of the delivered product