Process support for distributed team-based software development workshop

2001 ◽  
Vol 26 (6) ◽  
pp. 31-33 ◽  
Author(s):  
Pierre F. Tiako ◽  
Tim Lindquist ◽  
Volker Gruhn
Keyword(s):  
Software Development ◽  
Process Support ◽  
Distributed Team

Teaching Globally Distributed Software Development (DSD)

2012 ◽  
pp. 1475-1491
Author(s):  
Stuart Faulk ◽  
Michal Young
Keyword(s):  
Software Development ◽  
Collaborative Teaching ◽  
Team Approach ◽  
Distributed Software Development ◽  
Distributed Software ◽  
Teaching Community ◽  
Distributed Team ◽  
Future Work ◽  
Globally Distributed ◽  
Firsthand Experience

This chapter describes an approach to building a collaborative teaching community that seeks to address these problems. It begins by identifying the skills students should acquire in a Distributed Software Development (DSD) course and discusses why firsthand experience with DSD problems is essential to learning them. The chapter identifies the attributes that make DSD project courses difficult to develop or teach, and then it describes a distributed team approach to developing a reusable infrastructure and a teaching community to address those difficulties. Future work focuses on building an international community of educators and industry participants interested in partnering to develop and teach DSD courses.

Offshore Vendors’ Software Development Team Configurations

2011 ◽  
Vol 19 (3) ◽  
pp. 1-29
Author(s):  
Suranjan Chakraborty ◽  
Saonee Sarker ◽  
Sudhanshu Rai ◽  
Suprateek Sarker ◽  
Ranganadhan Nadadhur
Keyword(s):  
Software Development ◽  
Distributed Teams ◽  
Team Members ◽  
Development Team ◽  
Configuration Theory ◽  
Home Location ◽  
Distributed Team ◽  
Different Types ◽  
The One ◽  
Off Shoring

This research uses configuration theory and data collected from a major IT vendor organization to examine primary configurations of distributed teams in a global off-shoring context. The study indicates that off-shoring vendor organizations typically deploy three different types of configurations, which the authors term as thin-at-client, thick-at-client, and hybrid. These configurations differ in terms of the size of the sub-teams in the different distributed locations and the nature of the ISD-related tasks performed by the distributed team members. In addition, the different configurations were compared on their inherent process-related and resource-related flexibilities. The thick-at-client configuration emerged as the one that offers superior flexibility (in all dimensions).However, additional analysis also revealed contingencies apart from flexibility that may influence the appropriateness of the distributed ISD team configuration, including the volatility of the client organization’s environment and the extent to which the ISD tasks can be effortlessly moved to the vendor’s home location.

Differentiated Process Support for Large Software Projects

2009 ◽  
pp. 1-20
Author(s):  
Alf Inge Wang ◽  
Carl-Fredrik Sørensen
Keyword(s):  
Software Development ◽  
Software Projects ◽  
Individual Group ◽  
Development Organization ◽  
Process Support ◽  
Development Processes ◽  
Large Software ◽  
Organizational Levels ◽  
Different Levels ◽  
Project Level

This chapter presents a framework for differentiated process support in large software projects. Process support can be differentiated in different levels based on the size of the development organization and the need for coordination across different levels of the organization. We have defined four main perspectives: individual, group, team, and project level, where the framework consider essential issues when planning and executing the software development processes in organizations with different levels of management. Further, a guideline is provided that suggests what is required of process support in the various organizational levels.

Differentiated Process Support for Large Software Projects

2009 ◽  
pp. 2359-2378
Author(s):  
Alf Inge Wang ◽  
Carl-Fredrik Sørensen
Keyword(s):  
Software Development ◽  
Software Projects ◽  
Individual Group ◽  
Development Organization ◽  
Process Support ◽  
Development Processes ◽  
Large Software ◽  
Organizational Levels ◽  
Different Levels ◽  
Project Level

