Agile Contracts

Designing an Agile Team Selection Guideline

Jan Pries-Heje, Lene Pries-Heje

Research output: Contribution to journalConference articleResearchpeer-review

Abstract

When you have stable and non-ambiguous requirements then a classic contract for IS between a supplier and a public sector institution based on a requirements specification may be well suited. However, if you have to accept many changes or have ambiguous requirements then you may end up with “endless” re-negotiation of the requirements; you need a more flexible way to develop IS. A new way of coping with many changes is to use an agile development approach and a fixed budget and resources contract. This paper presents an example case. We analyse the case and design a guideline for how to implement a fixed budget and resources contract in the public sector. The guideline includes elements to cope with challenges in a tender process such as transparency, criteria for supplier selection, and live assessment of resource skills and capabilities, as well as achieving the flexibility for change needed.
Original languageEnglish
JournalProceedings / Information Systems Research In Scandinavia (IRIS)
Issue number5
ISSNx000-0036
Publication statusPublished - 2014

Cite this

@inproceedings{c948ef8fc189496b94509918e7aec59e,
title = "Agile Contracts: Designing an Agile Team Selection Guideline",
abstract = "When you have stable and non-ambiguous requirements then a classic contract for IS between a supplier and a public sector institution based on a requirements specification may be well suited. However, if you have to accept many changes or have ambiguous requirements then you may end up with “endless” re-negotiation of the requirements; you need a more flexible way to develop IS. A new way of coping with many changes is to use an agile development approach and a fixed budget and resources contract. This paper presents an example case. We analyse the case and design a guideline for how to implement a fixed budget and resources contract in the public sector. The guideline includes elements to cope with challenges in a tender process such as transparency, criteria for supplier selection, and live assessment of resource skills and capabilities, as well as achieving the flexibility for change needed.",
author = "Jan Pries-Heje and Lene Pries-Heje",
year = "2014",
language = "English",
journal = "Proceedings / Information Systems Research In Scandinavia (IRIS)",
issn = "x000-0036",
number = "5",

}

Agile Contracts : Designing an Agile Team Selection Guideline. / Pries-Heje, Jan; Pries-Heje, Lene.

In: Proceedings / Information Systems Research In Scandinavia (IRIS), No. 5, 2014.

Research output: Contribution to journalConference articleResearchpeer-review

TY - GEN

T1 - Agile Contracts

T2 - Designing an Agile Team Selection Guideline

AU - Pries-Heje, Jan

AU - Pries-Heje, Lene

PY - 2014

Y1 - 2014

N2 - When you have stable and non-ambiguous requirements then a classic contract for IS between a supplier and a public sector institution based on a requirements specification may be well suited. However, if you have to accept many changes or have ambiguous requirements then you may end up with “endless” re-negotiation of the requirements; you need a more flexible way to develop IS. A new way of coping with many changes is to use an agile development approach and a fixed budget and resources contract. This paper presents an example case. We analyse the case and design a guideline for how to implement a fixed budget and resources contract in the public sector. The guideline includes elements to cope with challenges in a tender process such as transparency, criteria for supplier selection, and live assessment of resource skills and capabilities, as well as achieving the flexibility for change needed.

AB - When you have stable and non-ambiguous requirements then a classic contract for IS between a supplier and a public sector institution based on a requirements specification may be well suited. However, if you have to accept many changes or have ambiguous requirements then you may end up with “endless” re-negotiation of the requirements; you need a more flexible way to develop IS. A new way of coping with many changes is to use an agile development approach and a fixed budget and resources contract. This paper presents an example case. We analyse the case and design a guideline for how to implement a fixed budget and resources contract in the public sector. The guideline includes elements to cope with challenges in a tender process such as transparency, criteria for supplier selection, and live assessment of resource skills and capabilities, as well as achieving the flexibility for change needed.

M3 - Conference article

JO - Proceedings / Information Systems Research In Scandinavia (IRIS)

JF - Proceedings / Information Systems Research In Scandinavia (IRIS)

SN - x000-0036

IS - 5

ER -