Relevant bibliographies by topics / The agile manifesto

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers

Academic literature on the topic 'The agile manifesto'

Author: Grafiati
Published: 4 June 2021
Last updated: 7 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'The agile manifesto.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "The agile manifesto"

1

Hattendorf, Mareike. "Die Aktualität des Agilen." Agile Organisationen – Versuch einer kritischen Bestandsaufnahme 29, no. 1 (June 2021): 93–119. http://dx.doi.org/10.30820/0942-2285-2021-1-93.

Full text
Abstract:
Die Anwendbarkeit des Agilen Manifestes in digitalen Dienstleistungsunternehmen ist bisher kaum in den Fokus einer praxisorientierten Theorie genommen worden, Gleiches gilt in diesem Kontext auch für die Aktualität agiler Werte und Prinzipen. Im Rahmen meiner Forschung untersuche ich deshalb, wie digitale Dienstleistungsunternehmen das Agile Manifest der Softwareentwicklung anwenden und ob und wie sie sich auf dieser Basis agil transformieren können. Die Beantwortung meiner Forschungsfrage ist für die Praxis sehr bedeutsam. Viele Unternehmen spüren die transformatorischen Anforderungen der Digitalisierung und suchen, teilweise verzweifelt, neue Wege. Mit Blick auf die agile Welt fehlt ihnen allzu oft das Handwerkszeug, gerade wenn es darum geht, erste agile Schritte zu wagen. Eine Anleitung, wie Agilität auf Basis des Agilen Manifests der Softwareentwicklung in Unternehmen umgesetzt werden kann, könnte für viele Unternehmen eine Hilfestellung darstellen.
APA, Harvard, Vancouver, ISO, and other styles
2

Чуланова, Оксана, Oksana Chulanova, А. Меркулова, and A. Merkulova. "Methodical Instrumentation of Scrum Application as the Variety of the Methodology of Flexibility of Agile Manifesto Projects in the Management of Project Activity." Management of the Personnel and Intellectual Resources in Russia 7, no. 2 (June 13, 2018): 61–66. http://dx.doi.org/10.12737/article_5afedb6a7bdfa3.22810979.

Full text
Abstract:
Project management includes many approaches and tools. The article presents the main principles of Agile as a methodology for flexible project management Agile manifesto. The main varieties of Agile manifesto are presented and the results of the author’s assessment of the possibilities and expediency of using each of the varieties are presented. More in detail in the article is considered Scrum. This methodology is popular in the development of complex projects. The essence of Scrum is to divide the entire process of the project into a lot of sprints, which require approximately the same amount of time to complete. Each sprint must combine an established number of specific tasks. The article notes that the ideological foundations of SCRUM are more clearly reflected in the Agile manifesto. This technology allows you to get the desired effect with minimal resources. Scrum allows you to correctly form resources and maximize the potential of the team. The article explores in detail the opportunities and risks that entail the use of one of the varieties of a flexible methodology for project management — Scrum. The author’s development of the methodological toolkit for implementing Scrum in project management of the organization is presented.
APA, Harvard, Vancouver, ISO, and other styles
3

Naicker, Nalindren, and Manoj Maharaj. "Investigating Agile Requirements Engineering Practices in the South African Software Development Market." Journal of Computing and Information Technology 28, no. 1 (July 13, 2020): 33–58. http://dx.doi.org/10.20532/cit.2020.1004868.

Full text
Abstract:
The aim of this research study was to assess Agile RE practices in the South African software development industry and investigate secure Agile RE initiatives towards developing secure products. This qualitative research study was contextualized in seventeen South African software development companies. The researchers used structured interviews and document reviews as the primary data collection instruments. Qualitative data was analyzed inductively using content analysis. Emanating from the research were recommendations to guide a regular software developer on good Agile RE practices. The study concluded that although Agile Software Development is practiced in the South African software industry, there needs to be stricter adherences to the Agile Manifesto and Agile Security Manifesto in requirements engineering.
APA, Harvard, Vancouver, ISO, and other styles
4

George, Joey F., Kevin Scheibe, Anthony M. Townsend, and Brian Mennecke. "The amorphous nature of agile: no one size fits all." Journal of Systems and Information Technology 20, no. 2 (May 14, 2018): 241–60. http://dx.doi.org/10.1108/jsit-11-2017-0118.

