Performance Evaluation of Software Development Teams: A Practical Case Study

Paulo Fernandes*, Afonso Sales, Alan R. Santos, Thais Webber

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

Abstract

Software development projects have become a challenge for both industry and academia regarding the performance evaluation of teams. Recently, a Stochastic Automata Networks (SAN) model was proposed as theoretical representation for performance prediction of software development teams. In this paper, we present an exercise of such SAN analytical modeling for a practical case study from an Information Technology company that has multiple sites and different participants' roles and expertises. We present the matching of our model predictions with the actual project observations. Then, we focus our attention on the central entity varying its availability and the level of provided support in order to observe the impact on the participants' performance. We summarize our study with further discussions of numerical results and possible model extensions.

Original languageEnglish
Pages (from-to)73-92
Number of pages20
JournalElectronic Notes in Theoretical Computer Science
Volume275
Issue number1
Early online date21 Sept 2011
DOIs
Publication statusPublished - 27 Sept 2011

Bibliographical note

Funding Information:
1 Authors receive financial support provided by PUCRS-Petrobras (Conv. 0050.0048664.09.9). 2 Corresponding author. The order of authors is alphabetical. 3 Paulo Fernandes is also funded by CNPq-Brazil (PQ 307284/2010-7). 4 Afonso Sales receives grants from CAPES-Brazil (PNPD 02388/09-0). 5 [email protected] 6 [email protected] 7 [email protected] 8 [email protected]

Keywords

  • Analytical Modeling
  • Global Software Development
  • Performance Evaluation
  • Stochastic Automata Networks
  • Team Building Process

Fingerprint

Dive into the research topics of 'Performance Evaluation of Software Development Teams: A Practical Case Study'. Together they form a unique fingerprint.

Cite this