This chapter presents a framework for differentiated process support in large software projects. Process support can be differentiated in different levels based on the size of the development organization and the need for coordination across different levels of the organization. We have defined four main perspectives: individual, group, team, and project level, where the framework consider essential issues when planning and executing the software development processes in organizations with different levels of management. Further, a guideline is provided that suggests what is required of process support in the various organizational levels.

scholarly journals Enriching Software Process Support by Knowledge-Based Techniques

1997 ◽  
Vol 07 (02) ◽  
pp. 185-215 ◽  
Author(s):  
Barbara Dellen ◽  
Frank Maurer ◽  
Jürgen Münch ◽  
Martin Verlage
Keyword(s):  
Software Development ◽  
Software Process ◽  
Process Models ◽  
Support Tool ◽  
Knowledge Based ◽  
Process Support ◽  
Complex Design ◽  
General Complex ◽  
Engineering Environment ◽  
Development Processes

Representations of activities dealing with the development or maintenance of software are called software process models. Process models allow for communication, reasoning, guidance, improvement, and automation. Two approaches for modeling processes and instantiating and managing the process models, namely CoMo-Kit and MVP-E, are combined to build a more powerful one. CoMo-Kit is based on AI/KE technology; it is a support tool system for general complex design processes, and was not been developed specifically with software development processes in mind. MVP-E is a process-sensitive software engineering environment for modeling and analyzing software development processes, and guides software developers. Additionally, it provides services to establish and run measurement programmes in software organizations. Because both approaches were developed independently from one another, major integration efforts had to be made to combine both their advantages. This article concentrates on the resulting language concepts, and their operationalization necessary for building automated process support.

Offshore Vendors’ Software Development Team Configurations

2012 ◽  
pp. 176-204
Author(s):  
Suranjan Chakraborty ◽  
Saonee Sarker ◽  
Sudhanshu Rai ◽  
Suprateek Sarker ◽  
Ranganadhan Nadadhur
Keyword(s):  
Software Development ◽  
Distributed Teams ◽  
Team Members ◽  
Development Team ◽  
Configuration Theory ◽  
Home Location ◽  
Distributed Team ◽  
Different Types ◽  
The One ◽  
Off Shoring

This research uses configuration theory and data collected from a major IT vendor organization to examine primary configurations of distributed teams in a global off-shoring context. The study indicates that off-shoring vendor organizations typically deploy three different types of configurations, which the authors term as thin-at-client, thick-at-client, and hybrid. These configurations differ in terms of the size of the sub-teams in the different distributed locations and the nature of the ISD-related tasks performed by the distributed team members. In addition, the different configurations were compared on their inherent process-related and resource-related flexibilities. The thick-at-client configuration emerged as the one that offers superior flexibility (in all dimensions).However, additional analysis also revealed contingencies apart from flexibility that may influence the appropriateness of the distributed ISD team configuration, including the volatility of the client organization’s environment and the extent to which the ISD tasks can be effortlessly moved to the vendor’s home location.

Teaching Globally Distributed Software Development (DSD)

2011 ◽  
pp. 234-250
Author(s):  
Stuart Faulk ◽  
Michal Young
Keyword(s):  
Software Development ◽  
Collaborative Teaching ◽  
Team Approach ◽  
Distributed Software Development ◽  
Distributed Software ◽  
Teaching Community ◽  
Distributed Team ◽  
Future Work ◽  
Globally Distributed ◽  
Firsthand Experience

This chapter describes an approach to building a collaborative teaching community that seeks to address these problems. It begins by identifying the skills students should acquire in a Distributed Software Development (DSD) course and discusses why firsthand experience with DSD problems is essential to learning them. The chapter identifies the attributes that make DSD project courses difficult to develop or teach, and then it describes a distributed team approach to developing a reusable infrastructure and a teaching community to address those difficulties. Future work focuses on building an international community of educators and industry participants interested in partnering to develop and teach DSD courses.

Sign in / Sign up

Export Citation Format

Share Document