Full text
Abstract:
Purpose This paper aims to investigate the extent to which newly agile organizations followed 2001’s Agile Manifesto, especially in terms of the 12 principles of the agile approach, as included in the Manifesto. Design/methodology/approach The authors conducted in-depth case studies of groups in three large business organizations that had recently adopted agile. Two researchers spent one day at each site, attending daily standups and conducting interviews with managers, developers and customers. Findings Across the three organizations, developers were faithful to two agile principles: the primacy of delivering valuable software continually and regular reflections on the process with an eye toward improvement. The developers were uniformly unfaithful to the principle that requires face-to-face communication. Each organization varied in their adherence to the remaining nine principles. Obstacles to faithful adoption included the experience of the organization with agile, the extent to which the industry was regulated and the extent to which developers and customers were physically dispersed. Originality/value While past research on agile development is extensive, this paper examines perspectives on the method and its adoption through the lens of the original Agile Manifesto and its 12 principles. The principles were grouped into three broader categories – software delivery, people and process – to provide additional insights and to sharpen the analysis.
APA, Harvard, Vancouver, ISO, and other styles
5

Kompalla, Andreas, and Jan Kopia. "Evaluation of the Agile Manifesto within Business Strategies." Journal of Economics and Public Finance 2, no. 2 (July 6, 2016): 227. http://dx.doi.org/10.22158/jepf.v2n2p227.

Full text
Abstract:
<p><em>Every institution, company or single person needs a guideline aligning specific actions, processes and assets to an overall target. Recent research shows that guidelines of enterprises within the manufacturing branch or more specific within the automotive industry are almost identical. But new and emerging competitors force the traditional industry to adapt its business strategy and especially to increase flexibility. The internal and external changes within the manufacturing environment support this trend. The lead times are constantly shrinking and an increasing variety in customer demands has to be handled via new platforms and models. In conclusion, enterprises within the automotive industry need to increase agility and flexibility in order to stay competitive.</em></p><p><em>Within IT-project management, agility has been a focus since the end of the 1990s. Beneath that the automotive industry has applied several principles on the core value chain, logistics and production. But on the highest strategic level of an enterprise these principles have not been analyzed yet. This research paper is evaluating case studies in order to derive core agile aspects as well as principles. Based on that business strategies within the automotive branch are broken down and compared with these principles.</em></p><p><em>The result is that most of the agile aspects are not yet considered on the highest strategic business levels although they could increase the performance of enterprises within the automotive branch. But they need to be adapted to the specific characteristics.</em></p>
APA, Harvard, Vancouver, ISO, and other styles
6

Alruwaili, Fatimah, Muna Alrajhi, and Kawther Saeedi. "How Agile Development and Its Tools Support Digital Transformation." INTERNATIONAL JOURNAL OF COMPUTERS & TECHNOLOGY 18 (February 1, 2019): 7440–50. http://dx.doi.org/10.24297/ijct.v18i0.8060.

Full text
Abstract:
Digital transformation is the enabler for new reform of businesses, socialites and governments. It is also the platform to the 2030 Vision in Saudi Arabia and in many other countries. Agile Manifesto succeeded to manage software development in a rapid and reliable fashion. Furthermore, incremental delivery of software release ensure that software audiences are engaged while delivering the product, their comments are considered in every function and any changes in requirements are based on imperial use of the software. This ensure the delivery of functionalities matching customer demands as well as reduce project failure risk. For this reason, Agility has been adopted in most software companies as a guaranteed and easy way to implement the digital solutions for their companies. This paper examines the characteristics of agile frameworks, such as Scrum and XP, and Agile tools, such as Jira, Agilo, and others, that facilitate digital transformation. Then compare productivity and efficacy of agile frameworks with traditional SDLC methods. The paper is concluded with the features of agile framework that enable digital transformation such as incremental development, flexible requirements and customer engagement.
APA, Harvard, Vancouver, ISO, and other styles
7

Jabar, Marzanah A., Norhayati Mohd Ali, Yusmadi Yah Jusoh, Salfarina Abdullah, and S. Mohanarajah. "Adaptive and Dynamic Hybrid Model for Software Project Management: A Review on its Clarity and Usage to Improve Project Success." Applied Mechanics and Materials 892 (June 2019): 38–45. http://dx.doi.org/10.4028/www.scientific.net/amm.892.38.

Full text
Abstract:
Software developers have shown a lot of interest in using agile approaches and methods to manage projects. The Agile Manifesto in 2001 provided a good basis to use this as it formulated its 4 values and 12 principles. Adaptability was a common feature in the Agile Manifesto to make agility happen and there appears a need to combine dynamism to ensure agility takes a more concrete and effective role. Whilst the term adaptability is discussed more often than dynamism by most researchers, the clarity in its meaning needs improvement as the terms are used interchangeably. This paper proposes a useful clarity on its differences and how it should be used. In addition, this approach would also facilitate the current research interest in mixing and combining software development methodologies to create hybrid versions as pure methods (traditional and agile) have not worked well in most software projects.
APA, Harvard, Vancouver, ISO, and other styles
8

Шапошнікова, О. П., and В. В. Кірвас. "Application of the Agile methodology in the practice of project-based learning in the training of IT specialists." Системи обробки інформації, no. 4(163), (October 28, 2020): 94–100. http://dx.doi.org/10.30748/soi.2020.163.10.

