The agile methods analyzed and reported on in this paper are those consistent with the manifesto for agile software development. For these collectively, this paper examines the methods' contributions in software maintenance and evolution, to and by three groups of software system stakeholders: users, customers, and information systems personnel. For each, a picture emerges that has not been previously reported in the literature. That picture is a mix of favorable and unfavorable contributions, and weights that are situation dependent.