What Counts in Software Process? Negotiating the Boundary of Software Work through Artifacts and Conversation

    Research output: Journal Article or Conference Article in JournalJournal articleResearchpeer-review

    Abstract

    In software development, there is an interplay between Software Process models and Software Process enactments. The former tends to be abstract descriptions or plans. The latter tends to be specific instantiations of some ideal procedure. In this paper, we examine the role of work artifacts and conversations in negotiating between prescriptions from a model and the contingencies that arise in an enactment. A qualitative field study at two Agile software development companies was conducted to investigate the role of artifacts in the software development work and the relationship between these artifacts and the Software Process. Documentation of software requirements is a major concern among software developers and software researchers. Agile software development denotes a different relationship to documentation, one that warrants investigation. Empirical findings are presented which suggest a new understanding of the relationship between artifacts and Software Process. The paper argues that Software Process is a generative system, which participants called “The Conversation,” that emerges out of the interplay between Software Process models and Software Process enactments.
    Original languageEnglish
    JournalComputer Supported Cooperative Work
    Volume18
    Issue number5-6
    Pages (from-to)401-443
    ISSN0925-9724
    Publication statusPublished - 2009

    Keywords

    • agile software development
    • requirements documentation
    • work artifacts
    • software process models and enactments
    • collaboration
    • negotiation

    Fingerprint

    Dive into the research topics of 'What Counts in Software Process? Negotiating the Boundary of Software Work through Artifacts and Conversation'. Together they form a unique fingerprint.

    Cite this