Assessing iterative practical software engineering courses with play money

Kai Mindermann, Jan Peter Ostberg, Stefan Wagner

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

1 Scopus citations

Abstract

Changing our practical software engineering course from the previous waterfall model to a more agile and iterative approach created more severe assessment challenges. To cope with them we added an assessment concept based on play money. The concept not only includes weekly expenses to simulate real running costs but also investments, which correspond to assessment results of the submissions. This concept simulates a startup-like working environment and its financing in an university course. Our early evaluation shows that the combination of the iterative approach and the play money investments is motivating for many students. At this point we think that the combined approach has advantages from both the supervising and the students point of view. We planned more evaluations to better understand all its effects.

Original languageEnglish
Title of host publicationProceedings - 5th International Workshop on Green and Sustainable Software, GREENS 2016
PublisherIEEE Computer Society
Pages754-755
Number of pages2
ISBN (Electronic)9781450341615, 9781450342056
DOIs
StatePublished - 14 May 2016
Externally publishedYes
Event2016 IEEE/ACM 38th IEEE International Conference on Software Engineering, ICSE 2016 - Austin, United States
Duration: 14 May 201622 May 2016

Publication series

NameProceedings - International Conference on Software Engineering
ISSN (Print)0270-5257

Conference

Conference2016 IEEE/ACM 38th IEEE International Conference on Software Engineering, ICSE 2016
Country/TerritoryUnited States
CityAustin
Period14/05/1622/05/16

Keywords

  • Finance
  • Iterative
  • Play money
  • Practical course

Fingerprint

Dive into the research topics of 'Assessing iterative practical software engineering courses with play money'. Together they form a unique fingerprint.

Cite this