Background: Software project management activities help to introducing software process models in Software Engineering courses. However, these activities should be adequately aligned with the learning outcomes and support student's progression. 

Objective: Present and evaluate an approach to help students acquire theoretical and practical knowledge and experience real-world software projects' challenges. The approach combines a serious game and a design-implement task in which students develop a controlled-scale software system.

Methods: To evaluate our approach, we analyzed the students' perceptions collected through an online survey, their project plans, and their final reports using thematic analysis.

Results: Results suggest that the approach promotes knowledge acquisition, enables students' progression, reinforces theoretical concepts, and is properly aligned with the course's learning outcomes.

Conclusion: The approach seems to help introducing software process models in Software Engineering courses. Our experience can also be inspiring for educators willing to apply our approach in similar courses.

Context: Backsourcing is the process of insourcing previously outsourced activities. When companies experience environmental or strategic changes, or challenges with outsourcing, backsourcing can be a viable alternative. While outsourcing and related processes have been extensively studied in information technology, few studies report experiences with backsourcing.

Objectives: We intend to summarize the results of the research literature on the backsourcing of IT, with a focus on software development. By identifying practical relevance experience, we aim to present findings that may help companies considering backsourcing. In addition, we aim to identify gaps in the current research literature and point out areas for future work.

Method: Our systematic literature review (SLR) started with a search for empirical studies on the backsourcing of IT. From each study we identified the contexts in which backsourcing occurs, the factors leading to the decision to backsource, the backsourcing process itself, and the outcomes of backsourcing. We employed inductive coding to extract textual data from the papers identified and qualitative cross-case analysis to synthesize the evidence from backsourcing experiences.

Results: We identified 17 papers that reported 26 cases of backsourcing, six of which were related to software development. The cases came from a variety of contexts. The most common reasons for backsourcing were improving quality, reducing costs, and regaining control of outsourced activities. The backsourcing process can be described as containing five sub-processes: change management, vendor relationship management, competence building, organizational build-up, and transfer of ownership. Furthermore, we identified 14 positive outcomes and nine negative outcomes of backsourcing. Finally, we aggregated the evidence and detailed three relationships of potential use to companies considering backsourcing.

Conclusion: The backsourcing of IT is a complex process; its implementation depends on the prior outsourcing relationship and other contextual factors. Our systematic literature review may contribute to a better understanding of this process by identifying its components and their relationships based on the peer-reviewed literature. Our results may also serve as a motivation and baseline for further research on backsourcing and may provide guidelines and process fragments from which practitioners can benefit when they engage in backsourcing.