Coordination artifacts in Agile Software Development

Agile Software Development is characterized by collaborative social interactions and fast-paced and iterative changes in project requirements. Much of the extant Agile development literature focuses on team and organizational aspects of Agile development projects. However, coordination mechanisms used within Agile projects have received less attention. Particularly, existing research lacks a discussion on how artifacts are applied in Agile software development to support project coordination, and how their potential for information richness and mutability impact their ability to support coordination.To address these issues, we conducted a case study of an Agile development project that involved customer and vendor organizations. Our case follows the interactions between the two organizations, identifies the different types of artifacts that they utilized to coordinate their joint activities throughout the various phases of the project, and traces the enactment of these artifacts' informational potential.Our study reveals that the organizations applied four different types of coordination artifacts - Foundational, Projective, Exposition and Indicative artifacts – to address different coordination challenges that arose throughout the project. The four types of artifacts were characterized by varying levels of information richness and mutability, which were shaped to support the Agile activities within which they were used.Our study enriches the understanding of the role of coordination artifacts in Agile projects, provides insights on the informational potential of the artifacts, and highlights some of the pitfalls than can result from misunderstanding object use.