Relevant bibliographies by topics / Agility in Software Development

Contents

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

Academic literature on the topic 'Agility in Software Development'

Author: Grafiati
Published: 4 June 2021
Last updated: 17 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 'Agility in Software Development.'

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 "Agility in Software Development"

1

Batra, Dinesh, Weidong Xia, and Shekhar Rathor. "Agility Facilitators for Contemporary Software Development." Journal of Database Management 27, no. 1 (January 2016): 1–28. http://dx.doi.org/10.4018/jdm.2016010101.

Full text
Abstract:
Agile software development generally refers to popular practices that are supposed to adhere to the Agile Manifesto with its values and principles. Empirical studies on agile software development have mainly focused on organizational adoption and impacts of agile practices. Furthermore, the literature on agile software development has mostly centered on small, co-located projects. However, agility is needed for software development projects of varied sizes in different organizations across industries. The general nature of agile values and principles and the procedure-driven nature of specific agile methods make it difficult for organizations to determine what they can do to effectively facilitate agility in their software development process. To bridge that literature gap and based on an evolved grounded-theory approach, this study identifies nine agility facilitators and their corresponding dimensions that extend beyond small, co-located projects to software projects of any size and distribution. These agility facilitators are further grouped into two categories: organizational foundation and project processes. In addition, the authors identify four dimensions of agility. The authors propose a framework that describes the organizational mechanisms through which the nine categories of facilitators lead to software development agility.
APA, Harvard, Vancouver, ISO, and other styles
2

Kettunen, Petri. "Extending Software Project Agility with New Product Development Enterprise Agility." Software Process: Improvement and Practice 12, no. 6 (2007): 541–48. http://dx.doi.org/10.1002/spip.342.

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

Forti, Tiago L. D., Gustavo C. Longhin, Nadia Cazarim da Silva Forti, and João Alberto V. Requena. "Agility based software development for truss design." Rem: Revista Escola de Minas 67, no. 3 (September 2014): 259–64. http://dx.doi.org/10.1590/s0370-44672014000300003.

Full text
Abstract:
This article describes the development of an application for structural analysis of tubular trussed girders. Such structural components are widely used on roofs for which long span components are a necessity, e. g., supermarkets, distribution centers, etc. The application supplies hints to the project engineers as to the most economic solutions for a combination of span, loads, and other characteristics. Software development techniques are also explored. Such techniques can be divided into two large groups. In the first one, which is most widely known and used, software development complies with very rigid planning, where processes are more important than skills. This methodology is known as the Rigorous Development System (RDS). The second group, called Agile Development System (ADS), is conceived as an option for those not aligned with the RDS rules. This text describes the experience of an ADS based software development for truss design. In Section 2, the basis of ADS is presented. Section 3 describes the truss design application and civil engineering related concepts. Section 4 brings an example illustrating the application. Conclusions are in Section 5.
APA, Harvard, Vancouver, ISO, and other styles
4

Balijepally, VenuGopal, Gerald DeHondt, Vijayan Sugumaran, and Sridhar Nerur. "Agility in Software Development and Project Value." Journal of Database Management 28, no. 4 (October 2017): 40–59. http://dx.doi.org/10.4018/jdm.2017100103.

Full text
Abstract:
Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.
APA, Harvard, Vancouver, ISO, and other styles
5

Bowen, Jonathan P., Mike Hinchey, Helge Janicke, Martin Ward, and Hussein Zedan. "Formality, Agility, Security, and Evolution in Software Development." Computer 47, no. 10 (October 2014): 86–89. http://dx.doi.org/10.1109/mc.2014.284.

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

de Cesare, Sergio, Mark Lycett, Robert D. Macredie, Chaitali Patel, and Ray Paul. "Examining perceptions of agility in software development practice." Communications of the ACM 53, no. 6 (June 2010): 126–30. http://dx.doi.org/10.1145/1743546.1743580.

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

Varajão, João. "Software Development in Disruptive Times." Queue 19, no. 1 (February 28, 2021): 94–103. http://dx.doi.org/10.1145/3454122.3458743.

