2002Unpublished venueRequires access

Measuring team activities in a process-oriented software engineering course

P.N. Robillard

Open publisher page 12 citations

Abstract

The paper describes a software process that enables the measurements of team activities in a software engineering project course. Observed measurements are presented for three types of team behaviors: full team, sub team and individual. A software process is needed to guide team activities. The generic software process presented is based on IEEE standards and is derived from observing professionals and downsizing their process. It proposes some guidelines and specifies the content of five basic documents. Student team members are required to follow this process and record the time spent on each activity. Observations from these time logs are presented. Student behaviors are analyzed in terms of the time spent on various team activities and on various process activities. The concluding remarks outline salient features of a team oriented project course. This process is designed for teams of six students and can be studied in a regular, one semester session.

About this research paper

What this paper is about

The paper describes a software process that enables the measurements of team activities in a software engineering project course. Observed measurements are presented for three types of team behaviors: full team, sub team and individual. A software process is needed to guide team activities. The generic software process presented is based on IEEE standards and is derived from observing professionals and downsizing their process. It proposes some guidelines and specifies the content of five basic documents. Student team members are required to follow this process and record the time spent on each activity. Observations from these time logs are presented. Student behaviors are analyzed in terms of the time spent on various team activities and on various process activities. The concluding remarks outline salient features of a team oriented project course. This process is designed for teams of six students and can be studied in a regular, one semester session.

Why it matters

OpenAlex reports 12 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

The paper describes a software process that enables the measurements of team activities in a software engineering project course. Observed measurements are presented for three types of team behaviors: full team, sub team and individual. A software process is needed to guide team activities. The generic software process presented is based on IEEE standards and is derived from observing professionals and downsizing their process. It proposes some guidelines and specifies the content of five basic documents. Student team members are required to follow this process and record the time spent on each activity. Observations from these time logs are presented. Student behaviors are analyzed in terms of the time spent on various team activities and on various process activities. The concluding remarks outline salient features of a team oriented project course. This process is designed for teams of six students and can be studied in a regular, one semester session.

Key concepts: Team software process, Software Engineering Process Group, Personal software process, Process (computing), Session (web analytics), Salient, Computer science, Software

Related papers

Back to paper searchBrowse research topicsOriginal source
Measuring team activities in a process-oriented software engineering course — Research Paper | ScholarLens