Agile Methoden
Im Februar 2001 wurde das Agile Software Development Manifesto verabschiedet. Siebzehn freie Denker und Vertreter von verschiedenen, damals „leichtgewichtig“ bezeichneten neuen Software-Entwicklungs-Methoden wie XP, Scrum, Crystal und weiteren kamen zusammen, um als „Agile Alliance“ eine gemeinsame Sicht auf die Alternativen zum traditionellen planungs- und dokumentationsgetriebenen Softwareprojektmanagement zu formulieren. Das Ergebnis ist das Agile Manifesto, eine Sammlung von gemeinsam Ideen und Wertvorstellungen zu agiler Software-Entwicklung(vgl. [Highsmith, 2001]).
Das Agile Manifesto lautet im englischen Original wie folgt:
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more. [Cunningham, 2001]
Das Agile Manifesto richtet sich dabei nach den folgenden zwölf Prinzipien [Cunningham, 2001]:
1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity - the art of maximizing the amount of work not done - is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
Dieses Manifest als gemeinsamer Nenner agiler Methoden rückt also das Individuum, Einfachheit, Flexibilität, enge Kundenbeziehungen und vor allem ein funktionierendes Endprodukt in den Vordergrund. Es erweckt den Eindruck eines sehr pragmatischen und praktischen Zuganges. Dieser Anspruch wird im nächsten Kapitel durch genauere Betrachtung einer sehr verbreiteten Agilen Methode überprüft: Scrum.
Letzte Änderung: 08.11.2010, 12:05 | 404 Worte