Scrum is an agile method (framework) that when instantiated can be rather ornate. Most developers, when I talk to them, tell me that when given a choice they would not be doing Scrum. While Scrum may have felt much lighter than the competition back in the nineties, today it weighs in as rather heavy.
Given this, I wanted to reflect on why I still teach Scrum (and have a blog post to point any of my students to).
The project management tool “RPLAN” makes it possible to plan projects efficiently and transparently. The user’s planning effort should be as small as possible. This will be achieved through a smart product which proposes further steps independently to the customer. For this purpose, RPLAN is connected to the web interface “Slack”, automating the planning process using natural language.
Arrow.js supports the user to identify the correlation between multiple contexts and a single file. We score the relation between different resources. As the result the user gets a score, which describes the probability of a connection between these data sets. This service is accessible through a REST call.
A system to test, if new data and code versions for the DB ticket booking system are valid. The system is deployed in a Docker container to be used in a continuous delivery process. The data and code versions are integrated into a VM, given to us by DB Systel, which can get booking requests and replies with the same information the DB booking site would. By validating, if these replies are what we expected, we can detect if the new code has errors a lot faster than before, thus improving overall developing speed of DB Systel.
Over the last few years, we have shifted most of our courses from traditional upfront lecturing to project-based learning. Each course consists of multiple projects with three main stakeholders: students, teachers, and industry. Using AMOS, our “agile methods and open source” software engineering course as the example, we review our course concept and discuss our experiences. We take the perspectives of the three stakeholders in turn: Achieving learning goals and performing meaningful work (students), fulfilling both an educational and an economic mission (university), and receiving a return on time and monetary investment (industry). The perhaps surprising result is that these three perspectives can work together well and make reaching each stakeholder’s goal easier.
Dieser Artikel stellt das AMOS Projektkonzept vor, welches ich in der Informatik-Lehre an der Universität Erlangen-Nürnberg einsetze. Ziel des AMOS Projekts ist es, Studierenden professionelle Softwareentwicklung in einem konkreten Projekt zu vermitteln, welches idealerweise zu einer Startup durch die am Ende ihres Studiums befindlichen Studierenden führt.
Das AMOS Projekt ist für mich eine neue Erfindung: Ich habe es das erste Mal 2010 so abgehalten. Deswegen dient dieser Artikel nicht nur der Schilderung des Projektkonzepts, sondern sollte auch als Aufforderung zum Kommentieren gelesen werden. Ich vermute, dass es anderswo in ähnlicher Form betrieben wird und würde gern von den dortigen Erfahrungen lernen.