Responsibility and lecturer: Markus Tiede
Version: 1.0.2
Module name and abbreviation |
Open Source Software Management (EOSS) |
Responsible institute / section |
Institut Public Sector Transformation (IPST), Digital Sustainability Lab |
Course of study |
Bachelor of Science Wirtschaftsinformatik (BWI) |
Module level additive |
Advanced level |
Semester |
3rd semester full-time, 4th semester part-time |
ECTS-Credits |
3 ECTS-Credits |
Language |
verbal: german; content & material: english |
Target Group |
primarily for BWI-students |
Short Description |
This module covers the foundation and concepts for building effective open source practices in companies and organizations. The focus is on the following phases: - Using open source software These three key stages are embedded in strategic considerations, governance processes and implementation. |
Long Description |
In the first section, you will learn the basic components of open source and open standards. You will also learn about the differences between open source and closed source software, the reasons for the use of each, and how the combination of standards and open source provides increased value to an organization. The second section discusses the various open source business models and how to develop practical strategies and policies for your organization’s chosen model. It also explains the value and importance of an Open Source Program Office (OSPO) as well as how the OSPO helps provide assistance in defining ROI and other open source metrics. In the third section, you will learn how to build an effective OSPO and articulate the different types of roles and responsibilities needed to run it successfully. Section 4 talks about the role of continuous integration and testing in a healthy open source project, and how you can apply open source development principles to internal projects within your organization to take best advantage of the value these principles bring. In the fifth section you will learn about the importance of effective open source license compliance and how to build programs and processes to ensure safe and effective consumption of open source in the enterprise. You will also get familiar with the most common open source license types, and their major characteristics, as well as how to choose the most appropriate license for a given situation. Section 6 discusses how to work most effectively with upstream open source projects and how to build sound contribution strategies in organizations to get the maximum benefit from working with project communities. It also describes multiple common upstream project governance models, and explains how these governance practices affect an organization’s ability to make effective contributions. Finally, the last section discusses the rationale and value for creating new open source projects as well as the required legal, business and development processes needed to launch new projects. |
Schedule & Structure |
Block of 4 lessons every 2 weeks Week 1: Open Source Introduction Week 3: Open Source Business Strategy Week 5: Effective Open Source Program Management Week 7: Open Source Development Practices Week 9: Open Source Compliance Programs Week 11: Collaborating Effectively with Open Source Projects Week 13: Creating Open Source Projects Case Studies Collaboration |
Teaching and learning methods |
On-site, hybrid and remote lectures combined with ~30+ tasks Self study: |
Literature |
https://digital-sustainability.github.io/module-eoss-ospo101/ |
Entry requirements |
Professional skills BFH-W competency model: |
Competencies upon completion |
Professional skills BFH-W competency model Agile methods Collaboration Self Organization Handling complexity |
Follow-up modules |
- module/wseg - Software Engineering |
Competency assessment* |
Exam (60%) at the end of the module Tasks (40%) |
Aids for written examination |
- Summary (max 10 single or 5 double pages) |
Comment |
All contents are available here https://github.com/digital-sustainability/module-eoss licensed under CC-BY 4.0 as OER. |
Das Modulkonzept dient dem gemeinsamen Verständnis aller an einem Modul Beteiligen bezüglich Inhalte, Didaktik und Tools. Es ist das zentrale Dokument beim Aufbau und bei Überarbeitungen von Modulen. Darüber hinaus hat es aber weitere Zielgruppen:
-
Dozierende/WMAs anderer Module: zum Aufbau und zur Abgrenzung von eigenen Modulinhalten, zum Angebot eines ausgewogenen Mixes von didaktischen Methoden sowie für einen koordinierten Einsatz von Tools
-
Studiengangsleitende: für die Kenntnis von Ansprechpartnern sowie zur Koordination von Modulinhalten, Didaktikvielfalt und Tooleinsatz
-
Instituts-, Abteilungs- und Fachgruppenleitende: zur Festlegung der Zuständigkeiten, für organisationsübergreifende Zusammenarbeit sowie zur Förderung von Themen der jeweiligen Organisationseinheiten
Die Studierenden sind keine direkte Zielgruppe des Modulkonzepts. In der Regel werden Ihnen nur Auszüge aus dem Konzept zur Verfügung gestellt; diese werden in die Modulbeschreibung auf IS-Academia übertragen. Die einzelnen Blöcke der Modulbeschreibung in IS-Academia sollen möglichst direkt aus dem Modulkonzept übernommen werden.
Das Modulkonzept wird im Rahmen des Neuaufbaus eines Moduls erstellt und bei Überarbeitungen angepasst. Zu jedem Zeitpunkt soll eine aktuelle Version verfügbar sein.
Die in der Vorlage zum Modulkonzept enthaltenen Blöcke sind Pflichtbausteine, zusätzliche Blöcke sind möglich. Diese sollen direkt im Konzept und nicht in separaten Dokumenten ergänzt werden.