RadGrad is a curriculum initiative implemented via a web-based application that combines features of social networks, degree planners, and serious games. RadGrad redefines the traditional meaning of "progress" and "success" in the undergraduate computer science degree program, with the ultimate goal of improving student engagement, diversity, and retention. In this paper, we relate RadGrad to other curriculum initiatives, overview its key functionality, present results from an evaluation conducted during its first year of deployment, and discuss our lessons learned and future directions.

Pedagogues such as the Personal Software Process (PSP) shift metrics definition, collection, and analysis from the organizational level to the individual level. While case study research indicates that the PSP can provide software engineering students with empirical support for improving estimation and quality assurance, there is little evidence that many students continue to use the PSP when no longer required to do so. Our research suggests that this "PSP adoption problem" may be due to two problems: the high overhead of PSP-style metrics collection and analysis, and the requirement that PSP users "context switch" between product development and process recording. This paper overviews our initial PSP experiences, our first attempt to solve the PSP adoption problem with the LEAP system, and our current approach called Hackystat. This approach fully automates both data collection and analysis, which eliminates overhead and context switching. However, Hackystat changes the kind of metrics data that is collected, and introduces new privacy-related adoption issues of its own.

After using and teaching the Personal Software Process (PSP)[6] for over four years, we came to appreciate the insights and benefits that it gave us. However, we noticed some general problems with the PSP. First, we started to question the quality of the data we recorded. In 1998, Anne Disney and Dr. Philip Johnson conducted a study to look at the data quality of the PSP data. They found that there are significant data quality issues with the manual PSP[2, 3]. Second, our experiences with industrial partners, management practices, and Robert Austin's book "Measuring and Managing Performance in Organizations"[1] brought to our attention the issue of measurement dysfunction in empirical software process improvement and review data. Essentially, measurement dysfunction means that an organization's goals to improve software development and formal technical review may inadv...

No abstract available.