2017Unpublished venueRequires access

Team Maturity in Software Engineering Teams

George Marsicano, Diana Valenca Pereira, Fábio Q. B. da Silva, César França

Open publisher page 6 citations

Abstract

Background: In Software Engineering (SE) the term maturity is often linked to the work process and product quality. In many cases, team maturity is seen as a backdrop to the process of SE, and sometimes as something that is known to exist, but which cannot be understood, neither measured accurately nor even dimension its value. Aim: In this article, we seek to understand the concept of mature teams in the context of SE, from the perspective of the software engineers themselves. Methods: We performed an exploratory qualitative research, collecting data from 26 practitioners, from 6 companies in 4 cities in Brazil. Data was analyzed using coding techniques from qualitative research. Results: Our findings pointed out three major dimensions of the concept of Team Maturity - Learning, Relationship and Technical Maturity - which, when kept in balance, can enhance the collective productivity, product quality and also the customer satisfaction. Conclusions: These results extend our current understanding of maturity of SE teams, shedding light on aspects that have been little explored so far in this field. The proposed model can serve as a guide for teams to enhance their approach of teamwork and for future research in this area.

About this research paper

What this paper is about

Background: In Software Engineering (SE) the term maturity is often linked to the work process and product quality. In many cases, team maturity is seen as a backdrop to the process of SE, and sometimes as something that is known to exist, but which cannot be understood, neither measured accurately nor even dimension its value. Aim: In this article, we seek to understand the concept of mature teams in the context of SE, from the perspective of the software engineers themselves. Methods: We performed an exploratory qualitative research, collecting data from 26 practitioners, from 6 companies in 4 cities in Brazil. Data was analyzed using coding techniques from qualitative research. Results: Our findings pointed out three major dimensions of the concept of Team Maturity - Learning, Relationship and Technical Maturity - which, when kept in balance, can enhance the collective productivity, product quality and also the customer satisfaction. Conclusions: These results extend our current understanding of maturity of SE teams, shedding light on aspects that have been little explored so far in this field. The proposed model can serve as a guide for teams to enhance their approach of teamwork and for future research in this area.

Why it matters

OpenAlex reports 6 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Background: In Software Engineering (SE) the term maturity is often linked to the work process and product quality. In many cases, team maturity is seen as a backdrop to the process of SE, and sometimes as something that is known to exist, but which cannot be understood, neither measured accurately nor even dimension its value. Aim: In this article, we seek to understand the concept of mature teams in the context of SE, from the perspective of the software engineers themselves. Methods: We performed an exploratory qualitative research, collecting data from 26 practitioners, from 6 companies in 4 cities in Brazil. Data was analyzed using coding techniques from qualitative research. Results: Our findings pointed out three major dimensions of the concept of Team Maturity - Learning, Relationship and Technical Maturity - which, when kept in balance, can enhance the collective productivity, product quality and also the customer satisfaction. Conclusions: These results extend our current understanding of maturity of SE teams, shedding light on aspects that have been little explored so far in this field. The proposed model can serve as a guide for teams to enhance their approach of teamwork and for future research in this area.

Key concepts: Maturity (psychological), Capability Maturity Model, Teamwork, Knowledge management, Exploratory research, Context (archaeology), Process management, Computer science

Related papers

Back to paper searchBrowse research topicsOriginal source
Team Maturity in Software Engineering Teams — Research Paper | ScholarLens