SWT II - Agile Software Development in Large Teams
Scaling Agile Development
In Software Engineering 2, you will learn how to manage a long-running software project with a large number of developers. We want to prepare you for a situation where you are in a leading position and responsible for a large piece of software. Thus, you shall learn methods, concepts, and technologies that help you to successfully deliver large software developed by multiple teams.
While still not on par with large enterprise projects, SWT2 is the only lecture in the curriculum that allows you to gain experience in a setting larger than in the bachelor's project.
Participants will be forming teams of 5-8 people. All teams will work collaboratively on the same software, handling all tasks from requirements engineering to design and implementation.
This year, we are happy to have HPI student clubs as a customer for the project, as you will develop a system to manage the application process for workshops and events held at the HPI.
We will teach you how to apply the Scrum methodology in a multi-team setting. Over the course of the semester, you will conduct 4 sprints à 2-3 weeks. The theory taught in the lecture can be applied directly in the accompanying exercise. This course focuses more on the methods and concepts and less on the actual result. The project is hosted on Github and will be available as an open-source project after the course closes.
If the number of participants is too low (i.e., < 10 people), only a single development team will be formed and focus will shift towards scalability of the developed application.
After this course, all students should have
- experience with Scrum and all of its artefacts and meetings
- learned how to scale Scrum over multiple collaborating teams
- the ability to use BDD and TDD where appropriate
- confidence with branching and merging in a source code management (SCM) system
- experienced the value of continuous integration (CI)
- learned to critically self-assess their role in a team
The final grading is determined by
- 30%: oral exam (written exam if the number of participants is unexpectedly high)
- 45%: usage of presented methods and concepts such as Scrum, BDD, TDD, SCM, and CI (team mark)
- 25%: software development results (team mark)
Completion of the introductory exercise is mandatory for passing the course.
If work is not distributed equally amongst team members, individual adjustments of the marks are possible.