Full text
Abstract:
In this project, the challenge was to "deploy software faster than the coronavirus spread." In a project with such peculiar characteristics, several factors can influence success, but some clearly stand out: top management support, agility, understanding and commitment of the project team, and the technology used. Conventional development approaches and technologies would simply not be able to meet the requirements promptly.
APA, Harvard, Vancouver, ISO, and other styles
8

Ortega-Ordóñez, Wilson Alfredo, César Jesús Pardo-Calvache, and Francisco José Pino-Correa. "Systematic mapping on the agility evaluation in software development organizations." ITECKNE 16, no. 1 (June 19, 2019): 64–76. http://dx.doi.org/10.15332/iteckne.v16i1.2162.

Full text
Abstract:
Agile software development approaches provide great benefits for organizations; however, their implementation is subject to many challenges. For organizations is important to know the level of agility achieved and the gaps in their transformation process in order to implement improvements in their processes and take advantage of the agile approaches. Keeping this in mind, this article presents a systematic mapping of the literature about the evaluation of agility in software development organizations. As a result, 18 studies were found, which were analyzed and compared taking into account the type of study, the relationship of the evaluation with the principles and agile values, the defined evaluation criteria, the validation methods used, and the proposed tools. In addition, the factors that influence the assessment of agility and the aspects that motivate the interest in this research stream are exposed.
APA, Harvard, Vancouver, ISO, and other styles
9

Singh, Sukhpal, and Inderveer Chana. "Introducing Agility in Cloud Based Software Development through ASD." International Journal of u- and e- Service, Science and Technology 6, no. 5 (October 31, 2013): 191–202. http://dx.doi.org/10.14257/ijunesst.2013.6.5.17.

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

Tian, Kun. "Adding More Agility to Software Product Line Methods." International Journal of Knowledge and Systems Science 5, no. 4 (October 2014): 17–34. http://dx.doi.org/10.4018/ijkss.2014100102.

Full text
Abstract:
Software Product Line Methods (SPLMs) have been continuously gaining attention, especially in practice, for on one hand, they address diverse market needs while controlling costs by planned systematic reuse in core assets development (domain engineering), and on another hand, they reduce products' time-to-market, achieving a certain level of agility in product development (application engineering). More cost-effective and agile as they are than traditional development methods for producing families of similar products, SPLMs still seem to be heavy weight in nature. In SPLMs, significant up-front commitments are involved in development of a flexible product platform, which will be modified into a range of products sharing common features. Agile Methods (AMs) share similar goals with SPLMs, e.g., on rapidly delivering high quality software that meets the changing needs of stakeholders. However, they appear to differ significantly practices. The purpose of this work is to compare Agile and Software Product line approaches from fundamental goals/principles, engineering, software quality assurance, sand project management perspectives, etc. The results of the study can be used to determine the feasibility of tailoring a software product line approach with Agile practices, resulting in a lighter-weight approach that provides mass customization, reduced time-to-market, and improved customer satisfaction.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Agility in Software Development"

1

Rathor, Shekhar. "Facilitators for Software Development Agility." FIU Digital Commons, 2016. http://digitalcommons.fiu.edu/etd/3059.

Full text
Abstract:
Software development methodologies provide guidelines and practices for developing information systems. They have evolved over time from traditional plan-driven methodologies to incremental and iterative software development methodologies. The Agile Manifesto was released in 2001, which provides values and principles for agile software development. Over the last few years, agile software development has become popular because its values and principles focus on addressing the needs of contemporary software development. IT and Business teams need agility to deal with changes that can emerge during software development due to changing business needs. Agile software development practices claim to provide the ability to deal with such changes. Various research studies have identified many factors/variables that are important for agile software development such as team autonomy, communication, and organizational culture. Most of these empirical studies on agile software development focus on just a few variables. The relationships among the variables is still not understood. The dimensions of agility and the relationship between agility and other variables have not been studied quantitatively in the literature. Also, there is no comprehensive framework to explain agile software development. This research study addresses these research gaps. This study analyzed a comprehensive research model that included antecedent variables (team autonomy, team competence), process variables (collaborative decision making, iterative development, communication), delivery capability, agility, and project outcomes (change satisfaction, customer satisfaction). It presents key dimensions of agility and quantitatively analyzes the relationship between agility and other variables. The PLS analysis of one hundred and sixty survey responses show that process variables mediate the relationship between antecedent variables and delivery capability and agility. The findings show that the delivery capability of the teams contributes to agility, antecedents and process variables contribute to agility, and delivery capability for better customer satisfaction. These results will help IS practitioners to understand the variables that are necessary to achieve agility for better project outcomes. Also, these quantitative findings provide better conceptual clarity about the relationship between various key variables related to agile software development.
APA, Harvard, Vancouver, ISO, and other styles
2

