Software governance using retrospectives: A case study

Yael Dubinsky, Orit Hazzan

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

In this paper we present our study on the implementation of the retrospective practice in software development projects. Specifically, we describe the retrospective practice and present its impact on the development process of a specific large-scale project. Our study shows that a team can steer its process evolution systematically by retrospectives, identifying process issues, discussing their nature, and deciding on mechanisms for their improvement. For the purpose of our research, we use five process elements: work procedures, policies, metrics, roles, and decision rights. Based on the data analysis of the retrospectives conducted in our case study, we illustrate each category and demonstrate how it is refined along the project timeline. We suggest using the retrospective practice as a qualitative data gathering tool that assists the governance process of a development project.

Original languageEnglish
Title of host publicationProceedings - 2012 IEEE International Conference on Software Science, Technology and Engineering, SWSTE 2012
Pages40-45
Number of pages6
DOIs
StatePublished - 2012
Externally publishedYes
Event2012 IEEE International Conference on Software Science, Technology and Engineering, SWSTE 2012 - Herzlia, Israel
Duration: 12 Jun 201213 Jun 2012

Publication series

NameProceedings - 2012 IEEE International Conference on Software Science, Technology and Engineering, SWSTE 2012

Conference

Conference2012 IEEE International Conference on Software Science, Technology and Engineering, SWSTE 2012
Country/TerritoryIsrael
CityHerzlia
Period12/06/1213/06/12

Keywords

  • process lifecycle
  • reflective practitioner
  • retrospectivse
  • software governance

ASJC Scopus subject areas

  • Software

Fingerprint

Dive into the research topics of 'Software governance using retrospectives: A case study'. Together they form a unique fingerprint.

Cite this