A taxonomy of dependencies in agile software development

Dependencies in a software project can contribute to unsatisfactory progress if they constrain or block the flow of work. Various studies highlight the importance of dependencies in the organisation of work; however dependencies in agile software development projects have not previously been a research focus. Drawing on three case studies of agile software projects, and the IS literature, this paper develops an initial taxonomy of agile software project dependencies. Three distinct categories of dependency are found: task, resource, and knowledge dependencies. This paper contributes to theory by providing a taxonomy of dependency types occurring in the area of agile software development. Practitioners can use this taxonomy as sensitising device to ensure they consider dependencies they might face that could hinder their projects, enabling them to take appropriate and timely mitigating action.

Global software development : measuring, approximating and reducing the complexity of global software development using extended axiomatic design theory

This paper considers GSD projects as designed artefacts, and proposes the application of an Extended Axiomatic Design theory to reduce their complexity in order to increase the probability of project success. Using an upper bound estimation of the Kolmogorov complexity of the so-called ‘design matrix’ (as a proxy of Information Content as a complexity measure) we demonstrate on two hypothetical examples how good and bad designs of GSD planning compare in terms of complexity. We also demonstrate how to measure and calculate the ‘structural’ complexity of GSD projects and show that by satisfying all design axioms this ‘structural’ complexity could be minimised.

The effect of software engineers' personality traits on team climate and performance: a systematic literature review

Context Over the past 50 years numerous studies have investigated the possible effect that software engineers' personalities may have upon their individual tasks and teamwork. These have led to an improved understanding of that relationship; however, the analysis of personality traits and their impact on the software development process is still an area under investigation and debate. Further, other than personality traits, "team climate" is also another factor that has also been investigated given its relationship with software teams' performance. Objective The aim of this paper is to investigate how software professionals' personality is associated with team climate and team performance. Method In this paper we detail a Systematic Literature Review (SLR) of the effect of software engineers' personality traits and team climate on software team performance. Results Our main findings include 35 primary studies that have addressed the relationship between personality and team performance without considering team climate. The findings showed that team climate comprises a wide range of factors that fall within the fields of management and behavioral sciences. Most of the studies used undergraduate students as subjects and as surrogates of software professionals. Conclusions The findings from this SLR would be beneficial for understanding the personality assessment of software development team members by revealing the traits of personality taxonomy, along with the measurement of the software development team working environment. These measurements would be useful in examining the success and failure possibilities of software projects in development processes. General terms Human factors, performance.

Critical success factors for the requirements engineering process, with reference to quality management of information systems development

Preliminary research into the critical factors associated with software development/implementation identified three dimensions for successful implementation based on alignment of the requirements engineering process with business needs, change management process and quality of the implementation process. Research results demonstrate the link between the conceptual model for process quality and the process management attributes determined during the research.

Providing process for projects in capstone courses

Our capstone course has undergone a number of evolutionary changes over the past few years. It was restructured to provide more realistic experiential learning with the introduction of larger software development projects involving 'real clients (sponsors)' and larger student teams with a mix of students across disciplines. We have introduced a project management focus into the course that allows for a more structured process of product development. This restructure was possible because the curriculum prior to the project course emphasized teamwork and project management.

This paper provides some background about our capstone course and the significance of the contribution made by two other courses taken earlier in the programme.

Development of an internet supportive platform for online teaching and learning of construction planning and scheduling

Construction Planning and Scheduling is taught for the fIrst time ill Semester 2, 2004 in the School of Architecture and Building, Deakin University. During the unit development process and the implementation of teaching activities, several issues arose in relation to implementing computer-aided construction scheduling and unit delivery in a unitary environment. Although various types of construction planning and scheduling software have been developed and applied, none of them can be run inside an online teaching software package, which provides powerful functions in administration. This research aims to explore the strategies to connect a project planning and scheduling software package and an online ~aching and learning software package by a Web-based support platform so that both the lecturer and students can draw up and communicate a construction plan or schedule with tables and fIgures. The key techniques of this supportive platfonn are idt;nlifies and they include a web-based graphically user-interfaced, dynamic and distributed multimedia data acquisition mechanism, which accepts users' drawings and retrieval information from canvas and stores the multimedia data ona server for further usage. This paper demonstrates the techniques and principals needed to construct such a multimedia data acquisition tool. This. research will fill the gap.in the literature in respect to an online pedagogical solution to an existing problem.

The attraction, retention/transition and nurturing process of sport development : some Australian evidence

The purpose of this study was to explore and map the sport development processes in Australia. A grounded theory approach identified sport development processes by examining 74 annual reports from 35 national sporting organizations (NSOs) over a period of 4 years, before and after the Sydney Olympic Games. The 3 frameworks presented in this article representing the attraction, retention/ transition, and nurturing process illustrate the generic processes and strategies described by NSOs. The results show that each sport development process requires human and financial input from various stakeholders. These stakeholders initiate or implement sport development strategies for each process and each process has different sport development outputs. These results contribute to the extant literature of sport development by demonstrating that sport development is more complex and encompassing than previously described. It is proposed that the generic frameworks derived from this study be subject to more specific testing using other sport systems, as context and case studies could lead to tailoring the frameworks to represent specific sport development processes and systems.

