The software-development project success depends on the technical competence of the development team, the quality of its tools and the project-management decisions it makes during the software lifecycle. New requirements, tight delivery schedules and team-member turnaround present the team with challenges. Flexible decision making for effective adaptation to these challenges is an extremely difficult skill to acquire, and even more challenging to teach. Instructors of software-engineering courses involving collaborative project development are often overwhelmed by the task of monitoring the progress of multiple teams and problems in the team's process may go unnoticed until it is too late to be fixed. In this paper we describe our work on analyzing the CVS history of a team project repository to extract information about the nature of the collaboration between the members of a team. This analysis can support the instructor in noticing evidence of potential problems who can then use this information to alert the team. It can also be shown to the team members themselves, so that they become more aware of their process. We evaluate our CVS analysis process with a case study, based on an undergraduate software-engineering course.