Artefacts in Agile Software Development

Gerard Wagenaar*, Remko Helms, Daniela Damian, Sjaak Brinkkemper

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contributionAcademicpeer-review

Abstract

Agile software development methods prefer limited use of artefacts. On the basis of existing artefact models and results from three case studies we present a Scrum artefact model. In this model we notice teams using Scrum artefacts, but they, in addition, decided to produce various non-Scrum artefacts, most notably design documents, test plans and user or release related materials.

Original languageEnglish
Title of host publicationProduct-Focused Software Process Improvement - 16th International Conference, PROFES 2015, Proceedings
EditorsMarkku Oivo, Pekka Abrahamsson, Luis Corral, Barbara Russo
Place of PublicationBozen-Bolzano, Italy
PublisherSpringer
Pages133-148
Number of pages16
ISBN (Print)9783319268439
DOIs
Publication statusPublished - 2015
Event16th International Conference on Product-Focused Software Process Improvement, PROFES 2015 - Bolzano, Italy
Duration: 2 Dec 20154 Dec 2015

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume9459
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

Conference16th International Conference on Product-Focused Software Process Improvement, PROFES 2015
Country/TerritoryItaly
CityBolzano
Period2/12/154/12/15

Keywords

  • Agile software development
  • Artefacts
  • Case studies
  • Scrum

Fingerprint

Dive into the research topics of 'Artefacts in Agile Software Development'. Together they form a unique fingerprint.

Cite this