Learn More
This paper reflects on three cases where the focus group method was used to obtain feedback and experiences from software engineering practitioners and application users. The focus group method and its background are presented, the method's weaknesses and strengths are discussed, and guidelines are provided for how to use the method in the software(More)
This paper reports findings from a survey that has been conducted in Finland to study how the software product companies have matured and evolved over the years. In addition to introducing some key terms for characterizing the software product business, we will provide some overall data on the sector, and discuss some specific issues related to the software(More)
This paper aims at identifying critical factors affecting organization-wide implementation of requirements engineering (RE) processes. The paper is based on a broad literature review and three longitudinal case studies that were carried out using an action research method. The results indicate that RE process implementation is a demanding undertaking, and(More)
Explicit risk management is gaining ground in industrial software development projects. However, there are few empirical studies that investigate the transfer of explicit risk management into industry, the adequacy of the risk management approaches to the constraints of industrial contexts, or their cost-benefit. This paper presents results from a case(More)
This paper describes experiences from two organizations that have used the Riskit method for risk management in their software projects. This paper presents the Riskit method, the organizations involved, case study designs, and findings from case studies. We focus on the experiences and insights gained through the application of the method in industrial(More)
Explicit and systematic management of risks in software projects has become a more common practice amongst leading software organizations, However, often the methods used have severe theoretical and practical limitations that may lead to biased or inappropriate control of risks. The first part of this tutorial presents a critical overview of the current(More)
Software development is always a challengingundertaking and it requires high commitments fromindividuals who participate in it. Software developmentoften involves new technology, challenging or unknownrequirements, and tight schedules ¿ making itparticularly prone to several types of risk. Thesechallenges are even more paramount in agiledevelopment and in(More)
Any software development project requires commitments from its participants. These commitments can include money, resources, deadlines, and specified functionality for the end product. We have developed a framework and a set of guidelines to support the specification of such commitments. We have evaluated the framework empirically in a series of case(More)