Understanding educational process in leadership development

This thesis is a case study of educational process in the leadership development program of the Australian Defence Force Academy. The intention is to determine the relative emphasis in educational process on the conventional command and managerial compliance (Type A) style and the emergent contingent and creative (Type B) style of leadership. The Type A style is theorised as emphasizing hierarchy and control, whereas the emphasis in a Type B style is on adaptive and entrepreneurial behaviour. This study looks at the learning process in a cultural and structural context rather than focus on curriculum and instructional design. Research in this wider context is intended to enable development processes to successfully bridge a gap between theory and practice, implicit in studies that identify theories 'in-operation' as different from the theories 'espoused' (Argyris 1992, Savage 1996). In terms of espoused and in-use theory, the study seeks to produce a valid and reliable result to the question: what is the relative emphasis on the two leadership styles in the operation of the three educational mechanisms of curriculum, pedagogy (teaching practice) and assessment? The quantitative analysis of results (n = 114) draws attention to both leadership styles in terms of two and three-way relationships of style, cadet or work group and service type. The data shows that both Type A and Type B leadership styles are evident in the general conversation of the organisation. This trend is present as espoused theory in the curriculum of the Defence Academy. However, the data also confirm a clear and strong emphasis towards command and managerial compliance as theory-in-use, particularly by cadets. This emphasis is noticeably evident in the teaching and assessment practice of the Defence Academy. Other research outcomes include the observation that: Contextually, while studies show it is difficult to isolate skills from their cultural and biographical context (Watkins, 1991:15), this study suggests that it is equally difficult to isolate skills development from this context. There is a strong task or instrumental link identified by cadet responses in terms of content and development process at the Defence Academy, in contrast to the wider developmental emphasis in general literature and senior officer interviews. There is a lack of awareness of teaching strategies and development activity consistent with espoused Type B leadership theory and curriculum content. This gap is compounded by the use in the Defence Academy of personnel without teaching expertise or suitable developmental experience. The socialisation of cadets into the military workplace is the primary purpose of training. This purpose appears taken for granted by all concerned - staff, cadets and senior officers. Defence Academy development processes appear to be faced with a dilemma. Arguably, training and learning from experience are limited approaches to development. Training, which involves learning by replication, and learning from experience, which is largely imitative, are both of little use when people are faced with novel and ambiguous situations. This study suggests that in order to support the development of capabilities that go beyond training based competence a learning and development approach is needed. This more expansive approach requires educational planners to consider the cultural and social context that can inadvertently promote the status quo in practice over espoused outcomes.

Performance appraisal of software testers

Context To determine the effectiveness of software testers a suitable performance appraisal approach is necessary, both for research and practice purposes. However, review of relevant literature reveals little information of how software testers are appraised in practice. Objective (i) To enhance our knowledge of industry practice of performance appraisal of software testers and (ii) to collect feedback from project managers on a proposed performance appraisal form for software testers. Method A web-based survey with questionnaire was used to collect responses. Participants were recruited using cluster and snowball sampling. 18 software development project managers participated. Results We found two broad trends in performance appraisal of software testers - same employee appraisal process for all employees and a specialized performance appraisal method for software testers. Detailed opinions were collected and analyzed on how performance of software testers should be appraised. Our proposed appraisal approach was generally well-received. Conclusion Factors such as number of bugs found after delivery and efficiency of executing test cases were considered important in appraising software testers' performance. Our proposed approach was refined based on the feedback received.

An empirical investigation of personality traits of software testers

Software testing is the process of an execution based investigation of some aspects of the software's quality. The efficiency of the process depends on the methods and technologies used, but crucially also on the human testers. Software testers typically attempt to anticipate and expose ways software may be defective, a fundamentally different task set to those of other software development practitioners. This raises the question of whether the personality of software testers may be different to other people involved in software development. To test this hypothesis, we collected personality profiles using the big five factor model of around 200 software development practitioners. Analysis of this data indicates that software testers are significantly higher on the conscientiousness factor than other software development practitioners, while other factors remain broadly consistent.

A development and evaluation process for mHealth interventions: examples from New Zealand

The authors established a process for the development and testing of mobile phone-based health interventions that has been implemented in several mHealth interventions developed in New Zealand. This process involves a series of steps: conceptualization, formative research to inform the development, pretesting content, pilot study, pragmatic randomized controlled trial, and further qualitative research to inform improvement or implementation. Several themes underlie the entire process, including the integrity of the underlying behavior change theory, allowing for improvements on the basis of participant feedback, and a focus on implementation from the start. The strengths of this process are the involvement of the target audience in the development stages and the use of rigorous research methods to determine effectiveness. The limitations include the time required and potentially a less formalized and randomized approach than some other processes. This article aims to describe the steps and themes in the mHealth development process, using the examples of a mobile phone video messaging smoking cessation intervention and a mobile phone multimedia messaging depression prevention intervention, to stimulate discussion on these and other potential methods.