At the university, we often experience a tension between trying to teach agile software product development and the limited and clearly defined time that students have to work on a software product. Even in our longest course, which implements software for external clients, there is only a little time to deal with maintenance issues or even to get feedback on the product in use. As a result, our students are still trained in a more project-oriented way, rather than gaining hands-on experience in the sustainable development of software products. Never experiencing real maintenance issues (e.g., the software being hard to understand and modify, dealing with regression bugs, etc.) makes it hard for them to understand the value of proven agile practices that would lead to better maintenance. Therefore, we would like to discuss and explore with you how to teach students in a practical and realistic way the skills needed to build sustainable, maintainable, and extensible software that delivers value while maintaining the required quality and ensuring a smooth handover to the customer.