Search results

Software projects are commonly late and over budget, causing the product to be late to market. Based on questionnaires and field research with software managers in Europe, the USA and Japan, seeks to isolate the management practices that accelerate software development. The results suggest that global differences are not pronounced: Japanese software factories have development processes structured similarly to their US and European counterparts; productivity is also roughly equivalent. To reduce development time, software managers currently achieve greater leverage from the management of people and the cross‐functional process than with the use of CASE tools and technology.

Agile software development is an emerging approach in software engineering, initially proposed and promoted by a group of 17 software professionals who practice a set of “lightweight” methods, and share a common set of values of software development. They consolidated their thoughts, and defined these methods as “agile”. The approaches are based on experiences and best practices from the past by the above‐mentioned group of 17 software professionals. The purpose of this article is to outline the history and evolution of agile software development practices, their principles, and the criticisms as reported by the software development community.

A comprehensive literature review was undertaken to do this research.

Based on the literature review, this paper provides a comprehensive document that helps the practitioners working in the area of the agile software development.

This article will provide comprehensive material for the researchers in the area of agile software development. It will also be very useful for the practitioners practicing software development in the area of agile software development.

The purpose of this article is to examine why US companies outsource software development offshore and to present the factors to be considered to determine if the benefits of offshore outsourcing outweigh the drawbacks. Is offshoring worth it in terms of cost savings and quality? What are the risks associated with offshoring software development, and how can you hedge against such risks? What types of software should be considered for offshoring? How can you recognize the danger signs of offshore work going awry? Are there alternatives to outsourcing software development offshore, or are there alternative ways to offshore? Offshore outsourcing of software development may not be worth the risk in all cases. However, in the cases that it is worth moving offshore, this paper makes suggestions about how to help ensure success. This article presents advantages, disadvantages, risks and alternatives to offshore outsourcing of software development. Also, it provides alternatives for offshore outsourcing that will be useful for any company or individual considering offshore outsourcing.

Increasingly companies recognize that effective and rapid software development – from ideation to delivery – is crucial to achieving competitiveness. This article looks at how leading companies are establishing an enterprise capability for accelerated software delivery to differentiate themselves in the market.

This research looks at how leading software organizations focus on software investments that efficiently and speedily deliver marketplace results.

Successful companies build comprehensive skills in Agile and lean software development methods and for fostering extensive collaboration among business users, IT professionals and customers throughout the software development and delivery lifecycle.

Advanced organizations are more likely to apply more mature development practices, such as service-oriented architecture (SOA) and Agile iterative development methods.

Advanced organizations collaborate much more with customers and business partners to improve software development outcomes.

Discusses problems related to software engineering task maintenance. Argues that since many scientists and practitioners have regarded maintenance as divorced from development, it is not properly embedded in project models. Relates four case studies. Looks at the range of maintenance tasks and strategies. Proposes a change of perspective that would make maintenance part of development. Advocates methods, tools and techniques as possible means of overcoming the problematic situation.

The purpose of this paper is to highlight the importance of alignment at the team level. Because teams are important in software development projects, the paper focuses on studying the influence of alignment between the social and technical capabilities on software development team performance. Drawing on socio‐technical theory and software product development literature, the paper aims to identify social and technical capabilities for software development teams.

Empirical data from 192 software development teams were analyzed. The profile deviation approach was used to calculate alignment.

The findings suggest that misalignment between capabilities negatively impacts product and process performance.

The study provides an intellectually coherent view in studying software development team performance. The study contributes to the literature by assessing alignment needs at the team level.

The study provides a holistic view for studying team capabilities and guides software development team leaders and managers to consider both the social and technical aspects in assessing team performance.

Alignment or misalignment is mostly studied in the literature from a macro level/organizational perspective. There exists a gap in the literature for studying alignment at more granular levels such as between various business sub‐units or within teams. The study addresses the gap by studying alignment within teams.

