Authors:
Benjamin S. Blau
1
;
Tobias Hildenbrand
1
;
Matthias Armbruster
1
;
Martin G. Fassunge
1
;
Yongchun Xu
2
and
Rico Knapper
2
Affiliations:
1
SAP AG, Germany
;
2
Research Center for Information Technology, Germany
Keyword(s):
Lean, Agile, Agent-based simulation, Performance, Incentive.
Related
Ontology
Subjects/Areas/Topics:
Agile Methodologies
;
Service-Oriented Software Engineering and Management
;
Software and Systems Development Methodologies
;
Software Engineering
;
Software Project Management
Abstract:
The application of lean principles and agile project management techniques in the domain of large-scale software product development has gained tremendous momentum over the last decade. However, a simple transfer of good practices from the automotive industry combined with experiences from agile development on a team level is not possible due to fundamental differences stemming from the particular domain specifics – i.e. different types of products and components (material versus immaterial goods), knowledge work versus production systems as well as established business models. Especially team empowerment and the absence of a a hierarchical control on all levels impacts goal orientation and business optimization. In such settings, the design of adequate incentive schemes in order to align local optimization and opportunistic behavior with the overall strategy of the company is a crucial activity of central importance.
Following an agent-based simulation approach with reinforcement le
arning, we (i) address the question of how information regarding backlog item dependencies is shared within and in between development teams on the product level subject to different incentive schemes. We (ii) compare different incentive schemes ranging from individual to team-based compensation. Based on our results, we are (iii) able to provide recommendations on how to design such incentives, what their effect is, and how to chose an adequate development structure to foster overall software product development flow by means of more economic decisions and thus resulting
in a shorter time to market. For calibrating our simulation, we rely on practical experience from a very large software company piloting and implementing lean and agile for about three years.
(More)