Full text
Abstract:
Theoretical and practical issues of the active learning methods application using the high-profile methodologies aimed at finding effective learning technologies have been considered. There have been analysed the educational methodologies based on the Agile methodology to solve educational problems, taking into account the values and principles of the Agile methodology formulated in the Agile Manifesto. The project-based learning practice introduction in the educational process with the adaptation of the Agile methodology for teaching the “Architecture and analysis of software requirements”, “Software quality and testing”, “IT projects management” disciplines has been suggested, and the results of this approach have been analyzed.
APA, Harvard, Vancouver, ISO, and other styles
9

Hassan, Ali, Soayba Younas, and Amiya Bhaumik. "Agile Methodology in an SaaS Deployment Project." International Journal of Information Technology Project Management 12, no. 2 (April 2021): 1–29. http://dx.doi.org/10.4018/ijitpm.2021040101.

Full text
Abstract:
Agile manifesto has proven its ability in managing and execution of projects in multiple industry sectors. Many researches have been conducted on the advantages and applicability of agile practices in software development and information technology industry. In this paper, empirical research has been conducted to identify the differences in agile management practices between software development and software as a service (SaaS) deployment projects. Case studies of a payment card industry (PCI) organization have been presented to identify key characteristics, tools, and methods of agile project management practices practically followed while implementing and managing of SaaS-based projects. Moreover, best suited agile management practices for pre- and post-deployment projects have also been discussed.
APA, Harvard, Vancouver, ISO, and other styles
10

KÖSE, Büşra Özdenizci. "RECENT AGILE REQUIREMENT ENGINEERING PRACTICES IN IT PROJECTS: A CASE ANALYSIS." Business & Management Studies: An International Journal 7, no. 4 (September 24, 2019): 1776–805. http://dx.doi.org/10.15295/bmij.v7i4.1214.

Full text
Abstract:
Today, the implementation of high quality and efficient Requirement Engineering (RE) practices in agile software development projects, is gaining great importance. Practitioners and researchers seeks for lighter RE practices that can handle the issues of abstract, unclear and changing requirements, and at the same time that can satisfy the Agile Manifesto philosophy. This study examines importance of RE practices in agile software development projects, and explores which aspects of the RE practices are perceived as most critical and how such aspects are adapted in practice today through two different agile software development projects of a case organization. This study aims to contribute agile RE literature by providing an interpretive analysis on perception of agile RE practices from different perspectives (agile team members, product owners, some top executives). Within this context, this study draws lessons from case studies and presents beneficial agile RE guidelines for practitioners and researchers.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "The agile manifesto"

1

Chandraseharan, Narendhira Ram. "Improving Adherence to Agile Manifesto Principles in Agile Methodology – A Case Study." The Ohio State University, 2013. http://rave.ohiolink.edu/etdc/view?acc_num=osu1366222792.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Flaten, Kayla. "The Progression of Agile Software Development." Scholarship @ Claremont, 2017. http://scholarship.claremont.edu/cmc_theses/1717.

Full text
Abstract:
This paper examines the use of Agile Software Development in the technology industry and how it came to be one of the leading models used in project management. By investigating the software development methods used in the late 1900s, it becomes clear where the system needed improvement in order to improve the efficiency in developing products. In investigating the Agile Manifesto, new and essential components are introduced that become vital in successfully producing a product. From this, it is easier to understand why Agile is so commonly used in the software development industry and how it became so effective.
APA, Harvard, Vancouver, ISO, and other styles
3

Nordin, Fredrik, and Henrik Larsson. "De agila principerna : Fortfarande aktuella och tillämpbara ett decennium senare?" Thesis, Linköpings universitet, Informatik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-110885.

