Traditionally, a high degree of requirement change has been considered harmful for the success of software projects. Software professionals who use agile software development methods tend to view this topic differently. They tend to view requirement changes more as opportunities, which should be welcomed. Possibly, both views are correct but valid in different software development contexts. This paper aims at increasing the understanding of the connections between the degree of requirement change, choice of development method, and project success. Seventy software professionals were asked to provide information about their last software project. A higher degree of requirement changes, here defined as more than 30% of the requirements added, deleted, or changed during the project’s execution, was connected with a higher proportion of successful projects in an agile development context, but only when this included frequent deliveries to production. Our results consequently support that the agile claim of “embrace change” has merit, but only in agile contexts.