Maruping, Likoebe Mohau. "Essays on agility in software development teams process and governance perspectives /." College Park, Md. : University of Maryland, 2006. http://hdl.handle.net/1903/3415.

Full text
Abstract:
Thesis (Ph. D.) -- University of Maryland, College Park, 2006.
Thesis research directed by: Business and Management. Title from t.p. of PDF. Includes bibliographical references. Published by UMI Dissertation Services, Ann Arbor, Mich. Also available in paper.
APA, Harvard, Vancouver, ISO, and other styles
3

Roman, Greice de Carli. "Characterizing the presence of agility in large-scale agile software development." Pontif?cia Universidade Cat?lica do Rio Grande do Sul, 2016. http://tede2.pucrs.br/tede2/handle/tede/7518.

Full text
Abstract:
Submitted by Caroline Xavier (caroline.xavier@pucrs.br) on 2017-06-30T18:19:05Z No. of bitstreams: 1 DIS_GREICE_DE_CARLI_ROMAN_COMPLETO.pdf: 9835425 bytes, checksum: aa605361de91b916006af4710a54365b (MD5)
Made available in DSpace on 2017-06-30T18:19:05Z (GMT). No. of bitstreams: 1 DIS_GREICE_DE_CARLI_ROMAN_COMPLETO.pdf: 9835425 bytes, checksum: aa605361de91b916006af4710a54365b (MD5) Previous issue date: 2016-12-15
Em fevereiro de 2001, o Manifesto ?gil foi proposto tendo como princ?pio equipes pequenas e co-localizadas. No entanto, ao longo destes 16 anos, a agilidade tamb?m foi posta em pr?tica em outros contextos, como por exemplo: equipes distribu?das e sistemas complexos, utilizando-se o termo "Desenvolvimento ?gil em Larga Escala". N?o h? uma defini??o clara e compreensiva de como a agilidade est? presente neste contexto. Assim, nosso trabalho preenche essa lacuna com o objetivo de caracterizar a agilidade no Desenvolvimento ?gil em Larga Escala. Neste trabalho, realizou-se um estudo organizado em duas fases. Na Fase 1, denominada Base Te?rica, realizamos um estudo do estado-da-arte da ?rea. Na Fase 2, denominado Estudo Emp?rico, n?s realizamos duas investiga??es: um estudo de campo em uma empresa ?gil em larga escala, para identificar o desenvolvimento durante o processo de transforma??o da empresa para esta nova abordagem e, um grupo focal, para identificar como as equipes ?geis em larga escala que v?m utilizando os m?todos ?geis o quanto se percebem em termos de aspectos de maturidade ?gil. Estes resultados contribuem para os pesquisadores e profissionais entenderem melhor como a agilidade e definida e percebida nestes grandes ambientes. O conhecimento e ?til para aqueles que querem entender como o desenvolvimento ?gil se adapta a tais ambientes e para pesquisadores com o objetivo de se aprofundar sobre o tema.
The Agile Manifesto was proposed in February 2001 having in mind small and collocated teams. However, agile has also been put in practice in other settings (e.g. large teams, distributed teams, complex systems) under the term ?Large-Scale Agile Development' (LSAD). There is no clear definition for and understanding of how agility is present in this setting. Thus, our work fills in this gap aiming to characterize agility in LSAD. We conducted a study organized in two phases. In Phase 1, named Theoretical Base, we conducted the state-of-the-art of the area. In Phase 2, named Empirical Study, we conducted two investigations: a field study in a large-scale agile company to identify how agility was developed during the transformation process of the company to this new approach, and a focus group to identify how large-scale agile teams that have been using agile for a certain while perceive themselves in terms of maturity in agile aspects. Findings contribute to researchers and professionals better understand how agility is defined and perceived in large settings. This knowledge is useful for those who want to enter the agile journey in such similar environments and for researchers aiming to further explore the topic.
APA, Harvard, Vancouver, ISO, and other styles
4