Full text
Abstract:
Agila metoder och modeller ses ofta som nytänkande och används idag flitigt av företag och organisationer runt om i värden. I realiteten är grunden till det agila metoderna idag 13 år och mycket har hänt, både teknisk och kring sättet vi arbetar, sedan 2001. Den agila metodiken baseras på två dokument, det agila manifestet och de agila principerna, där principerna är till för att konkretisera manifestet. Eftersom principerna är konkreta anser vi att de har en stark koppling till hur agil utveckling de facto bedrivs. Vi har därför valt att undersöka hur principerna står sig bland utvecklarna över ett decennium efter att de skrevs samt om utvecklarna ser ett behov av revidering och vilka delar de i så fall skulle vilja förändra. För att ta reda på detta genomförde vi fyra intervjuer med utvecklare som alla hade olika erfarenhet av agilt arbete samt utgick från en tidigare kvantitativ undersökning i ämnet. Slutsatsen av undersökning är att de agila principerna fortfarande står sig bra bland utvecklarna men att det finns ett behov av revidering. Original utformningen är dock så pass väl fungerande att behovet inte är omedelbart. Det finns flera ämnen som våra respondenter tagit upp som är viktiga att ta hänsyn till där kvalitet och dokumentation är de ämnen som står ut i mängden. I mångt och mycket överensstämmer vårt resultat med den undersökning vi utgått från vilket tyder på att den bild som förmedlas av de båda undersökningarna har en god förankring hos utvecklarna, även om det finns områden där våra resultat skiljer sig från varandra.
Agile methodology and models has a wide group of supporters among organizations and companies and is often seen as innovative. The agile methods are now 13 years and a lot has happened since then, both in our ways of working and in the technology we use. The agile methodology is based on two documents, the agile manifesto and the agile principles. The principles embodies the manifesto and in our view creates a strong connection with reality and by that a strong connection with how software is developed. To find out if the principles still are viable and used among developers and if a revision of them is needed we performed a survey based on four interviews and a previously conducted quantitative study. The conclusion of this survey is that the principles are used and works well in development projects and are well thought of by the developers but there is still a need for a revision. How this revision would look and when it should be done is hard to say, the need for it aren’t urgent because of the general support of the original principles are still strong. There are a couple of different areas that our respondents point out as important where quality and documentation stands out as the most important that organizations working agile have to focus on in their daily work. Our survey and the study we used as an inspiration ends up in mostly the same conclusions with only few differences, which we see as a confirmation that our study reflects the developers’ view.
APA, Harvard, Vancouver, ISO, and other styles
4

Kessing, David, and Manuel Löwer. "Vergleich der Motivationsprofile von Scrum-Teammitgliedern mit dem Agilen Manifest zur Entwicklung von Gamification-Strategien." Thelem Universitätsverlag & Buchhandlung GmbH & Co. KG, 2021. https://tud.qucosa.de/id/qucosa%3A75929.

Full text
Abstract:
Agile Methoden sind in der industriellen Anwendung Stand der Technik, wobei Scrum das am häufigsten verwendete Prozess-Framework zur effektiven Entwicklung komplexer Produkte ist. Entworfen wurde Scrum von Ken Schwaber und Jeff Sutherland, die ebenfalls 2001 das agile Manifest mitentwickelten, welches die vier Werte und zwölf Prinzipien für die Arbeit mit agilen Methoden definiert. Scrum zeichnet sich unter anderem durch flache Hierarchien aus. Hierdurch erhalten Mitarbeitende zunehmend Verantwortung und es entsteht aufgrund der vermehrt stattfindenden Kommunikation eine erhöhte Transparenz in allen Prozessen. Diese Eigenschaften bringen viele Vorteile aber auch Herausforderungen mit sich. Einerseits kann hohe Transparenz durch Offenlegung der Arbeit zu Unsicherheit seitens der Mitarbeitenden führen, andererseits sorgt die erhöhte Verantwortung auch für einen größeren Einfluss der einzelnen Team-Mitglieder auf das Ergebnis der Arbeitsprozesse. Die Motivation und Leistungsbereitschaft der Mitarbeitenden sind demzufolge ausschlaggebend für die erfolgreiche Produktentwicklung mit Scrum. Gamification ist ein neuer, vielversprechender Ansatz zur Steigerung der Motivation und wird dabei definiert als „die Verwendung von Spiel-Designelementen in Nicht-Spielkontexten“. Die dieser Veröffentlichung zugrundeliegende Forschung bildet die Grundlage zur Entwicklung von dedizierten Gamification-Strategien mit dem Ziel der Optimierung von Motivation und folglich der Leistung der Mitarbeitenden im Scrum-Entwicklungsprozess.
APA, Harvard, Vancouver, ISO, and other styles
5

Kuziwa, Ally, and Kazibwe Flavia Ndagire. "Application of Agile Methods in Distributed Software Development." Thesis, Umeå universitet, Institutionen för informatik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-122495.

Full text
Abstract:
Agile software development methods are characterized by developer’s empowerment through self-organization, incremental requirements and constant knowledge sharing. Despite some effort to elaborate how successfully agile methods can be applied in co-located development teams, little is known on how the same is done when the development teams are distributed. Our research focus is to uncover factors that influence the successful application of agile methods in distributed development teams using a software development company as our case study. With three distributed teams applying different agile methods, we conducted focused ethnography alongside interviews to comprehend what and how various factors under distributed development teams influence successful agile methods application. It seems, all that matters is team structure, team spirit, effective communication, product requirements, and knowledge sharing. The team structure has more influence than other factors and therefore our suggestions for successful application of agile methods in distributed software development is to focus on the development team, above all factors. The analysis shows that the development methods themselves have little to do with the successful application of agile methods in distributed software development teams.
APA, Harvard, Vancouver, ISO, and other styles
6

