Scrum Code Camps

Jan Pries-Heje; Lene Pries-Heje; Bente Dahlgaard

doi:10.1109/AGILE.2013.29

Scrum Code Camps

Jan Pries-Heje, Lene Pries-Heje, Bente Dahlgaard

Publikation: Bidrag til bog/antologi/rapport › Konferencebidrag i proceedings › Forskning › peer review

Abstract

A classic way to choose a supplier is through a bidding process where tenders from competing companies are evaluated in relation to the customer’s requirements. If the customer wants to hire an agile software developing team instead of buying a software product, a new approach for comparing tenders is required. In this paper we present the design of such a new approach, the Scrum Code Camp, which can be used to assess agile team capability in a transparent and consistent way. A design science research approach is used to analyze properties of two instances of the Scrum Code Camp where seven agile teams were evaluated.

Originalsprog	Engelsk
Titel	Agile Conference (AGILE) 2013
Antal sider	10
Vol/bind	2013
Forlag	IEEE
Publikationsdato	2013
Sider	64-73
DOI	https://doi.org/10.1109/AGILE.2013.29
Status	Udgivet - 2013
Begivenhed	AGILE 2013 - Nashville, USA Varighed: 5 aug. 2013 → 9 aug. 2013 http://agile2013.agilealliance.org/

Konference

Konference	AGILE 2013
Land/Område	USA
By	Nashville
Periode	05/08/2013 → 09/08/2013
Internetadresse	http://agile2013.agilealliance.org/

Navn	Agile Conference 2013

Link til dokument

10.1109/AGILE.2013.29

http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6612880&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6612880

Citer dette

@inproceedings{bebb4cdcb8b1475cb9f9ed7836c76aa1,

title = "Scrum Code Camps",

abstract = "A classic way to choose a supplier is through a bidding process where tenders from competing companies are evaluated in relation to the customer{\textquoteright}s requirements. If the customer wants to hire an agile software developing team instead of buying a software product, a new approach for comparing tenders is required. In this paper we present the design of such a new approach, the Scrum Code Camp, which can be used to assess agile team capability in a transparent and consistent way. A design science research approach is used to analyze properties of two instances of the Scrum Code Camp where seven agile teams were evaluated. ",

author = "Jan Pries-Heje and Lene Pries-Heje and Bente Dahlgaard",

year = "2013",

doi = "10.1109/AGILE.2013.29",

language = "English",

volume = "2013",

series = "Agile Conference 2013",

publisher = "IEEE",

pages = "64--73",

booktitle = "Agile Conference (AGILE) 2013",

address = "United States",

note = "AGILE 2013 ; Conference date: 05-08-2013 Through 09-08-2013",

url = "http://agile2013.agilealliance.org/",

}

TY - GEN

T1 - Scrum Code Camps

AU - Pries-Heje, Jan

AU - Pries-Heje, Lene

AU - Dahlgaard, Bente

PY - 2013

Y1 - 2013

N2 - A classic way to choose a supplier is through a bidding process where tenders from competing companies are evaluated in relation to the customer’s requirements. If the customer wants to hire an agile software developing team instead of buying a software product, a new approach for comparing tenders is required. In this paper we present the design of such a new approach, the Scrum Code Camp, which can be used to assess agile team capability in a transparent and consistent way. A design science research approach is used to analyze properties of two instances of the Scrum Code Camp where seven agile teams were evaluated.

AB - A classic way to choose a supplier is through a bidding process where tenders from competing companies are evaluated in relation to the customer’s requirements. If the customer wants to hire an agile software developing team instead of buying a software product, a new approach for comparing tenders is required. In this paper we present the design of such a new approach, the Scrum Code Camp, which can be used to assess agile team capability in a transparent and consistent way. A design science research approach is used to analyze properties of two instances of the Scrum Code Camp where seven agile teams were evaluated.

U2 - 10.1109/AGILE.2013.29

DO - 10.1109/AGILE.2013.29

M3 - Article in proceedings

VL - 2013

T3 - Agile Conference 2013

SP - 64

EP - 73

BT - Agile Conference (AGILE) 2013

PB - IEEE

T2 - AGILE 2013

Y2 - 5 August 2013 through 9 August 2013

ER -