Salvador, David Musat. "Hindrances for Agility : Detection and Recommendations." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3202.

Full text
Abstract:
Context. Global Software Development is software work undertaken at geographically separated locations across national boundaries in a coordinated fashion involving real time or asynchronous interaction. Distributed Agile Development aims at the benefits of both Agile Software Development and Global Software Development aiding the distributed teams to overcome the challenges brought by the distribution. Objectives. In this study the author investigates whether a globally distributed company is prepared to be agile, determining hindrances for agile and providing recommendations to mitigate or overcome the detected hindrances. Methods. In this case study, surveys and interviews were used to study the hindrances for agile and literature was used to provide the recommendations towards the detected hindrances. Results. 4 hindrances were detected. Only 1 was justified as necessary for the good performance of the distributed company. Several recommendations to overcome the hindrances were proposed. Both hindrances and proposed solutions were validated by the company representative. Conclusions. We conclude that the studied individuals are willing to be agile. As agile is built bottom-up, the company is prepared to be agile. However, they will not be able to be agile until they overcome or mitigate the detected challenges. In the study, several solutions for it are proposed.
APA, Harvard, Vancouver, ISO, and other styles
5

Srinivasan, Jayakanth. "Exploring the Sources of Enterprise Agility in Software Organizations." Doctoral thesis, Västerås : Akademin för innovation, design och teknik, Mälardalens högskola [School of Innovation, Design and Engineering], Mälardalen University, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-6853.

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

Winter, Jeff. "Measuring usability - balancing agility and formality : for stakeholders' needs in software development /." Licentiate thesis, Karlskrona : Department of Interaction and System Design, School of Engineering, Blekinge Institute of Technology, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00438.

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

Lee, Harris IV Edward. "Assessing and Improving "Agile Performance" : Using Comparative Agility to Improve Software Development Management." Thesis, KTH, Tillämpad maskinteknik (KTH Södertälje), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-148413.

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

Buslovic, Maksim, and Samson Deribe. "A Multiple Case Study on Contradictions and Pre-conditions for Outsourcing Agile Software Development Projects." Thesis, Linköpings universitet, Företagsekonomi, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-81884.

Full text
Abstract:
Title: A Multiple Case Study on Contradictions and Pre-conditions for Outsourcing Agile Software Development ProjectsAuthor: Maksim Buslovič & Samson DeribeSupervisor: Jonas SöderlundDate: May 30th, 2012Background: In today’s turbulent business environment organizational success depends on its ability to embrace change and adapt quickly. The ability to satisfy customer is core to profitability; thus being agile is a prominent factor, because customer expectations are never static. One of the project management methods which is quite popular in the software development are is Agile Method. Agile methods depart from the classical project approach as it emphasizes more on interaction among participant, short iteration and continuous feedback to embrace the continuously evolving customer requirements. However, implementing Agile methods in a distributed project work seems to be challenging, thus limiting projects to optimize form their distributed resource as well as external parties.Aim: The purpose of this thesis is to understand how Agile methods contradict with the Outsourcing practice, which ultimately lead to identifying the possibilities to successfully outsource project work based on Agile methods. In addition, the study aims in providing a good ground for future study in ‘Outsourcing within Agile Methods’ to fill the big theoretical gap identified in the area.Methodology: The thesis used a qualitative approach that intends to build theory through iteration by waving back and forth between data and literatures in an inductive manner. The research design was based on multiple case study that used five interviews and one direct observation as an instrument to collect primary data along with secondary data; all three together ensure proper triangulation resulting in higher research validity. Open coding system was used to analyze data; and findings were presented by tables, figures, models and direct quotations.Results: The study shows that values and principles of agile software development which gives much emphasis on proximity in order to have a daily stand-up meetings, visualizations, constant contact with customers and other team members, knowledge sharing and fun disappear when the project is involved in outsourcing partly the development process; because the need use more plans & documentation, clear contracts and less interaction implying a contradiction in both ‘Agile methods’ and ‘Outsourcing’ practices. However, the study identified preconditions that must be considered while involving in outsourcing part of Agile software development: Outsource only if the part to be outsourced is not related to core product; Put a complete team in a co-located manner; Minimize interdependence among distributed teams; and there should be enough time before delivering product to customers.
APA, Harvard, Vancouver, ISO, and other styles
9