Bazala, Jan. "Návrh generické agilní metodiky řízení projektů." Master's thesis, Vysoká škola ekonomická v Praze, 2013. http://www.nusl.cz/ntk/nusl-193860.

Full text
Abstract:
The present work is focused on project management and the relationship of this discipline to agile approaches. The aim was to design a generic agile project management methodolo-gy, which is based on Agile values and attitudes. Although the proposed methodology is mainly based on agile software development methodologies, it is also applicable to any type of project. The secondary objective was to propose possible ways of using this generic agile project management methodology in teaching 4IT414 - ICT Project Management, including the creation of documents to support this application. The work is divided into theoretical and practical. First the author defined the basic terms and knowledge of project management and subsequent-them, then also agile approaches and methodologies. In the practical part was introduced generic methodology for agile pro-ject management and proposed a possible way of involving the teaching methodology, including the design documents to serve. The objectives were met. Work can serve students agile approaches and project management, their teachers and the general public. The proposed methodology may be used for studies and real environments in various companies and institutions.
APA, Harvard, Vancouver, ISO, and other styles
7

Hollar, Ashby Brooks. "Cowboy : an agile programming methodology for a solo programmer /." VCU Scholars Compass, 2006. http://hdl.handle.net/10156/1400.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Bengtsson, Sandra, and Sara Gnospelius. "XP ett stöd eller ett hinder?" Thesis, Blekinge Tekniska Högskola, Avdelningen för för interaktion och systemdesign, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5439.

Full text
Abstract:
Detta arbete är en reflektion över ett programvaruutvecklingsprojekt, WAIS, och den arbetsmetodik som användes för detta projekt. Arbetsmetodiken för utvecklings-projektet var Extreme Programming (XP) och vi ifrågasätter om detta val var lämpligt för ett projekt som WAIS. Projektet genomfördes vid Blekinge Tekniska Högskola under våren 2004. Utvecklingsprojektet WAIS var en del av ett större projekt, AIS 42, som stöds av VINNOVA. Huvudprojektets bakgrund och syfte beskrivs för att läsaren skall förstå den roll projektet hade. Studenternas uppgift har varit att utveckla en prototyp för ett system som skall sprida information relaterad till logistik och transporter. Slutanvändarna till systemet är många och de tillhör olika organisationer som är spridda både fysiskt och verksamhetsmässigt. Arbetsmetodiken XP faller in under paraplybegreppet Agile manifesto vilkas principer beskrivs i detta arbete. Paralleller dras till arbetsprocessen och dess resultat som projektgruppen har utfört. Vi reflekterar över projektarbetet och arbetsmetodiken utifrån det perspektiv som växt fram under våra år på MDA-programmet. Synsättet bygger bland annat på particpatory design och människa-datorinteraktion där användarmedverkan har en central roll vid utvecklingsprocesser. Vår slutsats visar att utvecklingsprojektet gått miste om flera av de fördelar som arbetsmetodiken XP kan ge. De orsaker som identifierades var: tidsaspekter, tillgång till aktörer och avsaknaden av en tydlig gemensam målbild.
This thesis is a reflection over a software engineering project, WAIS, and the work methodology that has been used within the project. Extreme Programming (XP) was the work methodology used during the process of development. We question if the choice of work methodology is suitable for this kind of project. The project was running by student during spring 2004 at Blekinge Institute of technology (BTH). The project WAIS was a part of a larger project named AIS 42 that runs with funds from VINNOVA. The main projects background and purpose are described in thesis so that the reader can understand the students’ part in the projects as a whole. The students’ main task was to develop a prototype for a system that disseminates information about logistics and transports. The system has many different end users and they come from various organizations that are spread out both physical and organizational. XP is treated as a methodology with in Agile manifesto, which principles are being explained in the thesis. Parallels are being drawn between the work process and the result from the work done. We reflect over the process and the work methodology from a perspective that has been brought forth from our years of education at BTH. The approach is built up upon theories from participatory design and human computer interaction where the user has an essential part of the process of development. The conclusion shows that the project has missed some of the advantages that XP brings. The reasons that we identified were; timeaspects, access to users and the lack of a joint objectiv.
APA, Harvard, Vancouver, ISO, and other styles
9

Bagane, Houda. "Analyse des principes du génie logiciel au niveau du développement agile." Mémoire, 2011. http://www.archipel.uqam.ca/4010/1/M12003.pdf.

