t.BA.IT.PM4.19HS (Software Project 4) 
Module: Software Project 4
This information was generated on: 18 May 2024
Software Project 4
Organised by


Version: 5.0 start 01 February 2024


Short description

Students are able to develop a complex software system using an agile development process – from the initial idea through to the customised solution.

Module coordinator

Andreas Meier (meea)

Learning objectives (competencies)

Objectives Competences Taxonomy levels
You apply the agile principles consistently (individuals and interactions, working software, cooperating with clients, reacting to changes). F,M K3,K4
You apply the agile technical practices effectively (e.g. test-driven development, continuous integration, agile estimating and planning, etc.) F,M K2,K3
You create and maintain the necessary agile artefacts (product backlog, sprint backlog, burndown chart). F,M K2,K4
You implement the agile collaboration practices consistently (e.g. sprint planning, scrum meetings, sprint reviews, backlog refinement). F,M K3,K4
You employ the necessary development and collaboration tools and always keep your data and documentation up-to-date. F K3
You consistently apply the object-oriented design principles (SOLID) and implement them in a suitable architecture. F,M K3 (K4)
Your competences make you an ideal member of an agile team SO K4
You are able to assume the different roles in an agile team, to review them with the other team members and to develop them suitably (self-organizing team). SE K4,K5

Module contents

In teams of seven (±2) and using agile methodology, students complete a software development project from the project outline to the customized software.
  • Project setup: determining product vision (including creating product outline, defining requirements, identifying risks), creating product backlogs, estimating expenses and planning, setting up management and development tools
  • Project implementation in five iterations / two-week sprints 
    • Sprint planning: negotiating sprint backlog entries
    • Sprint implementation: applying agile practices, principles and tools, project management, analysis and design, tests, implementation, integration, deployment, etc.
    • Sprint review and retrospective: demonstrating products, reflecting on process, reacting to changes
    • Backlog refinement: adapting backlog (setting priorities, assigning roles, refining processes), adjusting time estimates and planning)
  • The following content/materials that can/could be used to solicit donations/funds:
    • Project outline with stakeholder analysis
    • Video recorded presentataion
    • Technical article
  • Closing Event: Final presentation and demonstration (during exam period)

Teaching materials

All information relevant to assessment will be made available during contact hours in written form (assignments, templates, etc.) and on occasion orally (inputs).
(Note: German only)

Supplementary literature

cf. module SWEN2
Clean Code, Robert C.Martin, Prentice Hall

Tidy First? A Personal Exercise in Empirical Software Design, Kent Beck, ISBN: 978-1-098-15124-9


This module is closely linked with SWEN2 and must be attended in the same semester.

Teaching language

(X) German ( ) English

Part of International Profile

( ) Yes (X) No

Module structure

Type 4
  For more details please click on this link: T_CL_Modulauspraegungen_SM2025


The lecturer can deviate from the usual rule of "assessment during contact hours" if he/she informs the students of this special module agreement in written form in the first week of the semester.
Name Type Form Frequency Assessment Weighting
Project Setup infrastructure, testing environment, product vision, team organization, product backlog implementation 1 x points 5%
Sprint Procedure application of agile methods and practices, backlog and documentation continually updated.
sprint demo
implementation 5 x points 20%
Sprint Retrospective reflection, reaction to change, self-organization implementation 2 x points 5%
Product assessment / evaluation of results (usability, functionality, code, documentation, test coverage) written form 1 x points 50%
ILC Project outline with stakeholder analysis, video recorded presentation, technical article written form/
1 x points 20%

As is usual for project modules, all assessment is done during contact hours. Instead of taking an end-of-module exam, students give a presentation and a demonstration in the exam period.


For group work, a student’s performance may affect his/her individual grades, i.e. group members might receive different grades.

Legal basis

The module description is part of the legal basis in addition to the general academic regulations. It is binding. During the first week of the semester a written and communicated supplement can specify the module description in more detail.


Course: Software-Projekt 4 - Praktikum
Software-Projekt 4 - Praktikum


  • No module description is available in the system for the cut-off date of 01 August 2099.