Search results

This paper seeks to describe the application of the Agile software development approach to rapidly develop and deploy a variety of innovative IT applications.

The Agile approach is flexible and iterative with continuous feedback and constant communication. It is also marked by frequent and short delivery schedules. An Agile team of staff and students was formed for different projects, and visual tools were used to show process and progress. Team members were also co‐located (situated in the same space), a key element that allowed faster and direct communication. Within the Agile framework, the Crystal Clear methodology was selected, which is based on team size and criticality of the application to develop the workflow and iterative processes.

The Agile approach is particularly suited to innovation development and creative teams for rapid development of products, services, and technology. However, its acceptance is dependent on organizational culture and nature of application.

As a next step, it would be useful to test the Agile approach in an innovative application that is on a larger scale than six team members and with a different level of criticality.

Flexibility and adaptability are needed in managing the development of IT innovations and applications as they vary in size and complexity. The flexible and iterative Agile approach provided the framework to develop and implement these projects despite the small staff size.

There is little in the professional literature on software development and project management approaches for small teams. The Agile approach would be of interest to an IT unit or library with limited staff resources and interested in a lightweight framework to develop and deploy innovative projects.

The aim of this paper is to make an attempt to find good values of onsite–offshore team strength; number of hours of communication between business users and onsite team and between onsite and offshore team to reduce cost and improve schedule for re-engineering projects in global software development environment.

The system dynamics technique is used for simulation model construction and policy run experimentation. The experts from Indian software outsourcing industry were consulted for model construction, validation and analysis of policy run results in both co-located and distributed software development environment.

The study results show that there is a drop in the overall team productivity in outsourcing environment by considering the offshore options. But the project cost can be reduced by employing the offshore team for coding and testing work only with minimal training for imparting business knowledge. The research results show that there is a potential to save project cost by being flexible in project schedule.

The study found that there could be substantial cost saving for re-engineering projects with a loss of project schedule when an appropriate onsite–offshore combination is used. The quality and productivity drop, however, were rather small for such combinations. The cost savings are high when re-engineering work is sent to offshore location entirely after completion of requirement analysis work at onsite location and providing training to offshore team in business knowledge The research findings show that there is potential to make large cost savings by being flexible in project schedule for re-engineering projects.

The software project manager can use the model results to divide the software team between onsite and offshore location during various phases of software development in distributed environment.

The study is novel as there is little attempt at finding the team distribution between onsite and offshore location in global software development environment.

It is all too easy in the hectic world of business to get too involved with the day‐to‐day managing of processes and events. When this happens it is difficult to see the wood for the trees and the automatic pilot syndrome takes over. This does not suggest that you do not know what you are doing ‐ on the contrary you are probably as switched on to whatever activity you are managing as anyone could be. What you could be missing, however, is the explanation as to why you are doing it. If this sounds familiar to you, what might be needed is a detached period from your work. By this I mean stay on the high ground for a while so you can get an overview of what you are doing and, more importantly, why you are doing it. How many managers, I wonder, get the opportunity to question what they are doing? If you allow yourself to slip into complacency then you and your organization will soon lose competitive advantage.

The purpose of this study is to examine if there is a difference between service-sector Lean Six Sigma (LSS) project teams that progress through Tuckman’s group development model and those that do not in terms of the number of completed projects, the number of projects completed on time, the length of time to complete the projects and the total cost savings and avoidance because of the projects.

The research consisted of a quantitative, descriptive methodology. The design included a sample from a service-sector LSS practitioner population, a survey instrument, one independent construct with two levels, four dependent constructs and a multivariate analysis of variance (MANOVA).

The progression of service-sector LSS teams through Tuckman’s group development model, as measured with the group process questionnaire, significantly influences the teams in terms of the number of completed projects, the number of projects completed on time, the length of time to complete the projects and the total cost savings and avoidance because of the projects.

A limitation of the study is there may be other factors not related to Tuckman’s group development model that can influence the outcomes of LSS projects. These variables may include senior executive buy-in, number of LSS practitioners in the organization, the robustness of LSS training programs, level of talent and other factors not related to Tuckman’s group development model. Another limitation of the study encompassed using a sample of convenience instead of a random sample.

The recommendation for practice is binate. First, service-sector LSS project teams should ensure they progress through the stages of Tuckman’s group development model to enjoy the significantly improved project outcomes. Second, LSS practitioners and trainers should ensure that Tuckman’s group development model is part of the training curriculum.

The study demonstrates that all groups should attempt to progress through the stages of Tuckman and Jensen (2010) group development model to enjoy the benefits of working in a cohesive, task-focused team.

This study adds to the body of knowledge because, prior to this study, there was not prior research involving Tuckman’s group development model and LSS team outcomes.

Agile software development helps software producing organizations to respond to manifold challenges. While prior research focused on agility as a project or process phenomenon, the authors suggest that agility is an emergent phenomenon on the team level. The paper aims to discuss this issue.

Using the theory of complex adaptive systems (CASs), the study captures the multiple influencing levels of software development teams (SDTs) and their interplay with self-organization and emergence. The authors investigate three agile SDTs in different contextual environments that participate with four or more different roles each.

The results suggest self-organization as a central process when understanding team agility. While contextual factors often provide restriction on self-organization, they can help the team to enhance its autonomy.

The theoretical contributions result from the development and test of theory grounded propositions and the investigation of mature agile development teams.

