@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}
}
@article {Li.2006.1,
	title = {An Empirical Study of Variations in COTS-Based Software Development Processes in Norwegian IT Industry},
	journal = {Empirical Software Engineering},
	volume = {11},
	number = {3},
	year = {2006},
	month = {September},
	pages = {433-461},
	author = {Li, Jingyue and Finn Olav {Bj{\o}rnson} and Conradi, Reidar and Vigdis By {Kampenes}}
}
@inbook {Arisholm.2006.1,
	title = {Evaluating the Effect of a Delegated Versus Centralized Control Style on the Maintainability of Object-Oriented Software},
	booktitle = {Software Process Improvement: Results and Experience from the Field},
	year = {2006},
	pages = {379-406},
	publisher = {Springer},
	organization = {Springer},
	chapter = {20},
	author = {Arisholm, Erik and Sj{\o}berg, Dag Ingar Kondrup},
	editor = {Conradi, Reidar and Dyb{\r a}, Tore and Sj{\o}berg, Dag Ingar Kondrup and Ulsund, Tor}
}
@inbook {Anda.2006.2,
	title = {Experiences From Introducing UML-Based Development in a Large Safety-Critical Project},
	booktitle = {Software Process Improvement. Results and Experiences from the Field},
	year = {2006},
	pages = {329-359},
	publisher = {Springer},
	organization = {Springer},
	chapter = {18},
	isbn = {3-540-32178-0},
	author = {Anda, Bente Cecilie Dahlum and Hansen, Kai and Gullesen, Ingolf and Hanne Kristin {Thorsen}},
	editor = {Conradi, Reidar and Dyb{\r a}, Tore and Sj{\o}berg, Dag Ingar Kondrup and Ulsund, Tor}
}
@book {Conradi.2006.3,
	title = {Software Process Improvement: Results and Experience From the Field},
	year = {2006},
	month = {March},
	publisher = {Springer},
	abstract = {For over a decade, software process improvement (SPI) has been promoted as an approach to improve systematically the way software is developed and managed. Mostly this research and the relevant experience reports have been focussed on large software companies. Conradi and his co-authors have collected the main results from four Norwegian industrial research and development projects on SPI carried out between 1996 and 2005, which, in contrast to other treatments, concentrated on small- and medium-sized companies, typically characterized by fast-changing environments and processes. The presentation is organized in five sections: general principles and methods of SPI, knowledge management for SPI, process modelling and electronic process guides, estimation methods, and object-oriented and component-based systems. A spectrum of empirical methods has been used, e.g. case studies, large-scale experiments, surveys and interviews, and action research. The book mainly targets researchers and graduate students in (empirical) software engineering, and software professionals working in development or quality assurance},
	isbn = {3-540-32178-0},
	author = {Conradi, Reidar and Dyb{\r a}, Tore and Sj{\o}berg, Dag Ingar Kondrup and Ulsund, Tor}
}
@inproceedings {Mohagheghi.2005.1,
	title = {Effort Estimation of Use Cases for Incremental Large-Scale Software Development},
	journal = {ICSE{\textquoteright}05},
	year = {2005},
	month = {May},
	pages = {303-311},
	publisher = {The 27th International Conference on Software Engineering, 15-21 May, St Louis, Missouri, USA},
	type = {Conference},
	abstract = {This paper describes an industrial study of an effort estimation method based on use cases, the Use Case Points method. The original method was adapted to incremental development and evaluated on a large industrial system with modification of software from the previous release. We modified the following elements of the original method: a) complexity assessment of actors and use cases, and b) the handling of non-functional requirements and team factors that may affect effort. For incremental development, we added two elements to the method: c) counting both all and the modified actors and transactions of use cases, and d) effort estimation for secondary changes of software not reflected in use cases. We finally extended the method to: e) cover all development effort in a very large project. The method was calibrated using data from one release and it produced an estimate for the successive release that was only 17\% lower than the actual effort. The study identified factors affecting effort on large projects with incremental development. It also showed how these factors can be calibrated for a specific context and produce relatively accurate estimates.},
	author = {Mohagheghi, Parastoo and Anda, Bente Cecilie Dahlum and Conradi, Reidar},
	editor = {Mohagheghi, Parastoo and Anda, Bente Cecilie Dahlum and Conradi, Reidar}
}
@article {Li.2005.1,
	title = {An Empirical Study of Variations in COTS-Based Software Development Processes in Norwegian IT Industry},
	journal = {Empirical Software Engineering},
	year = {2005},
	author = {Li, Jingyue and Finn Olav {Bj{\o}rnson} and Conradi, Reidar and Vigdis By {Kampenes}}
}
@inproceedings {Conradi.2005.1,
	title = {Reflections on Conducting an International Survey of CBSE in ICT Industry},
	journal = {ISESE05 (Fourth International Symposium on Empirical Software Engineering)},
	year = {2005},
	pages = {214-223},
	publisher = {IEEE Computer Society},
	type = {1},
	address = {Noosa, Australia, November 17-18},
	author = {Conradi, Reidar and Li, Jingyue and Odd Petter {Slyngstad} and Vigdis By {Kampenes} and Bunse, Christian and Morisio, Maurizio and Torchiano, Marco}
}
@inbook {Sjoberg.2003.1,
	title = {Challenges and Recommendations When Increasing the Realism of Controlled Software Engineering Experiments},
	booktitle = {Empirical Methods and Studies in Software Engineering: Experiences from ESERNET},
	series = {Lecture Notes in Computer Science, Volume 2765},
	year = {2003},
	pages = {24-38},
	publisher = {Springer},
	organization = {Springer},
	chapter = {Part II: Method Chapters},
	address = {Berlin / Heidelberg},
	abstract = {An important goal of most empirical software engineering experiments is the transfer of the research results to industrial applications. To convince industry about the validity and applicability of the results of controlled software engineering experiments, the tasks, subjects and the environments should be as realistic as practically possible. Such experiments are, however, more demanding and expensive than experiments involving students, small tasks and pen-and-paper environments. This chapter describes challenges of increasing the realism of controlled experiments and lessons learned from the experiments that have been conducted at Simula Research Laboratory.},
	isbn = {978-3-540-40672-3},
	author = {Sj{\o}berg, Dag Ingar Kondrup and Anda, Bente Cecilie Dahlum and Arisholm, Erik and Dyb{\r a}, Tore and J{\o}rgensen, Magne and Karahasanovic, Amela and Vok{\'a}c, Marek},
	editor = {Conradi, Reidar and Alf Inge {Wang}}
}
