AMOS Agile Methods and Open SourceModule description #40797 / Version 1
- 9 CP
- Portfolio examination
- Graded
- Winter semester
- English, German
This module description is not valid in the current semester (Winter semester 2026/27).
Current version (v10)
| Module / Version | #40797 / #1 |
|---|---|
| Validity | WS 2016/17 – WS 2016/17 |
| Available language(s) | English, German |
| Credit points | 9 |
| Person responsible for the module | Schieferdecker, Ina |
| Grading | Graded |
| Exam format | Portfolio examination |
| Language(s) of instruction | English, German |
Affiliation
| Faculty | Fakultät IV |
|---|---|
| Institute | Institut für Telekommunikationssysteme |
| Academic chair | 34332300 FG Open Distributed Systems (ODS) |
Contact
| Office | HFT 3 |
|---|---|
| Contact person | Vassiliou-Gioles, Theofanis |
| E-mail address | lehre@ods.tu-berlin.de |
| Website | http://www.ods.tu-berlin.de |
Learning outcomes
The objective of agile software development is to make software development processes more flexible and lean. For that e.g. approaches of team members and their interaction have priority over processes and tools. The project provides agile methods along a concrete software development and helps understanding of
● software products and software development in an industry context,
● methods, in particular Scrum and Extreme Programming,
● pen source software development and its underlying principles, and
● provides practical hands-on experience with a Scrum process and XP technical practices.
● software products and software development in an industry context,
● methods, in particular Scrum and Extreme Programming,
● pen source software development and its underlying principles, and
● provides practical hands-on experience with a Scrum process and XP technical practices.
Content
The AMOS Project teaches agile methods (Scrum and XP) using a concrete development project during the lecture period. Topics covered are:
● Agile methods, related software development processes, and the principles behind them
● Scrum roles, process practices, including product and engineering management
● Technical practices like refactoring, continuous integration, and test-driven development
● Principles, best practices, and tools of open source software development
The project is a software development project in which student teams work with an industry partner who provides the idea for the project. This is a practical hands-on experience. The students learn and apply all three main Scrum roles:
● Product owner and documenter. In this role, a student defines, prioritizes, communicates, and reviews requirements.
● Software developer. In this role, a student estimates their effort for requirements and implements them.
● Scrum master. In this role, a student manages the project success and removes non-technical obstacles (“impediments”).
You can learn more about the course and the schedule through this Google Spreadsheet: https://goo.gl/1YjlU0.
You can get an impression of prior AMOS projects here: http://osr.cs.fau.de/category/teaching/specific/amos/
● Agile methods, related software development processes, and the principles behind them
● Scrum roles, process practices, including product and engineering management
● Technical practices like refactoring, continuous integration, and test-driven development
● Principles, best practices, and tools of open source software development
The project is a software development project in which student teams work with an industry partner who provides the idea for the project. This is a practical hands-on experience. The students learn and apply all three main Scrum roles:
● Product owner and documenter. In this role, a student defines, prioritizes, communicates, and reviews requirements.
● Software developer. In this role, a student estimates their effort for requirements and implements them.
● Scrum master. In this role, a student manages the project success and removes non-technical obstacles (“impediments”).
You can learn more about the course and the schedule through this Google Spreadsheet: https://goo.gl/1YjlU0.
You can get an impression of prior AMOS projects here: http://osr.cs.fau.de/category/teaching/specific/amos/
Module components
Compulsory area
The following courses are mandatory for this module:
| Courses | Type | Number | Frequency | Language | Hours per week | Course catalog |
|---|---|---|---|---|---|---|
| Projekt AMOS | Project | 0432 L 782 | Winter semester | – | 6 | WS 2026/27 (1) ISIS |
Courses in the course catalog
Courses created from the teaching units of this module.
Winter semester 2026/27 (1)
Projekt AMOS (Project) 1
- AMOS - Software Developer Role (Projekt) Termingruppe 1 0432 L 782
Workload and credit points
Projekt AMOS (Project)
| Workload description | Multiplier | Hours | Total |
|---|---|---|---|
| Präsenzzeit | 15 | 6 h | 90 h |
| Vor-/Nachbereitung | 15 | 12 h | 180 h |
| 270 h | |||
The workload of the module adds up to 270 hours. The module therefore comprises 9 credit points.
Description of teaching and learning methods
Die Studierenden werden in Teams von 5-7 Personen eingeteilt. Ein Industriepartner stellt die Anforderungen bereit, welche von den Product-Ownern ausgearbeitet und durch die Softwareentwickler umgesetzt werden. Die verfügbaren Projekte werden per eMail spätestens zwei Wochen vor Projektbeginn vorgestellt.
Der Unterricht erfolgt als vierstündiger Block und besteht aus 90min Vorlesung und 90min begleiteter Übung. Räume für Projekttreffen werden zur Verfügung gestellt, sind aber optional.
Students will be organized into teams of 5-7 people. An industry partner will provide requirements to be worked out in detail by the product owners and to be realized by the software developers. The available projects will be presented by eMail two weeks before the project start.
Class is run as a 4h block and includes a 90min lecture and a 90min coached exercise session. Rooms for project meetings are made available, but are optional.
Der Unterricht erfolgt als vierstündiger Block und besteht aus 90min Vorlesung und 90min begleiteter Übung. Räume für Projekttreffen werden zur Verfügung gestellt, sind aber optional.
Students will be organized into teams of 5-7 people. An industry partner will provide requirements to be worked out in detail by the product owners and to be realized by the software developers. The available projects will be presented by eMail two weeks before the project start.
Class is run as a 4h block and includes a 90min lecture and a 90min coached exercise session. Rooms for project meetings are made available, but are optional.
Requirements for participation and examination
Desirable prerequisites for participation in the courses:
Fortgeschrittene Programmierkenntnisse und Grundlagen des Software Engineerings und des Projekt Managements
Bitte stellen Sie sicher, dass Sie sich drei (!) Wochen vor Beginn der Vorlesungszeit für den Kurs registriert haben, so dass wir sie anschreiben können, um eine Projektzuordnung vornehmen zu können.
Advanced programming skills and basics of software engineering and project management.
To get a chance for a seat in the course, please sign-up at least three (!) weeks before the lecture period. We will then reach out to you to inform you about the available projects and to allocate students to teams.
Bitte stellen Sie sicher, dass Sie sich drei (!) Wochen vor Beginn der Vorlesungszeit für den Kurs registriert haben, so dass wir sie anschreiben können, um eine Projektzuordnung vornehmen zu können.
Advanced programming skills and basics of software engineering and project management.
To get a chance for a seat in the course, please sign-up at least three (!) weeks before the lecture period. We will then reach out to you to inform you about the available projects and to allocate students to teams.
Mandatory requirements for the module examination registration:
This module has no examination requirements.
Completion of the module
| Grading | Graded |
|---|---|
| Exam format | Portfolio examination |
| Language | English, German |
Test elements
| Name | Points/Weight | Category | Duration/Extent |
|---|---|---|---|
| (Ergebnisprüfung/ Deliverable assessment) Rolle Product Owner: Qualität des Produkt-BackLogs sowie Prozessfähigkeit | 20 | Projektabhängig | |
| (Ergebnisprüfung/ Deliverable assessment) Rolle Scrum-Master: Qualität des Impediments-BackLogs sowie Prozessfähigkeit | 20 | Projektabhängig | |
| (Ergebnisprüfung/ Deliverable assessment) Rolle Software Developer: Qualität des Produkts (primär Code) sowie Prozessfähigkeit | 60 | Projektabhängig |
Exam description
Es können insgesamt 100 Portfoliopunkte erreicht werden.
A total of 100 portfolio points can be achieved.
Die Gesamtnote gemäß § 47 (2) AllgStuPO wird nach dem Notenschlüssel 2 der Fakultät IV ermittelt.
The final grade of the module is based on the grading system 2 of Faculty IV (§ 47 (2) AllgStuPO).
A total of 100 portfolio points can be achieved.
Die Gesamtnote gemäß § 47 (2) AllgStuPO wird nach dem Notenschlüssel 2 der Fakultät IV ermittelt.
The final grade of the module is based on the grading system 2 of Faculty IV (§ 47 (2) AllgStuPO).
Duration of the module
The following number of semesters is estimated for taking and completing the module: 1 semester(s).
This module can be started in the following semesters: Winter semester.
Maximum number of participants
The maximum capacity of participants is 20.
Registration procedures
Depending on the specific examination rules a registration via QISPOS or at the responsible examination office might be necessary.
For more information, visit: http://www.qds.tu-berlin.de
For more information, visit: http://www.qds.tu-berlin.de
Recommended reading, lecture notes
Lecture notes
unavailable
Electronic lecture notes
unavailable
Recommended literature
- Manifesto for Agile Software Development. http://agilemanifesto.org/
Assigned programs
This module is not used in any program.
Miscellaneous
Sprache:
Deutsch oder Englisch nach Wahl der Studierenden
Deutsch oder Englisch nach Wahl der Studierenden