The findings help practitioners to improve the cost-effectiveness ratio of their team’s operations.

The study provides empirical evidence for the emergence of team agility in agile SDTs. Using the lens of CAS, the study suggests the importance of the team’s autonomy.

This case study feature aims to focus on team performance in a global product development environment and endeavors to enable managers and leaders of global teams to benefit from the insight.

The paper outlines a case study conducted in an organizational setting spanning a period of five years. The researchers studied a department consisting of product development team members in an emerging region and report findings in the context of existing concepts.

Based on the case study, it is observed that global product development teams are similar to other teams and are governed by structure, task, leadership and team processes. The distance and culture aspect of global teams tend to have additional challenges. Some of these challenges can be mitigated by enabling a robust team design, the right team composition, common processes, alignment with structure, focused training and development, consistent performance and evaluation mechanisms, as well as implementing knowledge management systems and having senior management support.

Usage of global teams for product development is rapidly increasing and the understanding of team performance is critical for their success. This case study is based on an actual product development team engaged over a period of five years. The insights gathered provide a practical perspective of global team functioning that can be used for further exploration and research.

The case study findings can be used by practicing managers, leaders of global teams and organizations to help them understand various factors and implications that may reduce global team challenges in a product development scenario. Some of the best practices suggested in the study may help those creating a global team.

The case study illustrates some of the practical aspects of a global product development function. The approach into examining the functioning of a working team over a period of time helps provide a valuable and coherent view of a complex phenomenon. The factors uncovered during the study help provide a basis for further research.

Reports on the experience of production team leaders and their line managers on the quality of training and development of the former. The setting was the UK plant of a US‐based global organization competing in the telecommunications technology sector. Team leaders’ and line managers’ views were complemented with data from personnel records. The findings suggested that team leaders’ development was perceived to be inadequate in both the technical and leadership domains. Team leaders perceived deficiencies in their technical training and competence; and line managers viewed that team leaders lacked managerial and leadership skills. The analysis of personnel records corroborated those views as it suggested that existing training and development structures were not being properly implemented or designed. This situation can impact unit performance. Suggestions regarding rectification of such situations are made.

By combining the influence tactics and team development literatures, this paper aims to propose a new team-level approach to influence tactics in self-managed teams and a temporal account of the extent to which team-level influence tactics are associated with team performance as a dynamic process.

Using 75 self-managed teams, we examined the relationship between the proportion of team members who tend to use each influence tactic to a high degree and team performance at initial versus advanced stages of team development.

Results demonstrated at initial stages of team development, a high proportion of team members who tend to use assertiveness was detrimental to team performance, whereas at advanced stages of team development, a high proportion of team members tending to use ingratiation was detrimental, while rationality was positively associated with team performance. Additionally, a Fuzzy Qualitative Comparative Analysis showed that at advanced stages of team development, tactics configuration matters.

This study sets the stage for a team-level theory of influence tactics by examining the relationship between the proportion of team members who tend to use influence tactics to a high degree and team performance at initial versus advanced stages of team development, and the configurations of tactics associated with better team performance at these developmental stages. While the individual-level literature on influence tactics is based on notions of power and politics, in a team context and specifically with self-managed teams, there is a need to integrate theories of team processes and dynamics to understand how influence tactics are associated with performance.

The purpose of this paper is to examine the effect of team learning processes (information acquisition, information processing and information storage and retrieval) on team performance in software development projects and to assess the effect of ethical leadership and its influence on these processes.

The authors examined 354 software development project teams in Thailand. A quantitative study was conducted through a Web-based survey, with structural equation modelling used to test the hypotheses.

The results of this study revealed that ethical leadership is positively correlated with the team learning processes of information acquisition, information processing and information storage and retrieval. However, only information processing and information storage and retrieval are positively related to team performance. The results indicate that ethical leadership has a positive direct effect on team performance. The results also show that the positive relationship between ethical leadership and team performance is partially mediated by team learning processes, namely, information processing and information storage and retrieval.

This study highlights the importance of ethical leadership and guides managers towards considering the characteristics of both ethical leadership and team learning processes for enhancing team performance in software development projects.

This is the first study to the best of authors’ knowledge to examine the role of team learning processes in mediating the relationship between ethical leadership and team performance, particularly concerning software development projects. The present research contributes to the literature on team performance management, emphasising the manner in which ethical leadership can result in team learning and team performance. The findings of this study can be used to encourage organisations to develop ethical leadership behaviours and team learning processes in software development projects.

Working as a consultant in the field of team development, I frequently find myself at odds with people who have different perceptions about the nature of the work. This confusion was actually expressed in print when in 1980, following the publication of my article on team problem diagnosis, another consultant wrote of his “simpler” method. This turned out to be the “LIFO” system. Again, similar misunderstanding arose in 1982, within a large client organisation in the public sector. The client had undergone major reorganisation, and it had been decided to create an internal consultancy role, a central function of which was to be team development. I was engaged to train those appointed to the role, with emphasis on the skills required by internal consultants. It came as some surprise therefore to be told during a seminar with some of the organisation's directors, that “team building” had recently been conducted in the area concerned. I had not yet trained the internal consultants. It emerged of course that their “team building” and my “team development” were entirely different processes. Impatient to “get things moving”, the organisation had initiated a programme of “team‐building” activity based on packaged exercises, mainly concerned with the analysis of management style.