Full text
Abstract:
Dans le cadre du développement de logiciel, deux courants de pensée se font concurrence depuis quelques années : le développement de logiciels s'appuyant sur une modélisation plus détaillée et le développement de logiciels basé sur des méthodes agiles qui mettent l'accent sur la production de code opérationnel plutôt que sur la documentation. Chaque courant s'appuie sur ses propres principes. Diverses recherches ont été menées sur les fondements du génie logiciel plus « classique », de façon à en définir les principes. Parmi ces travaux figure la thèse de Normand Séguin, notre codirecteur. En revanche, aucune recherche n'a tenté d'étudier les fondements du développement agile de logiciel. Au début des années 2000, plusieurs grands noms du développement logiciel se sont réunis, parmi eux Cunningham, Beek, Schwaber, Sutherland et Fowler. Ces derniers ont tenté d'extraire, de leurs approches respectives, quatre valeurs et douze principes communs à tous dans le but de produire un « Manifeste agile ». Le développement agile de logiciel peut se faire à l'aide d'un ensemble de méthodes agiles. Bien que chaque méthode adhère aux valeurs et principes du manifeste, chacune met de l'avant des valeurs, des principes et des pratiques complémentaires. Ce mémoire présente les résultats d'une étude de 32 énoncés présentés comme étant des « principes agiles » répertoriés dans la littérature. La liste des principes étudiés est formée à partir des douze principes du manifeste agile, cinq principes de l'eXtreme programming (XP), six de Scrum et neuf de Dynamic System Development Method (DSDM). Notre étude est fondée sur une méthodologie analytique reposant sur une liste de critères pour vérifier si un « principe agile » correspond bien à un principe de génie logiciel. Notre analyse a permis d'identifier 19 principes qui répondent aux critères. Tous les principes retenus sont des propositions prescriptives guidant l'action dans le processus de développement de logiciel. ______________________________________________________________________________ MOTS-CLÉS DE L’AUTEUR : génie logiciel, développement agile, manifeste agile, méthodes agiles, principe, SWEBOK, eXtreme Programming, Scrum, DSDM.
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "The agile manifesto"

1

Carter, Eric, and Matthew Hurst. Agile Machine Learning: Effective Machine Learning Inspired by the Agile Manifesto. Apress, 2019.

Find full text
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "The agile manifesto"

1

Hazzan, Orit, and Yael Dubinsky. "The Agile Manifesto." In Agile Anywhere, 9–14. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-10157-6_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Meszaros, Gerard, Shaun M. Smith, and Jennitta Andrea. "The Test Automation Manifesto." In Extreme Programming and Agile Methods - XP/Agile Universe 2003, 73–81. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-45122-8_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Dueck, Gunter. "Agile Erziehung oder The Agile Education Manifesto (Daily Dueck 256, Januar 2016)." In Disruptive Zeiten, 137–38. Berlin, Heidelberg: Springer Berlin Heidelberg, 2017. http://dx.doi.org/10.1007/978-3-662-54881-3_56.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Mancl, Dennis, and Steven D. Fraser. "XP 2019 Panel: Agile Manifesto – Impacts on Culture, Education, and Software Practices." In Agile Processes in Software Engineering and Extreme Programming – Workshops, 143–48. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-30126-2_17.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Kiv, Soreangsey, Samedi Heng, Manuel Kolp, and Yves Wautelet. "Agile Manifesto and Practices Selection for Tailoring Software Development: A Systematic Literature Review." In Product-Focused Software Process Improvement, 12–30. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-030-03673-7_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Looks, Hanna, Jannik Fangmann, Jörg Thomaschewski, María-José Escalona, and Eva-Maria Schön. "Towards a Standardized Questionnaire for Measuring Agility at Team Level." In Lecture Notes in Business Information Processing, 71–85. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-78098-2_5.

Full text
Abstract:
AbstractContext: Twenty years after the publication of the agile manifesto, agility is becoming more and more popular in different contexts. Agile values are changing the way people work together and influence people’s mindset as well as the culture of organizations. Many organizations have understood that continuous improvement is based on measurement.Objective: The objective of this paper is to present how agility can be measured at the team level. For this reason, we will introduce our questionnaire for measuring agility, which is based on the agile values of the manifesto.Method: We developed a questionnaire comprising 36 items that measure the current state of a team’s agility in six dimensions (communicative, change-affine, iterative, self-organized, product-driven and improvement-oriented). This questionnaire has been evaluated with respect to several expert reviews and in a case study.Results: The questionnaire provides a method for measuring the current state of agility, which takes the individual context of the team into account. Furthermore, our research shows, that this technique enables the user to uncover dysfunctionalities in a team.Conclusion: Practitioners and organizations can use our questionnaire to optimize collaboration within their teams in terms of agility. In particular, the value delivery of an organization can be increased by optimizing collaboration at the team level. The development of this questionnaire is a continuous learning process with the aim to develop a standardized questionnaire for measuring agility.
APA, Harvard, Vancouver, ISO, and other styles
7

