Name
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. |
Year | DOI | Venue |
|---|---|---|
2015 | 10.1007/978-3-319-26844-6_10 | Product Focused Software Process Improvement |
Keywords | Field | DocType |
Agile software development, Artefacts, Case studies, Scrum | Scrum,Test plan,Systems engineering,Software engineering,Software design document,Agile software development,Notice,Empirical process (process control model),Engineering | Conference |
Volume | ISSN | Citations |
9459 | 0302-9743 | 1 |
PageRank | References | Authors |
0.35 | 12 | 4 |
Name | Order | Citations | PageRank |
|---|---|---|---|
| Gerard Wagenaar | 1 | 1 | 0.35 |
| Remko Helms | 2 | 114 | 12.71 |
| Daniela Damian | 3 | 2144 | 119.80 |
| Sjaak Brinkkemper | 4 | 2599 | 219.13 |