The user stories are provided by the business. These stories tell the UXD team the "what", "who" and "why" of the design requirements. Based on the discussion or story time, the Business Analyst can come up with more relevant and detailed user stories. The UXD team can use card sorting for organizing the available information and identify different categories of the target audience.
The agile framework is a robust one - but one with room for improvement. Working with Agile for creating a user-friendly design can be great, but it does come with its own set of challenges which can make Agile UX designing a little difficult. This is where RIDE comes in. RIDE stands for Rapid Iterative Design Experience, which is a distributed but governed model that improves the efficiency of design in a scaled agile framework. Right from assessing the user and the business' needs to testing and modifying the design, the RIDE model is good and effective through every step.
Agile and UX both focus on the same objective – providing better solutions and a more fluent management of deliverables by addressing the key pitfalls of traditional software development. In doing so, the two concepts relate to, and even complement each other. Incorporating a customer feedback loop in Agile for instance, is a logical extension of the methodology's principle of iterative development or incremental changes.
The UX design and output that you get when working in an Agile environment depends largely on the team you have in place. Usually, an Agile UX project team has only one UX design expert, who takes care of wireframe design and whatever usability testing is possible.