Hanser, Eckhart. "Das Agile Manifest." In Agile Prozesse: Von XP über Scrum bis MAP, 9–11. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12313-9_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Michl, Thomas. "Das agile Manifest – eine Einführung." In Agile Verwaltung, 3–13. Berlin, Heidelberg: Springer Berlin Heidelberg, 2018. http://dx.doi.org/10.1007/978-3-662-57699-1_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Andresen, Judith. "Agiles Manifest einlösen." In Agiles Coaching, 101–60. München: Carl Hanser Verlag GmbH & Co. KG, 2019. http://dx.doi.org/10.3139/9783446462755.006.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Sommerhoff, Benedikt, and Olaf Wolter. "Anhang: Manifest für Agiles Qualitätsmanagement." In Agiles Qualitätsmanagement, 115–23. München: Carl Hanser Verlag GmbH & Co. KG, 2019. http://dx.doi.org/10.3139/9783446457607.006.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "The agile manifesto"

1

Kamat, Venkatesh. "Agile Manifesto in Higher Education." In 2012 IEEE Fourth International Conference on Technology for Education (T4E). IEEE, 2012. http://dx.doi.org/10.1109/t4e.2012.49.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Darrin, M. Ann Garrison, and William S. Devereux. "The Agile Manifesto, design thinking and systems engineering." In 2017 Annual IEEE International Systems Conference (SysCon). IEEE, 2017. http://dx.doi.org/10.1109/syscon.2017.7934765.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Ozkan, Necmettin. "Imperfections Underlying the Manifesto for Agile Software Development." In 2019 1st International Informatics and Software Engineering Conference (UBMYK). IEEE, 2019. http://dx.doi.org/10.1109/ubmyk48245.2019.8965504.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Manamendra, M. A. S. C., K. N. Manathunga, K. H. D. Perera, and N. Kodagoda. "Improvements for agile manifesto and make agile applicable for undergraduate research projects." In 2013 8th International Conference on Computer Science & Education (ICCSE). IEEE, 2013. http://dx.doi.org/10.1109/iccse.2013.6553969.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Luna, Alexandre J. H. de O., Philippe Kruchten, Edson Luiz Riccio, and Hermano P. de Moura. "Foundations for an Agile Governance Manifesto: a bridge for business agility." In 13th CONTECSI International Conference on Information Systems and Technology Management. TECSI, 2016. http://dx.doi.org/10.5748/9788599693124-13contecsi/ps-4228.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Lindberg, Steven, and Matthew I. Campbell. "How the Design of a 3D Printer Bridged Engineering Design Processes and the Agile Software Manifesto." In ASME 2019 International Design Engineering Technical Conferences and Computers and Information in Engineering Conference. American Society of Mechanical Engineers, 2019. http://dx.doi.org/10.1115/detc2019-97261.

Full text
Abstract:
Abstract Individual engineering design projects face different challenges depending on their scale. Instead of dealing with problems of complex multidisciplinary systems, small scale design must overcome issues of limited resources. The philosophy of agile software development has been highly successful in addressing similar issues in the software engineering realm over the past two decades. Through the design and prototyping of a low-budget desktop stereolithography printer, the application of agile principles to engineering design process is explored. The printer’s design is discussed in detail to provide examples of successes and failures when these agile principles are put into practice. The paper concludes with a discussion of how agile principles could be leveraged in engineering design. The approach taken in this paper is more of a longitudinal study of a single design process over a twelve-month period as opposed to rigorous experiments that engage multiple users in short design scenarios. Nonetheless, this case study demonstrates how the application of agile principles can inform, improve, and complement traditional engineering design processes.
APA, Harvard, Vancouver, ISO, and other styles
7

Henriques, Vaughan, and Maureen Tanner. "Assessing the Association between Agile Maturity Model Levels and Perceived Project Success." In InSITE 2020: Informing Science + IT Education Conferences: Online. Informing Science Institute, 2020. http://dx.doi.org/10.28945/4519.

