Logo des Repositoriums

Auflistung nach Schlagwort "Agile Software Development"

1 - 6 von 6
  • Konferenzbeitrag
    Agile Software Quality Function Deployment
    (Software Engineering und Software Management 2018, 2018) Schockert, Sixten; Herzwurm, Georg
    User Stories repräsentieren das wesentliche Artefakt der Kommunikation von Anforderungen in einer agilen Entwicklung. Und unabhängig davon, ob sie sich als präzise Anforderungen für die Entwickler eignen, auf Basis der User Stories im Product Backlog wird entschieden, was in der nächsten Iteration umgesetzt wird und was nicht. Von daher muss ein Agiles Requirements Engineering Wege aufzeigen, gute User Stories zu finden, zu entwerfen und die gemäß Business Value vielversprechendsten für die Implementierung in der nächsten Iteration auszuwählen. Das ist entscheidend für eine nicht nur effiziente, sondern auch effektive agile Entwicklung, die an den wichtigsten Anforderungen ansetzt und nicht „nur“ plausible User Stories zügig umsetzt. Dieser Beitrag stellt dazu das Agile Software Quality Function Deployment (QFD) vor. Es basiert auf 27 Gestaltungsanforderungen, abgeleitet aus den Prinzipien und Werten der agilen Softwareentwicklung, dem Umgang mit Anforderungen in agilen Entwicklungsmodellen und empirischen Quellen des agilen Requirements Engineering. Den Vorschlag zum Agilen Software QFD kennzeichnen die nahtlose Einbettung in den agilen Iterationszyklus und besondere methodische Merkmale wie die inkrementell wachsende Priorisierungsmatrix und die Priority Map. Bewertet gegen die Gestaltungsanforderungen und verglichen mit weit verbreiteten Techniken des agilen Requirements Engineering kann das Agile Software QFD durch die konsequente Ausrichtung an den wichtigsten Stakeholderbedürfnissen, der Suche nach alternativen und besseren Lösungen sowie der engen Zusammenarbeit mit den Kunden/Nutzern einen Mehrwert für die agile Entwicklung darstellen. Agiles Software QFD verkörpert damit den Gestaltungsanspruch des Requirements Engineering in einer agilen Softwareentwicklung und ist Ausdruck eines am Business Value orientierten agilen Requirements Engineering.
  • Konferenzbeitrag
    Attitudes, Beliefs, and Development Data Concerning Agile Software Development Practices
    (Software Engineering 2020, 2020) Matthies, Christoph; Huegle, Johannes; Dürschmid, Tobias; Teusner, Ralf
    This work is a summary of research previously published at the 41st International Conference on Software Engineering: Software Engineering Education and Training in 2019. The perceptions and attitudes of developers impact how software projects are run and which development practices are employed in development teams. Recent Agile methodologies have taken this into account, focusing on collaboration and a shared team culture. In this research, we investigate the perceptions of Agile development practices and their usage in Scrum software development teams. Although perceptions collected through surveys of 42 participating students did not evolve significantly over time, our analyses show that the Scrum role significantly impacted participants' views of employed development practices. We find that using the version control system according to Agile ideas was consistently rated most related to the values of the Agile Manifesto. Furthermore, we investigate how common software development artifacts can be used to gain insights into team behavior and present the development data measurements we employed. We show that we can reliably detect well-defined Agile practices, such Test-Driven Development, in this data and that usage of these practices coincided with participants' self-assessments.
  • Konferenzbeitrag
    Comparing Pre Commit Reviews and Post Commit Reviews Using Process Simulation
    (Software Engineering 2017, 2017) Baum, Tobias; Kortum, Fabian; Schneider, Kurt; Brack, Arthur; Schauder, Jens
    Previous studies found that two variations of change-based code review are used in in- dustry: Pre commit review and post commit review. Which one is better in a given situation is not obvious. So we asked: Are there practically relevant performance differences between pre and post commit reviews? How are these differences influenced by contextual factors? To assess these ques- tions, we designed and validated a parametric discrete event simulation model of certain agile devel- opment processes. Our analysis indicates that the best choice does depend on the context, but also that there are many situations with no practically relevant difference between both choices. We iden- tified the main influencing factors and underlying effects and condensed our findings into heuristic rules.
  • Zeitschriftenartikel
    Die E-Learning-Plattform W3L
    (Wirtschaftsinformatik: Vol. 46, No. 2, 2004) Balzert, Helmut; Balzert, Heide; Zwintzscher, Olaf
    The acceptance of e-learning depends substantially on three factors: effective learning for the learners, effective providing of authors in producing learning contents and their economical application in enterprises and organizations. Optimal learning requires a representation and a dressing of teaching subjects, which consider the possibilities and boundary conditions of e-learning. In order to reduce arduous reading on the screen, e-learning-contents have to be available as scripts or books for the learners. The e-learning-platform W3L (Web Life Long Learning) realizes these requirements and makes “Blended Learning plus printr” possible. The W3L-Plattform can be acquired under license or used as ASP users.
  • Konferenzbeitrag
    How has SPI changed in times of agile development? Results from a multi-method study
    (Software Engineering 2020, 2020) Küpper, Steffen; Pfahl, Dietmar; Jürisoo, Kristjan; Diebold, Philipp; Münch, Jürgen; Kuhrmann, Marco
    The emergence of agile methods and practices has not only changed the development processes but might also have affected how companies conduct software process improvement (SPI). Through a set of complementary studies, we aim to understand how SPI has changed in times of agile software development. Specifically, we aim (1) to identify and characterize the set of publications that connect elements of agility to SPI, (2) to explore to which extent agile methods/practices have been used in the context of SPI, and (3) to understand whether the topics addressed in the literature are relevant and useful for industry professionals. To study these questions, we conducted an in-depth analysis of the literature identified in a previous mapping study, an interview study, and an analysis of the responses given by industry professionals to SPI-related questions stemming from an independently conducted survey study.
  • Zeitschriftenartikel
    Problembereiche verteilter agiler Teams: Literaturanalyse und Praxisimplikationen
    (HMD Praxis der Wirtschaftsinformatik: Vol. 57, No. 5, 2020) Haslinger, Lukas; Sikora, Hermann; Riedl, René
    Seit Bestehen des Agilen Manifests 2001 bildeten sich vermehrt agile Softwareentwicklungs-Teams, die sich in Aufbau und Funktionsweise voneinander unterscheiden. Viele dieser Teams verteilen sich auf mehrere Standorte. Der Grad der Verteilung kann dabei von „in unterschiedlichen Gebäuden auf einem Firmengelände“ bis hin zu „anderer Kontinent“ reichen. Da das Agile Manifest auf stetige informelle Kommunikation (kurze, unbürokratische Wege) und vergleichsweise wenig Dokumentation setzt, sind bei verteilten Teams Schwierigkeiten und Probleme zu erwarten, wenn die Werte des Manifests konsequent verfolgt werden. Ein verteiltes Softwareentwicklungs-Projekt birgt an sich bereits Risiken (z. B. im Wissenstransfer zwischen den Entwicklern), wobei bei einem verteilten agilen Projekt zusätzliche Probleme auftreten können. Die Fachliteratur befasst sich seit rund 15 Jahren mit dieser Problematik. Befunde empirischer Studien beschreiben verschiedene Problembereiche; zudem werden Lösungswege erläutert. Im gegenständlichen Beitrag wird der aktuelle Stand der Literatur analysiert, um die wichtigsten Problembereiche herauszuarbeiten. Die Beschreibung dieser Problembereiche hilft insbesondere Handlungs- und Entscheidungsträgern in der Praxis, potenzielle Schwierigkeiten verteilter agiler Teams zu erkennen. Dies ist eine wesentliche Grundlage für proaktives Management, um die möglichen negativen Wirkungen zu vermeiden. Since the foundation of the Agile Manifesto in 2001, increasingly more agile software development teams have been formed, which differ in terms of structure and organization. Many of these teams are spread across multiple locations. The degree of distribution can range from “in different buildings on one company site” to “another continent”. As the Agile Manifesto focuses on constant informal communication (short unbureaucratic channels) and comparatively little documentation, difficulties and problems can be expected in distributed teams if one consistently follows the values of the manifesto. A distributed software development project already involves risks (e.g., transfer of knowledge between developers), and additional problems can arise in a distributed agile project. The academic literature has been dealing with this problem for around 15 years. Findings from empirical studies describe various problem areas and solutions are also outlined. The present article analyzes the current state of the literature in order to identify the most important problem areas. The description of these problem areas helps decision-makers in practice to better understand potential difficulties of distributed agile teams. This is an essential basis for proactive management in order to avoid possible negative effects.