Creating high-performing software development teams

Abstract

With software development (SD) constituting one of the largest portions of corporate capital expenditures, an organization's capability to manage the SD process is a key success factor. Additionally, SD is increasingly an important driver of successful technology‐based products as evidenced by the interdependence of software and hardware in telecommunications equipment, computers, medical devices, measurement/monitoring equipment, and industrial controls equipment. Building high‐performing SD teams that utilize state‐of‐the‐art development processes increases the likelihood that firms can compete and meet the ever‐expanding expectations of stakeholders. We first introduce the generic process models of SD and then address a number of major issues that can arise in the course of building highly effective SD teams. We then identify a number of best practices that can improve SD teams, both in terms of technical and intragroup aspects, and the role that senior management can play in reinforcing effective project team behaviors. Finally, we address the concept of capturing learning from SD project teams and advance several areas for future research.

Service innovativeness and the structuring of organizations: The moderating roles of learning orientation and inter-functional coordination

“…The rationale is that an organic structure, with open communication, flexible in administrative relations, nonbureaucratic structural attributes is broadly defined and relies on less formalized jobs. This enables an organization to be more entrepreneurial in nature, which allows organizations to be innovative and respond to market opportunities and environmental challenges in an effective manner (Burns & Stalker, 1961;Pattit & Wilemon, 2005). Covin and Slevin (1988) consider this organic organization structure as a critical part of an entrepreneurial style of leadership.…”

A Scientifically Experimental Approach to the Simulation of Designer Activity in the Conceptual Designing of Software Intensive Systems

“…The indexed copy of the source code is registered in the editor memory, and it is visualized in the area (3). After saving the current state of the source code, its indexed copy transfers (4) to the QA-database (5). At any time, any QA-program from the database can be uploaded to the editor.…”

“…Any new SIS project is evolved through the real-time solution of the technological and subject tasks that are distributed between members of the team [5]. This distribution accounts for the personal experience of any member with real-time access to the collective experience and its models.…”

Managing emergent changes: ad hoc teams’ praxis and practices

“…Change requests have a different meaning to different companies and scholars (e.g. Matheus et al , 2016; Pattit and Wilemon, 2005; Tang, 2015). In the project studied in this paper, the terms and processes were interpreted, primarily, as changes to technical requirements, and subsequent changes to project scope and scheduling.…”