Full text
Abstract:
Aim/Purpose: Given the underlying philosophy of the agile manifesto, this study investigates whether an increase in agile maturity is associated with improved perceived project success. Background: The underlying philosophy of the agile manifesto is embodied in principle one which promotes the continuous delivery of software that is deemed valuable by the customer, while principle twelve encourages continual improvement of the delivery process. This constant improvement, or maturity, is not a concept unique to agile methods and is commonly referred to as a maturity model. The most common of maturity model is the Capability Maturity Model Integrated (CMMI). However, research consensus indicates CMMI might not fully be compatible with agile implementation, specifically at higher levels of maturity without sacrificing agility. Agile maturity models (AMM), which are aligned to agile principles encourage continuous improvement while maintaining agility. Methodology: The study employs a conceptual model based on an existing agile maturity model that is related to perceived project success. Using an objectivist perspective, a quantitative method was employed to analyze the results of an online survey of agile practitioners. Contribution: The significant contribution from this research is the validation of the conceptual model relating the activities and maturity levels of the AMM as the independent variables to the dependent variable of perceived project success. Findings: The data analysis found that a significant positive correlation exists between maturity levels and perceived project success. The strongest correlation was found at the highest maturity level, with relatively weaker correlation at the lower levels of maturity. It can thus be concluded that a higher level of maturity in the AMM is positively associated with perceived project success. Recommendations for Practitioners: The study has practical implications in highlighting that performance management, requirements management, regular delivery and customer availability are key areas to focus on to establish and continually improve the success of agile implementations. This study further assists practitioners in systematically identifying the critical agile activities, such as the use of story cards, continuous delivery and the presence of a knowledgeable customer. Recommendation for Researchers: The contributions of this study for academics is the confirmation of the maturity model developed by Patel and Ramachandran (2009a). This study also shows the association between the individual activities within the maturity levels as well as the maturity levels and the perceived project success, addressing a gap in literature relating these concepts. Future Research: It would be useful to replicate this study whilst following a qualitative approach. The study could also be replicated with a sample consisting of agile project customers.
APA, Harvard, Vancouver, ISO, and other styles
8

Kessing, David, and Manuel Löwer. "Vergleich der Motivationsprofile von Scrum-Teammitgliedern mit dem Agilen Manifest zur Entwicklung von Gamification-Strategien." In Entwerfen Entwickeln Erleben - EEE2021. Prof. Dr.-Ing. habil Ralph H. Stelzer, Prof. Dr.-Ing. Jens Krzywinski, 2021. http://dx.doi.org/10.25368/2021.57.

Full text
Abstract:
Agile Methoden sind in der industriellen Anwendung Stand der Technik, wobei Scrum das am häufigsten verwendete Prozess-Framework zur effektiven Entwicklung komplexer Produkte ist. Entworfen wurde Scrum von Ken Schwaber und Jeff Sutherland, die ebenfalls 2001 das agile Manifest mitentwickelten, welches die vier Werte und zwölf Prinzipien für die Arbeit mit agilen Methoden definiert. Scrum zeichnet sich unter anderem durch flache Hierarchien aus. Hierdurch erhalten Mitarbeitende zunehmend Verantwortung und es entsteht aufgrund der vermehrt stattfindenden Kommunikation eine erhöhte Transparenz in allen Prozessen. Diese Eigenschaften bringen viele Vorteile aber auch Herausforderungen mit sich. Einerseits kann hohe Transparenz durch Offenlegung der Arbeit zu Unsicherheit seitens der Mitarbeitenden führen, andererseits sorgt die erhöhte Verantwortung auch für einen größeren Einfluss der einzelnen Team-Mitglieder auf das Ergebnis der Arbeitsprozesse. Die Motivation und Leistungsbereitschaft der Mitarbeitenden sind demzufolge ausschlaggebend für die erfolgreiche Produktentwicklung mit Scrum. Gamification ist ein neuer, vielversprechender Ansatz zur Steigerung der Motivation und wird dabei definiert als „die Verwendung von Spiel-Designelementen in Nicht-Spielkontexten“. Die dieser Veröffentlichung zugrundeliegende Forschung bildet die Grundlage zur Entwicklung von dedizierten Gamification-Strategien mit dem Ziel der Optimierung von Motivation und folglich der Leistung der Mitarbeitenden im Scrum-Entwicklungsprozess.
APA, Harvard, Vancouver, ISO, and other styles
9

Choma Neto, João, Luiz Henrique Ten Caten Bento, Edson OliveiraJr, and Simone Do Rocio Senger Souza. "Are we teaching UML according to what IT companies need? A survey on the São Carlos-SP region." In Simpósio Brasileiro de Educação em Computação. Sociedade Brasileira de Computação, 2021. http://dx.doi.org/10.5753/educomp.2021.14469.

Full text
Abstract:
The Unified Modeling Language (UML) arisen intending to unify the many modeling languages and become the universal language for software modeling. Since its creation, more than 25 years have passed. With the growing success of agile methodologies for software development, supported by less modeling and documentation manifest, the use of UML-driven software processes has decreased, thus a specific subset of diagrams has been adopted, such as use case, class, and sequence. On the other hand, in academia, UML is still being taught in Computing courses, most of the time without knowing whether what is taught is what the industry needs for practical use. This paper presents an overview of the UML adoption in IT companies of the region. We analyzed quantitative and qualitative data to support academia at focusing on the most used UML diagrams by practitioners. We constructed a survey composed of 21 questions, distributed to 10 region companies, and we received 24 answers. The results of our study show high usage of UML, including companies adopting agile methods. Certain diagrams are more intensively used, for instance, use case diagrams. The results provide directions to improve UML teaching, focusing on diagrams that best adhere to the development processes employed, in particular, agile processes.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'The agile manifesto' for particular source types:
Journal articles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography