Employees' attitudes towards organizational change are a critical determinant in the change process. Researchers have therefore tried to determine what underlying concepts that affect them. These extensive efforts have resulted in the identification of several antecedents. However, no studies have been conducted in a software engineering context and the research has provided little information on the relative impact and importance of the identified concepts. In this study, we have combined results from previous social science research with results from software engineering research, and thereby identified three underlying concepts with an expected significant impact on software engineers' attitudes towards organizational change, i.e. their knowledge about the intended change outcome, their understanding of the need for change, and their feelings of participation in the change process. The result of two separate multiple regression analysis, where we used industrial questionnaire data (N=56), showed that the attitude concept openness to change is predicted by all three concepts, while the attitude concept readiness for change is predicted by need for change and participation. Our research provides an empirical baseline to an important area of software engineering and the result can be a starting-point for future organizational

Several research findings conclude that many doctoral students fail to complete their studies within the allowable time frame, in part because of problems related to the research and supervision process. Surveys show that most doctoral students are generally satisfied with their dissertation supervision. However, these surveys also reveal some students think their supervisors meet with them too infrequently, lack interest in their dissertation topics, and provide insufficient practical assistance. Furthermore, many countries will soon witness a large turnover in the labour market as people near retirement. Because this is also the case at many universities and colleges, the expectation is that there will be many teaching and research vacancies. Therefore, many new doctoral students who plan to enter academia after earning their doctoral degrees are needed. In responding to these complaints, this conceptual paper examines the use of the agile approach-which has achieved recognition and approval in software development-in the doctoral dissertation process. In the teaching/learning sphere, the agile approach can be used in iterative meetings between doctoral student and supervisor for dissertation planning, direction, and evaluation. The focus of the iterations, the so-called Sprints, is on communication and feedback throughout the entire process. The paper is based in theories on teaching/learning and on the author's personal experience with the agile approach. Use of the agile approach, which can decrease the time required for doctoral studies, may thus increase the number of graduates with doctoral degrees. The paper makes suggestions for practical implementation of the agile approach.

No abstract

The values of software organizations are crucial for achieving high performance; in particular, agile development approaches emphasize their importance. Researchers have thus far often assumed that a specific set of values, compatible with the development methodologies, must be adopted homogeneously throughout the company. It is not clear, however, to what extent such assumptions are accurate. Preliminary findings have highlighted the misalignment of values between groups as a source of problems when engineers discuss their challenges. Therefore, in this study, we examine how discrepancies in values between groups affect software companies' performance. To meet our objectives, we chose a mixed method research design. First, we collected qualitative data by interviewing fourteen (N  =  14) employees working in four different organizations and processed it using thematic analysis. We then surveyed seven organizations (N  =  184). Our analysis indicated that value misalignment between groups is related to organizational performance. The aligned companies were more effective, more satisfied, had higher trust, and fewer conflicts. Our efforts provide encouraging findings in a critical software engineering research area. They can help to explain why some companies are more efficient than others and, thus, point the way to interventions to address organizational challenges.

No abstract