Mulder, Susan. "An action research study on the use of Scrum to provide agility in data warehouse development." Diss., University of Pretoria, 2010. http://hdl.handle.net/2263/24561.

Full text
Abstract:
Data warehousing is a new and emerging field. Projects tend to be complex and time consuming. Because of this complexity, teams tend to commit to more than they can deliver. This causes delayed delivery. Applying Agile development styles to data warehousing is one of the alternative methodologies that are being investigated to help teams to accelerate the delivery of business value. Scrum is one of the frameworks that falls within the Agile stream. Scrum focuses on project management and makes use of iterative and incremental development. It tries to deliver the smallest piece of business value the fastest. The paper evaluates the implementation of Scrum in a data warehouse team of a financial investment company. The researcher did an action research study on the team to see if Scrum can be used as a viable alternative framework to bring agility to Data Warehouse development. She examined the changes that the team experienced during and after the implementation of Scrum, focusing on team structure and roles within the teams. The researcher defined a framework to evaluate how well the team implemented Scrum. The researcher also evaluated the quality of work delivered, and the predictability and productivity of the team as metrics to see if Scrum made a difference within the team. The research paper examined why the implementation failed and what issues Scrum highlighted within the team as well as within the way that the company implemented it.
Dissertation (MCom)--University of Pretoria, 2010.
Informatics
unrestricted
APA, Harvard, Vancouver, ISO, and other styles
10

Chidyiwa, Octavia. "An investigation of the best-practices for implementing an Ecommerce software engineering project comparing two common methodologies, viz. Agile and Traditional." University of the Western Cape, 2020. http://hdl.handle.net/11394/7925.

Full text
Abstract:
Masters of Science
In a world where technology is advancing at a very rapid pace, global competition has significantly increased, and this is putting pressure on software companies to produce quality software. It has therefore become critically important to manage well the implementation of software engineering projects by employing effective methods that ensure the best product is produced. The most popular software project implementation methodologies are the Traditional methods and Agile methods. This research explored these two methodologies by comparing the strength and weakness of both approaches. The research was conducted using a constructionist epistemology with a critical inquiry using the grounded theory methodology, applying both quantitative and qualitative methods to the case studies. Findings were collected through participant observation using a designed questionnaire targeting a selected sample of the study population. This sample of the population consisted of Ecommerce organizations in the Western Cape province of South Africa to establish which of the Traditional or Agile methods would best lead to the successful implementation of Ecommerce software engineering projects. The research results showed that the Agile methodology was the preferred and recommended approach. Very few participants of the research supported the Traditional approach to still be considered and used for projects with well-known end goals. An Ecommerce website prototype for a local Cape Town business was constructed as following the Agile approach to measure and validate the findings of the research. The prototype was built successfully from conception to the final delivery product and on time confirming the Agile approach as best for Ecommerce software development. In conclusion, the Agile methodology is the choice approach based on reviewed literature, the research results, and the prototype construction. These results will help in critical decision making regarding an appropriate development methodology to follow for the Ecommerce industry in the Western Cape.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Agility in Software Development"

1

