This website is no longer updated.

As of 1.10.2022, the Faculty of Physics has been merged into the TUM School of Natural Sciences with the website For more information read Conversion of Websites.

de | en

Project Organisation and Management in Software Engineering

Module IN2083

This Module is offered by TUM Department of Informatics.

This module handbook serves to describe contents, learning outcome, methods and examination type as well as linking to current dates for courses and module examination in the respective sections.

Module version of WS 2011/2

There are historic module descriptions of this module. A module description is valid until replaced by a newer one.

Whether the module’s courses are offered during a specific semester is listed in the section Courses, Learning and Teaching Methods and Literature below.

available module versions
SS 2012WS 2011/2

Basic Information

IN2083 is a semester module in German or English language at Bachelor’s level and Master’s level which is offered in summer semester.

Total workloadContact hoursCredits (ECTS)
180 h 60 h 6 CP

Content, Learning Outcome and Preconditions


Among others, the module IN2083 is concerned with the following topics:
- Project Organization
++ Lifecycle model of a Project
++ Types of organizations (Line-, Matrix-and Project-based organizations)
++ Roles and Responsibilities, Management Antipatterns
++ Global Software Projects
++ Organizational Maturity Models (CMM, CMMI)
- Project Plans
++ Software Lifecycle Models
++ Linear Models (Waterfall and V-Model)
++ Iterative models (Spiral, Unified Process, V XT)
++ Agile models (Scrum, Kanban)
++ Estimation
++ Scheduling
- Contracts and Contracting
++ Types of contracts
++ Lifecycle of a Contract
++ Legal issues
- Change Management
++ Configuration Management
++ Continuous Integration
++ Continuous Delivery
- Quality Management
++ Usability Management
++ Testing, V&V
++ Risk Management
++ IEEE Standards

Learning Outcome

After successful completion of the module, participants understand the key concepts of traditional and agile project management techniques and are able to deal with typical software project management problems such as writing a project plan, initiating and managing a small project, tailoring a software lifecycle, developing strategies for merge management, continuous integration or continous delivery. They also are familiar with the most important techniques of risk management, scheduling, planning, testing and delivery and apply them to solve simple problems.


IN0006 Introduction to Software Engineering

Courses, Learning and Teaching Methods and Literature

Courses and Schedule

Learning and Teaching Methods

Lecture, tutorials, in-class exercises, assignments for individual study


Slides and films for each lecture, Moodle


- Bruegge, Dutoit: Object-Oriented Software Engineering: Using UML, Patterns and Java, 3rd Edition, Pearson Education, 2009.
- Kemerer: Software Project Management: Readings and Cases MacGraw Hill, 1997
- Royce: Software Project Management: A Unified Framework Addison Wesley, 1998
- Duvall et al.: Continuous Integration, Addison-Wesley Verlag, 2007
- Schwaber, Beedle: Agile Software Development with Scrum, Addison-Wesley Verlag, 2002
- Kevin Aguanno (Ed), Managing Agile Projects, Multi-Media Publications Inc., 2005
- Tapscott, Williams: Wikinomics, Portfolio Verlag, 2006
- Dutoit, McCall, Mistrik, Paech: Rationale Management in Software Engineering, Springer Verlag, 2006.
- Broy, Kuhrmann: Projektorganisation und Management im Software Engineering, Springer, 2013.

Additional readings will be made available at the beginning of the class. Literature for specific topics will be announced at the end of each lecture.

Module Exam

Description of exams and course work

Type of Assessment: exam
The exam takes the form of a 90 minutes written test. Knowledge questions assess the acquaintance of the students about typical software project management problems. Problem tasks assess the ability to describe management problems such as scetching a software plan, designing a configuration management plan, a branching model or a relese plan. By scetching these plans and models the students demonstrate that they have understood the principles of software project management and are able to apply these.

Exam Repetition

The exam may be repeated at the end of the semester.

Top of page