Antecedents to Team Performance on Student IT Projects

A study was performed to test the impact of factors suggested by social capital and social cognitive theories as important antecedents to team performance on information technology (IT) course projects. Specifically, the impact of personal outcome expectations and social interaction ties on the quality and quantity of knowledge sharing is examined; then, the impact of the quality and quantity of knowledge sharing on team performance is analyzed. The analysis is performed using the partial least squares approach to structural equation modeling. The results indicate that personal outcome expectations significantly impact knowledge sharing while no evidence was found for a relationship between social interaction ties and knowledge sharing. Additionally, both the quantity and quality of knowledge sharing were found to have significant positive effects on team performance

Understanding the role of knowledge management in software development: a case study in very small companies

Software and systems engineering is distinct from other forms of engineering as it deals with an intangible product, where the progress in construction is not explicitly visible and team members often rely on the docu- mentation of others to follow and review progress. Furthermore unlike traditional engineering disciplines, there is no single standardized unified process. The role of knowledge management in the software engineering literature is becoming more evident, as the software development activity is essentially a human knowledge intensive activity and is seen by many as a key factor. This paper discusses the role of software development knowledge management within software development process and specifically how software development knowledge is managed in software development in order to support software process improvement and the role of knowledge management in this. The authors present the results of a study of knowledge management process practices in very small software companies and discusses these under the major identified issues of: Communication; Learning and sharing; Documentation and Knowledge management process and com- mitment. The findings in this study give an insight towards knowledge management practices as they relate to software development process practices in very small companies and the important factors that must be considered to preserve knowledge and quality software

Agile software development in large-scale new product development organization: team level perspective

Many modern intelligent products and systems (e.g., automotive, consumer electronics, telecommunications) contain more and more embedded software. Often the new product development (NPD) companies developing such products operate under turbulent circumstances stemming from the business environment, technology development and other, even disruptive sources. The embedded software development functions of such NPD organizations then face the uncertainties directly or indirectly, often coupled with time-to-market, quality and productivity pressures. Agile software development has been advocated as a new way of coping with such circumstances in particular with small independent teams developing customer-driven software products. This thesis investigates in contrast how it can be utilized with embedded software development teams in large-scale market-driven industrial NPD context. The exploratory, problem-driven research process is based on interpretive design science and action research principles. The author worked as a full-time software quality and process development specialist employee inside the case organization, thus acting as a reflective practitioner. The longitudinal study research cycles were conducted over several years in that particular NPD organization context. The cycle viewpoints evolved from first recognizing typical software project problems and uncertainties, and developing certain solutions to software team knowledge management and software process model selection. This development led to consider, what problems current agile software methods address. The realization of agile software development was then further examined with respect to the cost factors, and finally towards integrating agile software product development teams into larger-scale NPD organization. The main result of this research is that agile software development models address many typical key issues in large-scale industrial NPD context, and the cost/benefit factors are in principle justifiable. However, if agile software methods are applied just bottom-up trying to integrate isolated agile software teams into larger organizational context, this inside-out approach leads often to problems with organizational barriers and impediments. Thus, in order to be able to leverage the potential benefits, agile software development should be approached more from the strategic business perspective (outside-in), viewing the software development functions as elements of the total value-creation system in the NPD organization. Different software development (project) teams may have different roles and needs for agility in this complex over time. The contributions imply that rational software team-level improvements require in many cases wider, even enterprise-level perspectives in creating and improving the agile capabilities of the NPD organization. It is thus fundamental to conceptualize agility in the NPD context by combining software development with the overall NPD processes. In particular in large organizations, the improvements may require more actions at the organizational level than in software teams

Software Process Improvement in Very Small Entities: An investigation of Software Development Knowledge Management and Team issues in maintaining and evolving software process and process improvement.

technique at both management and team level in software development VSEs. These methods assisted the researchers in examining the attitude and perceptions of practitioners towards the research issues. The researchers also made use of survey questionnaires in VSEs in order to gain more input and to validate the qualitative data. The findings from the first stage analysis (qualitative analysis), in which the content analysis and grounded theory coding approaches were used, show the pattern and detailed categories that influence and are related with the software process and process improvement in VSEs. These categories are related to each other and allow the researchers to produce and validate the studies theoretical model. Likewise the second stage analysis (quantitative analysis) assisted the researchers in conforming and enhancing the first stage findings. This investigation shows that SPI programmes in VSEs are being undertaken in a very informal manner and also in indirect ways. The primary reasons identified for the informal nature of VSE SPI are due to cost, time, customer and company size, which give a higher priority to the product rather than process. In relation to teams, the small team size coupled with the working and management style have lead VSEs to be more informal in their knowledge management process and team organization. Moreover VSEs are largely ignoring the best practice SPI models. The reasons and acceptance criteria for this are discussed. This research also confirmed that SPI does not solely depend on technology but also the contributions of human aspects have a strong emphasize, especially in VSEs. Therefore a contribution of this research is to provide an extended knowledge and understanding of SPI research area in general and within VSEs domain in particular