Description: The relevance of researching the methodology for managing requirements for software in Agile based on the creation of user stories was substantiated in the article. An analysis of the use of tools for creating requirements in agile methodologies was conducted. The results of such analysis allow achieving the puppies – to investigate the processes of requirements management based on user stories. Four main stages can be identified in the requirement management: the creation, discussion, validation and structuring of user stories was shown. The main methods of prioritization, which include: the Cano method, the Pareto method, the quality function structuring (QFD) method, the causal diagram (Ishikawa diagram), the failure mode analysis method (FMEA), the methods of estimation, which include the Story Point metric, and the decomposition of user stories on such patterns: the sequence of actions, functional / non-functional requirements, the complexity of the functional, the basic work, the complexity of the interface, data variations, management operations, business rule options are considered. The advantages of the agile approach to requirements management based on user stories, that allows to quickly respond to changes in users' needs, save time and money for the creation software product was substantiated.
Keywords: Agile, software requirement, requirements management, user story, pattern