@inproceedings {SE.5.Westerheim.2002,
	title = {{\textquoteright}Leave the Programmers Alone{\textquoteright} - a Case Study},
	journal = {4th International Conference on Product Focused Software Process Improvement},
	year = {2002},
	month = {December 9-11},
	pages = {291-299},
	publisher = {Springer-Verlag},
	type = {1},
	address = {Rovaniemi, Finland},
	abstract = {There has been much focus on the development process in the Software Process Improvement community. This paper describes software process improvement work done within a product division in a medium-sized Norwegian software company. The division has the main responsibility for the market activities, development, implementation, maintenance and support of their software products. We identified three main problem areas related to the overall process for management of the software product. None of the problem areas were directly concerned with the development process itself. The problem areas were addressed by the division{\textquoteright}s management. Despite the lack of focus on the programmers and the development process, the programmers{\textquoteright} attitude changed into a more positive one. One reason might be that the new overall product handling process "protected" the programmers from the market activities, and also clarified responsibility for the core development and the maintenance development. This paper discusses the findings in the case-study, and concludes that maybe the best software process improvement initiative would be to simply leave the programmers alone.},
	author = {Westerheim, H. and Koren, E.}
}
@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.}
}
@inproceedings {SE.5.Koren.2002.b,
	title = {Techniques for Gathering Information About an Organisation and Its Needs for Software Process Improvement},
	journal = {EASE 2002},
	year = {2002},
	month = {April 8-10},
	publisher = {-},
	type = {1},
	address = {Keele, England},
	abstract = {This paper reports on how the authors planned and conducted the work in the initial phase of software process improvement in a Norwegian software house. The work was motivated by the results from the projects SPIQ (Dyb{\r a}, Wedde et al. 2000) and PROFIT (http://www.geomatikk.no/profit), where a pragmatic approach to software process improvement was the main focus. The way the work was conducted was further motivated by the results of Tore Dyb{\r a} (Dyb{\r a} 2001). He claimed that for instance participation of employees and exploitation of existing knowledge has positive influence on the success of software process improvement. This led us to arrange workshops with participants from all relevant parts of the organisation to gather a picture as broad as possible of the situation. The paper is organised as follows: First we describe the motivation behind the choice of method. Then we describe the case study. Then we discuss the results we got from our investigations. The paper ends with a conclusion and a description of further work.},
	author = {Koren, E. and Westerheim, H.}
}
