@inproceedings {Simula.se.757,
	title = {Software Entropy in Agile Product Evolution},
	journal = {Proceedings of the 43rd Hawaii International Conference on System Sciences},
	year = {2010},
	pages = {1-10},
	publisher = {IEEE Computer Society},
	type = {Conference},
	abstract = {As agile software development principles and methods are being adopted by large software product organizations it is important to understand the role of software entropy. That is, how the maintainability of a system may degrade over time due to continuous change. This may on one side affect the ability to act agile in planning and development. On the other side, an agile process may affect growth of entropy. We report from a case study of a successful software product line organization that has adopted the agile development method Evo, showing how agility and entropy are negatively related. We conclude this study by suggesting a two-step approach to manage entropy while maintaining process agility. First, the system needs to be restructured to establish a level of manageable entropy, and then, that the agile process must be complemented with continuous semi-automated quality monitoring and refactoring support.},
	isbn = {978-0-7695-3869-3},
	doi = {http://doi.ieeecomputersociety.org/10.11},
	author = {Geir Kjetil {Hanssen} and Yamashita, Aiko and Conradi, Reidar and Moonen, Leon},
	editor = {Ralph H. {Sprague}}
}
@inproceedings {Simula.SE.629,
	title = {Maintenance and Agile Development: Challenges, Opportunities and Future Directions},
	journal = {25th IEEE International Conference on Software Maintenance (ICSM)},
	year = {2009},
	month = {March 2009},
	publisher = {IEEE},
	type = {Conference},
	abstract = {Software entropy is a phenomenon where repeated changes gradually degrade the structure of the system, making it hard to understand and maintain. This phenomenon imposes challenges for organizations that have moved to agile methods from other processes, despite agile{\textquoteright}s focus on adaptability and responsiveness to change. We have investigated this issue through an industrial case study, and reviewed the literature on addressing software entropy, focussing on the detection of {\textquotedblleft}code smells{\textquotedblright} and their treatment by refactoring. We found that in order to remain agile despite of software entropy, developers need better support for understanding, planning and testing the impact of changes. However, it is exactly work on refactoring decision support and task complexity analysis that is lacking in literature. Based on our findings, we discuss strategies for dealing with entropy in this context and present avenues for future research.},
	isbn = {978-1-4244-4897-5},
	author = {Geir Kjetil {Hanssen} and Yamashita, Aiko and Conradi, Reidar and Moonen, Leon},
	editor = {Beyer, Dirk}
}
@inproceedings {SE.5.Hanssen.2002,
	title = {SPI - Easy in Theory, Hard in Practice},
	journal = {Proceedings of European Software Process Improvement Conference (EuroSPI{\textquoteright}2002)},
	year = {2002},
	month = {18-20 September},
	type = {1},
	address = {N{\"u}rnberg, Germany},
	author = {Geir Kjetil {Hanssen} and Dyb{\r a}, Tore and St{\r a}lhane, T. and Dings{\o}yr, T. and Westerheim, H.}
}