Refactoring to agility. [Upper Saddle River, N.J: Addison Wesley Professional, 2006.

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

Shalloway, Alan. Lean-agile software development: Achieving enterprise agility. Upper Saddle River, NJ: Addison-Wesley, 2010.

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

Guy, Beaver, and Trott James, eds. Lean-agile software development: Achieving enterprise agility. Upper Saddle River, NJ: Addison-Wesley, 2010.

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

Shalloway, Alan. Lean-agile software development: Achieving enterprise agility. Upper Saddle River, NJ: Addison-Wesley, 2010.

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

Shalloway, Alan. Lean-agile software development: Achieving enterprise agility. Upper Saddle River, NJ: Addison-Wesley, 2009.

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

Shalloway, Alan. Lean-agile software development: Achieving enterprise agility. Upper Saddle River, NJ: Addison-Wesley, 2010.

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

1974-, Broderick Stacia, ed. The software project manager's bridge to agility. Upper Saddle River, NJ: Addison-Wesley, 2008.

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

Boehm, Barry W. Balancing agility and discipline: A guide for the perplexed. Boston: Addison-Wesley, 2003.

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

Making sense of agile project management: Balancing control and agility. Hoboken, NJ: Wiley, 2011.

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

Enterprise software delivery: Bringing agility and efficiency to the global software supply chain. Upper Saddle River, NJ: Addison-Wesley, 2013.

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

Book chapters on the topic "Agility in Software Development"

1

Houston, Daniel X., and Stephen W. Rosemergy. "Assessing Product Development Agility." In Managing Software Process Evolution, 39–60. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-31545-4_3.

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

Šmite, Darja, Nils Brede Moe, and Pär J. Ågerfalk. "Fundamentals of Agile Distributed Software Development." In Agility Across Time and Space, 3–7. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12442-6_1.

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

Ambler, Scott W. "Agile Software Development at Scale." In Balancing Agility and Formalism in Software Engineering, 1–12. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-85279-7_1.

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

Sarker, Saonee, Charles L. Munson, Suprateek Sarker, and Suranjan Chakraborty. "Contribution of Agility to Successful Distributed Software Development." In Agility Across Time and Space, 107–16. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12442-6_7.

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

Kulak, Daryl, and Hong Li. "Seven Principles of Systems Thinking for Software Development." In The Journey to Enterprise Agility, 35–45. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-54087-0_4.

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

Laanti, Maarit, Jouni Similä, and Pekka Abrahamsson. "Definitions of Agile Software Development and Agility." In Communications in Computer and Information Science, 247–58. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39179-8_22.

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

Ressin, Malte, José Abdelnour-Nocera, and Andy Smith. "Lost in Agility? Approaching Software Localization in Agile Software Development." In Lecture Notes in Business Information Processing, 320–21. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-20677-1_25.

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

Rychlý, Marek, and Pavlína Tichá. "A Tool for Supporting Feature-Driven Development." In Balancing Agility and Formalism in Software Engineering, 196–207. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-85279-7_16.

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

Cichocki, Przemyslaw, and Alessandro Maccari. "Empirical Analysis of a Distributed Software Development Project." In Balancing Agility and Formalism in Software Engineering, 169–81. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-85279-7_14.

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

Silingas, Darius, and Ruslanas Vitiutinas. "Towards UML-Intensive Framework for Model-Driven Development." In Balancing Agility and Formalism in Software Engineering, 116–28. Berlin, Heidelberg: Springer Berlin Heidelberg, 2008. http://dx.doi.org/10.1007/978-3-540-85279-7_10.

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

Conference papers on the topic "Agility in Software Development"

1

Houston, Dan X. "Agility beyond software development." In the 2014 International Conference. New York, New York, USA: ACM Press, 2014. http://dx.doi.org/10.1145/2600821.2600837.

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

Patel, C., M. Lycett, R. Macredie, and S. de Cesare. "Perceptions of Agility and Collaboration in Software Development Practice." In Proceedings of the 39th Annual Hawaii International Conference on System Sciences (HICSS'06). IEEE, 2006. http://dx.doi.org/10.1109/hicss.2006.378.

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

Shawky, Doaa M., and Ahmed F. Ali. "A practical measure for the agility of software development processes." In 2010 2nd International Conference on Computer Technology and Development (ICCTD). IEEE, 2010. http://dx.doi.org/10.1109/icctd.2010.5645881.

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

Morien, Roy, and Pornpit Wongthongtham. "Supporting agility in software development projects - defining a project ontology." In 2008 2nd IEEE International Conference on Digital Ecosystems and Technologies (DEST). IEEE, 2008. http://dx.doi.org/10.1109/dest.2008.4635218.

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

Dorairaj, Siva, and James Noble. "Agile Software Development with Distributed Teams: Agility, Distribution and Trust." In 2013 Agile Conference (AGILE). IEEE, 2013. http://dx.doi.org/10.1109/agile.2013.7.

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

Dingsøyr, Torgeir, Nils Brede Moe, and Helena Holmström Ohlsson. "Towards an understanding of scaling frameworks and business agility." In XP '18 Companion: 19th International Conference on Agile Software Development. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3234152.3234176.

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

Mikio Ikoma, Masayuki Ooshima, Takahiro Tanida, Michiko Oba, and Sanshiro Sakai. "Using a validation model to measure the agility of software development in a large software development organization." In 2009 31st International Conference on Software Engineering - Companion Volume. IEEE, 2009. http://dx.doi.org/10.1109/icse-companion.2009.5070967.

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

Weitzel, Balthasar, Dominik Rost, and Mathias Scheffe. "Sustaining Agility through Architecture: Experiences from a Joint Research and Development Laboratory." In 2014 IEEE/IFIP Conference on Software Architecture (WICSA). IEEE, 2014. http://dx.doi.org/10.1109/wicsa.2014.38.

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

Escobar-Sarmiento, Victor, and Mario Linares-Vasquez. "A model for measuring agility in small and medium software development enterprises." In 2012 XXXVIII Conferencia Latinoamericana En Informatica (CLEI). IEEE, 2012. http://dx.doi.org/10.1109/clei.2012.6427226.

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

L. Cooper, Kendra. "Can Agility be Introduced into Requirements Engineering for COTS Component Based Development?" In 2006 International Workshop on Software Product Management (IWSPM'06 - RE'06 Workshop). IEEE, 2006. http://dx.doi.org/10.1109/iwspm.2006.2.

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

Reports on the topic "Agility in Software Development"

1

Dow, Stephen J. Trainer Software Development. Fort Belvoir, VA: Defense Technical Information Center, October 2001. http://dx.doi.org/10.21236/ada396902.

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

Baskinger, Patricia J., Larry Ozarow, and Mary C. Chruscicki. Speakeasy Software Development. Fort Belvoir, VA: Defense Technical Information Center, August 1993. http://dx.doi.org/10.21236/ada283816.

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

Ellison, Robert J. Software Development Environments. Fort Belvoir, VA: Defense Technical Information Center, July 1986. http://dx.doi.org/10.21236/ada181742.

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

Piercey, R. B. Gammasphere software development. Office of Scientific and Technical Information (OSTI), January 1993. http://dx.doi.org/10.2172/6561547.

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

Forney, Glenn P., and Walter W. Jones. Software development tools. Gaithersburg, MD: National Institute of Standards and Technology, 1990. http://dx.doi.org/10.6028/nist.ir.4363.

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

Luqi. Documentation Driven Software Development. Fort Belvoir, VA: Defense Technical Information Center, June 2010. http://dx.doi.org/10.21236/ada532459.

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

de Vaulx, Frederic, paul Khouri Saba, Marcus Newrock, and Bertrand Stivalet. Initiating mobile software development :. Gaithersburg, MD: National Institute of Standards and Technology, 2011. http://dx.doi.org/10.6028/nist.ir.7838.

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

Manna, Zohar. Next Generation Software Development. Fort Belvoir, VA: Defense Technical Information Center, January 2005. http://dx.doi.org/10.21236/ada435087.

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

Peatman, William C. Nanoelectronic Modeling Software Development. Fort Belvoir, VA: Defense Technical Information Center, March 1998. http://dx.doi.org/10.21236/ada340531.

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

Hsu, Y. L., Juan F. Reynaud, and Ernst W. Schwiderski. Tidal Atlas Software Development. Fort Belvoir, VA: Defense Technical Information Center, December 1993. http://dx.doi.org/10.21236/ada275251.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Agility in Software Development' for particular source types:
Journal articles Dissertations / Theses Books
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