A Case Study: GQM and TSP in a Software Engineering Capstone Project

  • Authors:
  • Brian R. von Konsky;Michael Robey

  • Affiliations:
  • Curtin University of Technology;Curtin University of Technology

  • Venue:
  • CSEET '05 Proceedings of the 18th Conference on Software Engineering Education & Training
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

This paper presents a case study, describing the use of a hybrid version of the Team Software Process (TSP) in a capstone software engineering project. A mandatory subset of TSP scripts and reporting mechanisms were required, primarily for estimating the size and duration of tasks and for tracking project status against the project plan. These were supplemented by metrics and additional processes developed by students. Metrics were identified using the Goal-Question-Metric (GQM) process and used to evaluate the effectiveness of project management roles assigned to each member of the project team. TSP processes and specific TSP forms are identified as evidence of learning outcome attainment. The approach allowed for student creativity and flexibility and limited the perceived overhead associated with use of the complete TSP. Students felt that the experience enabled them to further develop and demonstrate teamwork and leadership skills. However, limited success was seen with respect to defect tracking, risk management, and process improvement. The case study demonstrates that the approach can be used to assess learning outcome attainment and highlights for students the significance of software engineering project management.