The Cost of Problem-Based Learning: An Example in Information Systems Engineering

TL;DR

This paper evaluates the implementation of Problem-Based Learning in a Masters in software development, highlighting its benefits and the significant costs associated with setup and scenario development.

Contribution

It provides an analysis of the costs involved in adopting PBL in information systems engineering education, an area with limited prior focus on economic aspects.

Findings

PBL improves student engagement and skills.

Setup and scenario development are costly.

Initial results show promise despite expenses.

Abstract

High-quality education helps in finding a job - but student skills heterogeneity and student reluctance to move towards a professional attitude are important barriers to employability. We re-engineered some of the technical courses of a Masters in software development using a Problem-Based Learning (PBL) approach. Although initial results are encouraging, the cost of using PBL must be taken into account. Two aspects are particularly expensive: (i) set-up of the software development practicum, a mid-sized information system and its environment; (ii) screenwriting of problem-based learning scenarios, including procurement of input artefacts.