Abstract
Agile development is a force that reshapes requirements engineering (RE). Agile RE processes are not constrained to pre-development phase like in traditional RE; they're evenly spread throughout development. High-level RE occurs at the project beginning, and then agile RE continues at each development cycle. Each development cycle starts with customer representatives discussing requirements with the development teams. To seek new understanding of the requirements engineering process in agile projects, we have applied the model of software development as a conversation. In this paper we describe this model and use it to explain a selection of findings from a case study in a large-scale agile project.