This study seeks to determine factors that encourage post‐meeting work activity in a software development group by assessing attendee diversity (functional, staffing and tenure), meeting size, and meeting history.

One year's worth of meeting data from a software development group in a US‐based financial services company were collected and analyzed. A binary logistic regression analysis was utilized to determine the impact of diversity, meeting size, and meeting history on the likelihood of post‐meeting work activity.

Tenure diversity and meeting history for each meeting event significantly contribute to the likelihood of post‐meeting work activity.

A lack of variance in the data does not allow for the examination of staffing diversity. Further, generalizability of findings is limited since data come entirely from one organization. Findings suggest that meeting characteristics, specifically tenure diversity and meeting history, can improve the likelihood of post‐meeting work activity occurring.

Findings illustrate that management can leverage tenure diversity and meeting history within a software development group to encourage post‐meeting work activity.

All organizations employ meetings, and research that clarifies how to extract maximum value from meeting events is critical. This study provides a first step in uncovering specific meeting characteristics which are most likely to impact post‐meeting work activity.

Packaged software companies evolve in an environment characterized by ever‐shorter product life cycles and ever‐increasing competition. Reaching the marketplace first is often the way to gain a competitive advantage. This situation leads many packaged software organizations to change both their (often sequential) software development processes and rely on (often cross‐functional) teams. Reports on the software development practices of Software Corp., an organization developing software products for the travel industry, which experimented with several different approaches and finally implemented cross‐functional development teams. Data presented show that changes in the software development process deeply affect many aspects of the organization. The conclusions emphasize the importance of considering the work culture and organizational history when implementing a new software development method and highlight the importance of clearly defining the roles and responsibilities of all groups involved and the necessity to modify the company’s performance‐appraisal system to promote and support the new organizational objectives embodied in the changes in software development methods.

The purpose of this paper is to improve the understanding of the role of the bottlenecks in the dynamic software development supply chains. The paper examines the effects of the task priorities in the software development and investigates the possible strategies to manage them effectively.

In this paper, a software development supply chain has been simulated. This includes modeling of the various sizes of software requirement, different priorities, variations in development times, quality defects, etc. The model assumes a fixed set of resources of various skills. The model is studied for the bottlenecks, throughput, work in progress (WIP), etc. under various work preemption scenarios.

The results indicate that job priorities impact the bottleneck formulation, throughput and WIP of the software development. The work interruption policies to accommodate priority jobs adversely impact the throughput. Selective introduction of interruptions by leaving the bottlenecks from interruptions helps balancing the throughput and priorities.

The impact of the learning curve and knowledge acquisition time needed by the resources to restart the interrupted work has not been considered in this paper, which can be a future area of research.

The paper helps the practicing managers evaluate the dynamics of the bottlenecks with various task management approaches and comprehend the possible tradeoffs between priority and throughout.

The paper looks at software development from a perspective of workflow dynamics. This is a pioneer effort, as it utilizes simulation and modeling approach in understanding the software supply chains better.

ISO 90003 provides guidelines for applying ISO 9001 to software development processes. The purpose of this paper is to present how the software development process in large, virtual teams (LVTs) can be managed, so that they are in compliance with ISO 9001.

The firm's actions are described in a case example format that illustrates how fit between theory and practice is achieved; and forms a precursor to the derivation of appropriate research arguments.

The steps presented show the application of ISO 90003 guidelines to software development planning activities in LVTs, to meet the requirements of ISO 9000 certification.

The scope of this paper is limited to the application of Section 7.3 (Design and development) of ISO 90003:2004 to the software development process. The paper presents the discussion in a “generalized” fashion so that the steps described can be implemented by any software development company.

The implications for managers in this study lie in the presentation of a set of steps to manage software development processes in LVTs, so that they are in compliance with ISO 9001.

There is a dearth of studies on the application of process‐based approaches in virtual organizations. This paper addresses this gap in the literature by examining how software development processes in virtual organizations (specifically, LVTs) may be formally managed, so that they are in compliance with ISO 9001.