Relevant bibliographies by topics / Agile systems development methodologies

Contents

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

Academic literature on the topic 'Agile systems development methodologies'

Author: Grafiati
Published: 4 June 2021
Last updated: 10 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 'Agile systems development methodologies.'

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 "Agile systems development methodologies"

1

Binsaleh, Muazzan, and Shahizan Hassan. "Systems Development Methodology for Mobile Commerce Applications." International Journal of Online Marketing 1, no. 4 (October 2011): 33–47. http://dx.doi.org/10.4018/ijom.2011100103.

Full text
Abstract:
There are several systems development methodologies including traditional and agile methodologies being utilized in current systems development. However, it could be argued that when developing mobile commerce applications, suitable development framework should be investigated as these applications are utilized in different contexts from fixed ecommerce applications. This study identifies suitable system development methodology framework for mobile commerce applications. In order to achieve this aim, the practitioners from seven organizations were asked to provide information about their development methodologies by answering the questions regarding mobile commerce application development. The questions were opened and aimed to explore practitioner’s perspectives on the development methodologies. From the practitioner’s perspectives, it was found that there were several development methodologies being used in mobile commerce application development and these can be classified into two different development frameworks which are heavyweight/traditional and lightweight/agile methodologies. The suitable methodology framework for mobile commerce application development thus was identified.
APA, Harvard, Vancouver, ISO, and other styles
2

Shahzeb Hussain, Namrata Bhadri, and Syed Razauddin Shahlal. "Factors Influencing the Efficacy of Agile Usage." International Journal of Engineering and Management Research 10, no. 5 (October 5, 2020): 1–4. http://dx.doi.org/10.31033/ijemr.10.5.1.

Full text
Abstract:
Agile techniques that utilize iterative development are broadly used in various industry projects as a lightweight development technique which can satisfy the continuous changes of requirements. Short repetitions are used that are required for efficient product delivery. Traditional and old software development methods are not much efficient and effective to control the rapid change in requirements. Despite the benefits of Agile, criticism on agile methodology states that it couldn’t succeed to pay attention to architectural and design issues and therefore is bound to produce small design-decisions. The past decade has observed numerous changes in systems development with many organizations accepting agile techniques as a viable methodology for developing systems. An increase in the number of research studies reveals the growing demand and acceptance of agile methodologies. While most research has focused on acceptance rate and adaptation of agile practices, there is very limited knowledge of their post-adoption usage and incorporation within organizations. Several factors explain the effective usage of agile methodologies. A combination of previous research in Agile Methodologies, Diffusion of Innovations, Information Systems implementation, and Systems Development has been carried out to develop a research model that identifies the main factors relevant to the propagation and effective usage of agile methodologies in organizations.
APA, Harvard, Vancouver, ISO, and other styles
3

Stormi, Kati Tuulikki, Teemu Laine, and Tuomas Korhonen. "Agile performance measurement system development: an answer to the need for adaptability?" Journal of Accounting & Organizational Change 15, no. 2 (June 3, 2019): 231–56. http://dx.doi.org/10.1108/jaoc-09-2017-0076.

Full text
Abstract:
Purpose The purpose of this study is to reflect upon the feasibility of agile methodologies, Scrum in particular, to supplement the procedural design and implementation of performance measurement systems (PMS). Design/methodology/approach The study is an interventionist case study that applied agile methodologies in the PMS development. Researchers actively participated in the PMS development, e.g. researchers designed some of the performance measurement prototypes in order to facilitate the agile development. Findings The study outlines an agile approach suitable for PMS development. The paper answers the topical needs for adaptability and agility in management accounting, by applying agile methodologies into PMS development. PMS development does not take place only as a project or process that systematically progresses from the measure selection to measure implementation. Instead, as the requirements for the PMS change during the development project, management may reject some measures and new measures emerge as the understanding about changing situations increase. Agile methodologies are a methodological way to respond to the inevitable change and to enhance management accounting adaptability. Research limitations/implications This study contributes to the PMS literature by proposing that agile development methodologies can advance organizational features that increase management accounting adaptability. As a result, the study proposes a new approach for PMS development to supplement existing ones. Agile methodologies are especially suitable for extending the PMS in new, yet relatively immature areas of performance measurement. The new approach applies Scrum principles in PMS development. By drawing from the theories of performance measurement (system) development and enabling PMS, the paper furthers academic understanding about agile development of accounting information systems. Practical implications Companies can use the proposed approach in PMS development, particularly after the initial system implementation in redesigning the system. The approach may increase the PMS impact in organizations and prevent PMS implementation failures. Originality/value The paper identifies the potential of using agile methodologies to enhance PMS adaptability and provides preliminary evidence of the potential of such approach in supplementing processual PMS development frameworks.
APA, Harvard, Vancouver, ISO, and other styles
4

Khan, Rashid Ali, Muhammad Faisal Abrar, Samad Baseer, Muhammad Faran Majeed, Muhammad Usman, Shams Ur Rahman, and You-Ze Cho. "Practices of Motivators in Adopting Agile Software Development at Large Scale Development Team from Management Perspective." Electronics 10, no. 19 (September 24, 2021): 2341. http://dx.doi.org/10.3390/electronics10192341.

Full text
Abstract:
Agile software development methodologies have become the most popular software development methods in the last few years. These methodologies facilitate rapid development. The low cost and prioritized user satisfaction make these methodologies more attractive. These methodologies were also intended for small scale developmental teams. Therefore, challenges were encountered when these methodologies were used in large-scale development teams. This study was based on the identification of factors which were discovered in our previous study. Some of the factors included “leadership strong commitment and team autonomy”, “cooperative organizational culture”, and “team competency—agile development expertise”. A total of 147 practices were identified in this study via a systematic literature review. These practices will help practitioners and project managers to adopt agile software methodologies and encourage them to the enhance them.
APA, Harvard, Vancouver, ISO, and other styles
5

Madadipouy, Kasra. "An Examination and Evaluation of Agile Methodologies for Systems Development." Australasian Journal of Computer Science 2, no. 1 (January 15, 2014): 1–17. http://dx.doi.org/10.3923/aujcs.2015.1.17.

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

Bushuyev, S., S. Murzabekova, and M. Khussainova. "COMPETENCE APPROACH IN AGILE TRANSFORMATION OF EDUCATION ESTABLISHMENT." Scientific Journal of Astana IT University, no. 5 (July 27, 2021): 52–62. http://dx.doi.org/10.37943/aitu.2021.97.75.005.

Full text
Abstract:
The subject of the article is development of project, programs and project portfolios management systems with drivers of innovation in Agile transformation of Education Establishment is considered. Substantial changes in the environment require further research into the effectiveness of the application of existing agile methodologies, knowledge systems and competencies of project managers and their leadership. The foundations of environmental change lie in changing the decision-making paradigm in innovation project and programs management in Agile transformation of Education Establishment. The goal is to explore modern approaches to leadership formation when applying agile methodologies of its specificity from the point of view of decision-making processes in project management. The problems of leadership creation and development in the application of agile project management methodologies for the implementation of information and communication systems are considered. The results of studies were conducted on the basis of a competency-based approach modelled by the International Project Management Association. The content model of competency of the leader applying agile management is presented. Conclusion: The Agile leadership and leadership behaviour patterns are formed in a project management behavioural competency system based on agile technology methods and tools. These competencies included: Self-reflection and self-management, Personal integrity and reliability, Personal communication, Relationships and interaction, Leadership, Teamwork, Conflicts and crises, Inventiveness, Reconciliation, and Orientation to results. The patterns of project managers' behaviour as agile leaders in project product creation and agile project management are explored. The differences in the behaviour patterns of leaders and agile leaders were examined by behavioural competencies within the identified key competency indicators. Such patterns allowed the authors to identify bottlenecks in the application of agile project management methodologies in the context of the development of innovative products of innovation systems.
APA, Harvard, Vancouver, ISO, and other styles
7

Ríos, Jimmy Molina, and Nieves Pedreira-Souto. "Approach of Agile Methodologies in the Development of Web-Based Software." Information 10, no. 10 (October 13, 2019): 314. http://dx.doi.org/10.3390/info10100314.

Full text
Abstract:
The current inclusion of agile methodologies in web-oriented projects has been considered on a large-scale by software developers. However, the benefits and limitations go beyond the comforts that project managers delimit when choosing them. Selecting a methodology involves more than only the associated processes or some documentation. Based on the above, we could define as the main concerns the approach with which we identify the methodology, the needs of the company, the size, and qualities of the project, and especially the characteristics of agile development that they possess. However, there are several difficulties in selecting the most appropriate methodology due to the features in common; Will it be suitable for my project? What challenges will be presented in the process? Will my team understand each stage? Will I be able to deliver software that satisfies the client? Project managers create these questions, which seem manageable but have huge effects. This paper presents a systematic literature review based on the analysis of the approaches of six web development methodologies. The aim of the study is to analyze the approaches presented by relevant methodologies, identifying their common agile characteristics and managing to contrast both its benefits and limitations during a project. As a result, we could itemize five common features, which are presented within the processes; (1) flexibility, (2) constant communication of the workgroup, (3) use of UML, (4) the inclusion of the end-user and (5) some documentation.
APA, Harvard, Vancouver, ISO, and other styles
8

Binsaleh, Muazzan, and Shahizan Hassan. "Systems Development Methodology for Mobile Commerce Applications." International Journal of Mobile Computing and Multimedia Communications 3, no. 4 (October 2011): 36–52. http://dx.doi.org/10.4018/jmcmc.2011100103.

Full text
Abstract:
There are several methodologies, including traditional and agile methodologies, being utilized in current systems development. However, it could be argued that existing development methodologies may not be suitable for mobile commerce applications, as these applications are utilized in different contexts from fixed e-commerce applications. This study proposes a system development methodology for mobile commerce applications. In order to achieve this aim, four objectives are proposed: investigating existing systems development methodologies used to develop mobile commence applications, identifying strengths and weaknesses of existing development methodologies, construction of a suitable methodology for mobile commerce applications, and testing for its applicability and practicality. The research methodology used in the study is the design research, which includes the steps of awareness of problems, suggestion, development, evaluation and conclusion. However, this paper only focuses on the first two phases of the whole study, which are awareness of the problem and making suggestions, while the evaluation and conclusion will be conducted as future works.
APA, Harvard, Vancouver, ISO, and other styles
9

Kendall, Kenneth E., Sue Kong, and Julie E. Kendall. "The Impact of Agile Methodologies on the Quality of Information Systems." International Journal of Strategic Decision Sciences 1, no. 1 (January 2010): 41–56. http://dx.doi.org/10.4018/jsds.2010103003.

Full text
Abstract:
Systems developers and IT project managers who apply agile methods for developing information systems (IS) subscribe to a set of values and principles. This adherence to a set of values and principles, along with a passion or fervor surrounding the agile philosophy, made us question whether the adoption of agile methodologies has an effect on information systems built, and in particular, the quality of the IS developed. In this paper we construct a conceptual model, conduct a survey of software developers, and analyze our results, which support our hypotheses about the importance of the strategic selection of a development methodology. We conclude that practicing project managers should consider the decision to use certain methodologies as part of the strategic process.
APA, Harvard, Vancouver, ISO, and other styles
10

Onokoy, L. S. "Flexible approaches to the development of software: evolution and prospects of development." Quality. Innovation. Education, no. 1 (2021): 57–67. http://dx.doi.org/10.31145/1999-513x-2021-1-56-66.

Full text
Abstract:
The article is devoted to the study of fiexible approaches (Agile) to the design of information systems software. Much attention is paid to the comparative analysis of currently popular fiexible methodologies, including the DevOps (Development and Operation) methodology [4], [5], which covers the entire life cycle of creating a software product. In conclusion, based on the conducted research, the author reveals the global and Russian trends in the development of Agile and formulates their development prospects.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Agile systems development methodologies"

1

Kalubila, Muriel Chibwe. "The contingent use of agile systems development methodologies / M.C. Kalubila." Thesis, North-West University, 2012. http://hdl.handle.net/10394/9778.

Full text
Abstract:
Over the years, organizations have seen fit to adopt the use of agile systems development methodologies (ASDMs) because of the benefits that they offer, such as flexibility and the ability to deliver products faster, in constantly changing environments. When ASDMs are used in projects, they are made to fit or be suitable for a project‟s unique aspects, such as its size, requirements, scope and outcomes. This is known as the contingent use of ASDMs. Little is known about the contingent use of ASDMs in South African organizations. It is not known whether it is happening, its procedure and its success. It is important to know this because quality and control need to be maintained in systems produced. There is always a danger that the benefits of using a system development methodology (SDM) would be lost if ASDMs are highly adapted. This led to an investigation of three organizations in South Africa that use contingent ASDMs. With the help of semi-structured interviews, focus groups and documents, data was collected that was analysed, using the tool ATLAS.ti, and the analysis methods content and cross-case analysis. It was found that some South African organizations in the telecommunications, consulting, technological, outsourcing and agricultural sectors use ASDMs in combination with the still popular waterfall SDM. Compatibility between the SDM and the project is a factor in some organizations. Scrum was cited to be the ASDM that was used in some of the organizations interviewed due to its maturity. They make ASDMs contingent by using aspects in the methods, such as Scrum, that are useful for their unique projects. These aspects are in some cases combined with other SDMs to form hybrid methodologies. Some organizations use criteria, such as project needs, outcomes, size and complexity to make ASDMs contingent. Some organizations have measures and facilities in place to manage, monitor, control and document the process used to make ASDMs contingent. They make use of contingent ASDMs as they have experienced more success with them and they will continue to do so.
Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.
APA, Harvard, Vancouver, ISO, and other styles
2

Garcia, Erik Roberto. "Resource dependencies in parallel development of military systems : a comparison of waterfall and agile development methodologies." Thesis, Massachusetts Institute of Technology, 2014. http://hdl.handle.net/1721.1/105297.

Full text
Abstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, 2014.
DVD-ROM contains supplemental models: four .mdl files and two .vdf files.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 63-64).
The United States Department of Defense has been plagued with failing programs that are over budget, behind schedule, and exhibit poor performance during testing. Once a program has cost, schedule, or capability issues, follow-on development efforts adopt the underlying issues only to reinforce poor performance. To address these issues that lead to firefighting, one option is to use an Agile software development process to introduce capabilities earlier in the development process for effective testing. Two System Dynamics models compare Agile with the traditional Waterfall development approach to determine: if Agile development reduces the conflict between cost, schedule, and capability constraints; if Agile development reduces firefighting; and will Agile development impact other development tasks. Based on the simulation of each model, Agile did improve the dynamics of parallel development cycles by maximizing the productivity of the entire development team. Under the same System and Software Engineering team size and development release schedule, Agile development increases the quantity of requirements introduced within a development cycle. However, Agile development emphasized less on maturing new technologies leading to considerably less innovative builds. Thesis Supervisor:
by Erik Roberto Garcia.
S.M. in Engineering and Management
APA, Harvard, Vancouver, ISO, and other styles
3

Noruwana, Nimrod. "How do South African organisations adopt agile methodologies for software development in practice?" Master's thesis, University of Cape Town, 2010. http://hdl.handle.net/11427/11708.

Full text
Abstract:
Includes bibliographical references (leaves 81-90).
Before organisations adopt agile methods, they need to ensure that they are prepared for the change. They also need to understand the problems they are trying to address by adopting agile methods. Agile methods deviate substantially from traditional methods of systems development (Tolfo & Wazlawick, 2008). This, therefore, makes it difficult for organisations to adopt agile methods even though they might see them attractive, as the adoption of such methods has an effect on organisational culture. If the culture cannot accommodate an agile approach, then the organisation will not be able to adopt agile (Lindvall, Basisli, Boehm, Costa, Dangle, Shull, Teseriero, Williams & Zelkowitz, 2002). Having a culture that is conducive to the adoption of agile methods is almost unanimously perceived by agile experts to be a necessary factor for the introduction of agile methodologies (eWorkshop, 2002). It is also important to understand the phases organisations go through during the process of adopting agile methods.
APA, Harvard, Vancouver, ISO, and other styles
4

Delcheva, Yana. "Challenges during the transition to Agile methodologies : A holistic overview." Thesis, Internationella Handelshögskolan, Högskolan i Jönköping, IHH, Informatik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-40692.

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

Tabrez, Shams, and Islam Jan. "Documentation and Agile Methodology." Thesis, Uppsala universitet, Institutionen för informatik och media, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-212653.

Full text
Abstract:
Computer science in general and software engineering in specific is changing very fast. Software engineers are constantly using more innovative and more efficient ways to develop new software than in the past. This continuous evolution of software development methodologies has a great impact on both the software developed and the environment that the developers work-in. Agile software development methodologies are used to overcome many issues in the software development processes. One of the issues which still exists and needs to be addressed is the preparation of proper documentation along with the software. The work presented in this dissertation focuses on software documentation. The work starts by a thorough literature review which focuses on different aspects of software documentation and different agile methodologies. The thesis focuses on finding out the challenges that the developers faces during their development process. Two major questions addressed in the thesis. First one is to find the motivation to document in agile envirionment, whih is based on the hypothesis that there do exist a motivation. The second question is that how should documentation be produced such that we could avoid maximum possible potential problems. These questions are addressed with the help of different perspectives of the stockholders (i.e. developers and users) and the existing methods for documentation. A questionnaire was developed based on the nine categories of documentation, like user documents and system documents etc.. It included different questions related to the types of documents created in software development processes, the software development stage at which the documents are created and the importance of the documents. Questions from this questionnaire are then posted on agile specific discussion forums. Where many experienced and fresh practitioners participated in the discussion. We had a detailed discussion on every component of documentation and problems were identified by the practitioners. The questionnaire was also sent to different companies practicing agile methodology. we received about 14 responses as it was detailed questionnaire with about 34 questions. The responses of the discussion forum and survey are then analyzed and conclusions were drawn. The conclusions include that all the participants consider software documentation very important to the success of a software development project. the question of motivation is answered from the literature and opinions we received from experienced practitioners. While seven factor are identified that affect your documentation, to help solve the question of how should documentation be done.
APA, Harvard, Vancouver, ISO, and other styles
6

Wagener, Ruhan Pieter. "Investigating critical success factors in agile systems development projects / Ruhan Wagener." Thesis, North-West University, 2012. http://hdl.handle.net/10394/9251.

Full text
Abstract:
This study investigates the critical success factors involved in agile systems development projects. Various systems development methodologies and project management methodologies are presented with their underlying principles, strengths and weaknesses. Thereafter the critical success factors adopted from the work of Chow and Cao (2007) are presented. A positivistic research paradigm was chosen for data collection and analysis. The survey method was chosen for data collection. A questionnaire was sent to multiple respondents in a predominantly agile work environment, which resulted in a total of 129 respondents in various business sectors. The results were analysed by implementing multiple correlation and regression statistics as well as descriptive statistics. The results show that there are in fact 16 critical success factors that have a direct impact on the success of agile systems development projects. Agile systems development methodologies have been increasing in use during the last 3 years, and most organisations are implementing some form of project management methodology. The first recommendation is based on the findings that strong customer involvement and the appropriate management of the agile process with a satisfactory amount of documentation resulted in greater process success. Therefore, organisations should encourage these critical success factors when implementing an ASDM as this has a positive effect on the project outcome. The appropriate management of the agile process with a satisfactory amount of documentation, the application of good design practices and technical knowledge to a project, and a cooperative organizational culture instead of hierarchical are three of the key critical success factors that were positively related to the success of the product. By focussing on these critical success factors, the success of the entire project can be predicted.
Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.
APA, Harvard, Vancouver, ISO, and other styles
7

Mazengera, Bruce Mwai Analinafe. "The use of agile systems development methodologies in the telecommunication industry in South Africa / B.M. Mazengera." Thesis, North-West University, 2009. http://hdl.handle.net/10394/5039.

Full text
Abstract:
Over the last decade, systems development professionals have recognised the need to use agile systems development methodologies (ASDMs) in the telecommunication industry. This is partly due to the barriers identified by Mansurov (2000) which suggest that the use of agile methodologies in the telecommunication industry would reduce the ratio of time-to-market. In the South African context, the industry has cemented its position as a major driving force of the economy as a whole. The industry's level of competitiveness is in part informed by the information technology practices that it follows, and hence systems development is deemed to be a crucial and value-adding component of the environment This research therefore aims to investigate the systems development practices currently being used in the telecommunication industry of South Africa, as well as the perceived sentiments towards the use of ASDMs. The investigation into the level of applicability of ASDMs in the industry is largely informed by literature from agile proponents which suggest that ASDMs are highly suitable to projects where the user requirements continuously change. In order to identify the current SD practices followed and the sentiments towards ASDMs in the telecommunication industry, the interpretive paradigm was used. Three prominent organisations were identified and case studies were conducted at each of these companies. The data collection method used was a combination of semi-structured interviews and questionnaires, and the data analysis tools were ATLAS.ti for the semi-structured interviews and SPSS for the questionnaires. Thereafter, the data collected was analysed by using the cross-case analysis method. The results indicated that the incumbent companies in the telecommunication industry used an SDM that followed the waterfall approach, and the use of ASDMs was informed by a multitude of factors.
Thesis (M.Sc. (Computer Science))--North-West University, Potchefstroom Campus, 2010.
APA, Harvard, Vancouver, ISO, and other styles
8

Grey, Johannes. "An investigation of the suitability of agile system development methodologies for the development of data warehouses / J. Grey." Thesis, North-West University, 2006. http://hdl.handle.net/10394/1596.

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

Tavares, João Luís Boleto. "Metodologias híbridas no desenvolvimento de sistemas embebidos." Master's thesis, Instituto Superior de Economia e Gestão, 2019. http://hdl.handle.net/10400.5/20038.

Full text
Abstract:
Mestrado em Gestão de Projetos
Nos últimos 20 anos, as metodologias ágeis têm vindo a afirmar-se como uma referência metodológica nos projetos de desenvolvimento de software. Esta realidade alicia muitos gestores a identificarem a necessidade de implementar esta abordagem no desenvolvimento de sistemas embebidos. Todavia, esta tarefa torna-se complexa devido à natureza deste tipo de projetos. Por esta razão têm surgidos propostas de utilização de metodologias híbridas, que são uma abordagem de desenvolvimento que combina práticas ágeis e tradicionais. No entanto, a sua utilização atual tem sido relatada como pouco estruturada, não havendo um enquadramento claro dos benefícios para o desenvolvimento destes sistemas específicos. Assim, este estudo pretende aprofundar o conhecimento atual sobre as práticas correntes no âmbito da utilização das metodologias, explorando e mapeando-as, em particular no que toca às metodologias híbridas. Foram realizadas quatro entrevistas semi-estruturadas para ganhar um maior entendimento sobre o contexto que leva à utilização de metodologias híbridas no desenvolvimento de sistemas embebidos. Posteriormente, foi aplicado um questionário a 132 profissionais da área dos quais se 68 forneceram respostas válidas. A análise dos resultados revelou que as metodologias mais utilizadas em Portugal não diferem das anteriormente reportadas na literatura. Porém, foi possível estabelecer uma dependência estatística entre as metodologias Scrum e Waterfall, confirmando a existência e utilização da metodologia híbrida Water-Scrum-Fall
Across the last 20 years, agile methodologies have substantially increased their influence on software and systems development. This reality encourages many managers to identify the need to implement this approach in embedded systems development projects. However, this task becomes very complex due to the nature of such development projects. For this reason, efforts have been made to use hybrid methodologies, which are a development approach that combines agile and traditional practices. Nevertheless, this use has been reported as unstructured and without a clear framework for the benefits to the development of these specific systems. Thus, this study intends to expand the current knowledge about current practices in the use of methodologies, exploring and mapping them, namely concerning hybrid methodologies. Four semi-structured interviews were conducted to acquire a deeper understanding of the reasons that lead to the use of hybrid methodologies in the development of embedded systems. Subsequently, a questionnaire was applied to 132 professionals in the area of embedded system development, from which 68 provided valid answers were collected. The analysis of the results revealed that the most used methodologies in Portugal do not differ from those previously reported in the literature. Still, it was possible to establish a statistical dependence between Scrum and Waterfall methodologies, confirming the existence and application of the Water-Scrum-Fall hybrid methodology.
info:eu-repo/semantics/publishedVersion
APA, Harvard, Vancouver, ISO, and other styles
10

Gislen, Mikael. "Dysfunctional aspects of Software Development : An analysis of how lip-service, deception and organisational politics may side-track the result of well-intended methodologies." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5445.

Full text
Abstract:
This paper tries to identify and understand the human social obstacles for developing quality software. These include lip-service, cutting corners, deception and effects of internal politics. These obstacles can undermine the good intentions behind the software methodologies. The paper draws from the literature in different disciplines and uses an ethnographic research methodology to create a rich picture of the concerning aspects in the framework of one software development company in India. What stands out among the findings are that internal audits has mainly focused on finding errors in documentation procedures but study of the actual practices has often been shallow. In addition the understanding of business risks by the internal auditors have often been weak. Context. The human based obstacles affecting Software Development Methodology analysed in the context of an ISO 9000 quality system in an Indian Software Development company working mainly with Swedish companies. Objectives. Identifying and increasing the understanding of intrinsic negative social aspects such as lip service, cheating and politics which are affecting the results of Software Development Methodologies and if possible suggest some means to mitigate them. In particular to create a deeper understanding of why people cheat and pay lip service to methodologies and to try to understand the political aspects of methodology and quality systems. There are other positive social aspects, but they are not considered since the objective is about understanding the negative aspects and possibly mitigate them. Methods. Ethnographic research using analysis of ISO 9000 and design artefacts, semi-structured interviews, participation in internal audits, Results. Most focus in audits was on documentation and very less focus on underlying methodologies, some indications of lip-service to process and processes were also mainly managed on a higher level in the organization while the understanding and practices were less well established on lower level. It was hard to get a grip on the internal political aspects since the perception of the subject in the informants view was that it is mainly malicious and therefore embarrassing to speak about. Some conflicts between internal quality goals and customers’ needs were also identified. Conclusions. An ethnographic research methodology gives a rich picture. The analysis gives deeper understanding of the problem areas, but not necessary solutions. The author suggests that at the heart of the problem is a difference in world view. Software professionals generally tend to resolve [technical] problems using a reductionist approach, while these intricate challenges cannot easily be resolved by this approach. A more holistic systemic approach is required and while the software methodology is useful to structure the development it does not resolve these dysfunctions. They have to be resolved on another level. It was also found that further studies is required in particular to better understand Internal politics, the effect of Positive and Negative Incentives, the effect of software metrics on quality performance and subjectivity in customers’ perception and expectation.
Uppsatsen försöker förstå mänskliga sociala hinder för att utveckla programvara med hög kvalitet. Dessa hinder inkluderar "läpparnas bekännelser", ta genvägar, vilseleda och internpolitik. Sådana hinder kan underminera utvecklingsmetoder. Denna uppsats bygger på literatur från olika discipliner och använder etnografisk forskningsmetodik för att skapa en rik bild av dessa oroande aspekter inom ramen för ett IT-företag i Indien. Vad står ut är att intern kvalitetsrevision fokuserar för mycket på att finna fel i dokumentationsprocesser medan revision av hur utvecklingsarbetet faktiskt sker har varit för ytligt. Dessutom har de interna revisorernas förståelse av affärsrisker varit svag.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Agile systems development methodologies"

1

Crowder, James A., and Shelli Friess. Systems Engineering Agile Design Methodologies. New York, NY: Springer New York, 2013. http://dx.doi.org/10.1007/978-1-4614-6663-5.

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

Crowder, James A. Systems Engineering Agile Design Methodologies. New York, NY: Springer New York, 2013.

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

Mirtalebi, Mohsen. Embedded Systems Architecture for Agile Development. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3051-0.

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

G, Fitzgerald, ed. Information systems development: Methodologies, techniques, and tools. Oxford [England]: Blackwell Scientific Publications, 1988.

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

G, Fitzgerald, ed. Information systems development: Methodologies, techniques, and tools. 3rd ed. London: McGraw-Hill, 2003.

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

G, Fitzgerald, ed. Information systems development: Methodologies, techniques and tools. 4th ed. London: McGraw-Hill, 2006.

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

Avison, D. E. Information systems development: Methodologies, techniques, and tools. Oxford [England]: Blackwell Scientific Publications, 1994.

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

Appelo, Jurgen. Management 3.0: Leading Agile developers, developing Agile leaders. Upper Saddle River, NJ: Addison-Wesley, 2011.

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

Hafedh, Mili, and SpringerLink (Online service), eds. Agile Business Rule Development: Process, Architecture, and JRules Examples. Berlin, Heidelberg: Springer-Verlag Berlin Heidelberg, 2011.

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

Tom, Poppendieck, ed. Lean software development: An agile toolkit. Boston: Addison-Wesley, 2003.

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

Book chapters on the topic "Agile systems development methodologies"

1

Buchalcevova, A. "Research of the Use of Agile Methodologies in the Czech Republic." In Information Systems Development, 51–64. Boston, MA: Springer US, 2008. http://dx.doi.org/10.1007/978-0-387-68772-8_5.

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

Mikulenas, Gytenis, and Kestutis Kapocius. "A Framework for Decomposition and Analysis of Agile Methodologies During Their Adaptation." In Information Systems Development, 547–60. New York, NY: Springer New York, 2010. http://dx.doi.org/10.1007/978-1-4419-7355-9_46.

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

Jander, Kai, Lars Braubach, Alexander Pokahr, and Winfried Lamersdorf. "Validation of Agile Workflows Using Simulation." In Languages, Methodologies, and Development Tools for Multi-Agent Systems, 39–55. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22723-3_3.

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

Cawley, Oisín, Xiaofeng Wang, and Ita Richardson. "Lean/Agile Software Development Methodologies in Regulated Environments – State of the Art." In Lean Enterprise Software and Systems, 31–36. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-16416-3_4.

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

Nerur, Sridhar, Alan Cannon, VenuGopal Balijepally, and Philip Bond. "Towards an Understanding of the Conceptual Underpinnings of Agile Development Methodologies." In Agile Software Development, 15–29. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12575-1_2.

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

Ivanov, Vladimir, Sergey Masyagin, Alan Rogers, Giancarlo Succi, Alexander Tormasov, Jooyong Yi, and Vasily Zorin. "Comparison of Agile, Quasi-Agile and Traditional Methodologies." In Advances in Intelligent Systems and Computing, 128–37. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-14687-0_11.

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

Fitzgerald, Brian. "Systems Development Methodologies." In Systems Development Methods for the Next Century, 127–39. Boston, MA: Springer US, 1997. http://dx.doi.org/10.1007/978-1-4615-5915-3_12.

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

Crowder, James A., and Shelli Friess. "Introduction." In Systems Engineering Agile Design Methodologies, 1–7. New York, NY: Springer New York, 2013. http://dx.doi.org/10.1007/978-1-4614-6663-5_1.

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

Crowder, James A., and Shelli Friess. "The Psychology of Change." In Systems Engineering Agile Design Methodologies, 9–14. New York, NY: Springer New York, 2013. http://dx.doi.org/10.1007/978-1-4614-6663-5_2.

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

Crowder, James A., and Shelli Friess. "The Modern Design Philosophy: Avoiding Change is Perilous." In Systems Engineering Agile Design Methodologies, 15–18. New York, NY: Springer New York, 2013. http://dx.doi.org/10.1007/978-1-4614-6663-5_3.

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

Conference papers on the topic "Agile systems development methodologies"

1

Keramati, Hossein, and Seyed-Hassan Mirian-Hosseinabadi. "Integrating software development security activities with agile methodologies." In 2008 IEEE/ACS International Conference on Computer Systems and Applications (AICCSA). IEEE, 2008. http://dx.doi.org/10.1109/aiccsa.2008.4493611.

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

Hildenbrand, Tobias, Michael Geisser, Thomas Kude, Denis Bruch, and Thomas Acker. "Agile Methodologies for Distributed Collaborative Development of Enterprise Applications." In 2008 International Conference on Complex, Intelligent and Software Intensive Systems. IEEE, 2008. http://dx.doi.org/10.1109/cisis.2008.105.

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

Quelal, Rosa E., Monica Villavicencio, and Luis E. Mendoza. "A survey of agile software development methodologies in Ecuador." In 2018 13th Iberian Conference on Information Systems and Technologies (CISTI). IEEE, 2018. http://dx.doi.org/10.23919/cisti.2018.8399186.

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

Cagle, Rick. "Enterprise Architecture facilitates adopting Agile development methodologies into a DoD acquisition." In 2012 6th Annual IEEE Systems Conference (SysCon). IEEE, 2012. http://dx.doi.org/10.1109/syscon.2012.6189431.

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

Gharaibeh, Natheer, Saleh M. Abu-Soud, Wafa Bdour, and Islah Gharaibeh. "Agile Development Methodologies: Are they suitable for developing Decision Support Systems." In 2009 Second International Conference on the Applications of Digital Information and Web Technologies (ICADIWT). IEEE, 2009. http://dx.doi.org/10.1109/icadiwt.2009.5273971.

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

Silva, Vanessa B. S., Fernando Schramm, and Adriana C. Damasceno. "A multicriteria approach for selection of agile methodologies in software development projects." In 2016 IEEE International Conference on Systems, Man, and Cybernetics (SMC). IEEE, 2016. http://dx.doi.org/10.1109/smc.2016.7844542.

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

Dyck, Sebastian, and Tim A. Majchrzak. "Identifying Common Characteristics in Fundamental, Integrated, and Agile Software Development Methodologies." In 2012 45th Hawaii International Conference on System Sciences (HICSS). IEEE, 2012. http://dx.doi.org/10.1109/hicss.2012.310.

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

Mudarikwa, Grace, and Thomas D. Grace. "Agile system development methodologies usage and acceptance in South African banking firms." In SAICSIT '18: 2018 Annual Conference of the South African Institute of Computer Scientists and Information Technologists. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3278681.3278711.

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

"Agile Models Need to be Bottom-up - Adding Productivity to a Late Project Makes it Later." In Special Session on Model Driven Development for Information Systems: Techniques, Tools and Methodologies. SciTePress - Science and and Technology Publications, 2012. http://dx.doi.org/10.5220/0004155903950400.

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

Silva, Marcos Antônio da, and Paloma Maira Oliveira. "DEVELOPMENT OF INTEGRATED SYSTEMS OF MANAGEMENT TO MICRO AND SMALL BUSINESSES USING METHODOLOGIES OF AGILE PROCESSES." In 10th CONTECSI International Conference on Information Systems and Technology Management. Sao Paulo: TECSI, 2013. http://dx.doi.org/10.5748/9788599693094-10contecsi/ps-11.

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

Reports on the topic "Agile systems development methodologies"

1

Cloutier, Robert, Ali Mostashari, Sara McComb, Abhijit Deshmukh, Jon Wade, Deanna Kennedy, and Peter Korfiatis. Investigation of a Graphical CONOPS Development Environment for Agile Systems Engineering. Fort Belvoir, VA: Defense Technical Information Center, October 2009. http://dx.doi.org/10.21236/ada548692.

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

Cloutier, Robert, Ali Mostashari, Sara McComb, Abhijit Deshmukh, Jon Wade, Deanna Kennedy, Peter Korfiatis, and Anne Carrigy. Investigation of a Graphical CONOPS Development Environment for Agile Systems Engineering - Phase 2. Fort Belvoir, VA: Defense Technical Information Center, May 2010. http://dx.doi.org/10.21236/ada545258.

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

Cloutier, Robert, Sara McComb, Abhijit Deshmukh, Teresa Zigh, Peter Korfiatis, Benham Esfahbod, Peizhu Zhang, and Keith Hall. Prototype of a Graphical CONOPS (Concept of Operations) Development Environment for Agile Systems Engineering. Fort Belvoir, VA: Defense Technical Information Center, March 2012. http://dx.doi.org/10.21236/ada582528.

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

Cloutier, Robert. Prototype of a Graphical CONOPS (Concept of Operations) Development Environment for Agile Systems Engineering. Fort Belvoir, VA: Defense Technical Information Center, August 2013. http://dx.doi.org/10.21236/ada604335.

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

Hossain, Niamat Ullah Ibne, Raed Jaradat, Michael Hamilton, Charles Keating, and Simon Goerger. A historical perspective on development of systems engineering discipline : a review and analysis. Engineer Research and Development Center (U.S.), April 2021. http://dx.doi.org/10.21079/11681/40259.

Full text
Abstract:
Since its inception, Systems Engineering (SE) has developed as a distinctive discipline, and there has been significant progress in this field in the past two decades. Compared to other engineering disciplines, SE is not affirmed by a set of underlying fundamental propositions, instead it has emerged as a set of best practices to deal with intricacies stemming from the stochastic nature of engineering complex systems and addressing their problems. Since the existing methodologies and paradigms (dominant pat- terns of thought and concepts) of SE are very diverse and somewhat fragmented. This appears to create some confusion regarding the design, deployment, operation, and application of SE. The purpose of this paper is 1) to delineate the development of SE from 1926-2017 based on insights derived from a histogram analysis, 2) to discuss the different paradigms and school of thoughts related to SE, 3) to derive a set of fundamental attributes of SE using advanced coding techniques and analysis, and 4) to present a newly developed instrument that could assess the performance of systems engineers. More than Two hundred and fifty different sources have been reviewed in this research in order to demonstrate the development trajectory of the SE discipline based on the frequency of publication.
APA, Harvard, Vancouver, ISO, and other styles
6

Lempert, Robert J., Michelle Miro, and Diogo Prosdocimi. A DMDU Guidebook for Transportation Planning Under a Changing Climate. Edited by Benoit Lefevre and Ernesto Monter Flores. Inter-American Development Bank, February 2021. http://dx.doi.org/10.18235/0003042.

Full text
Abstract:
The effects of climate-related natural hazards pose a significant threat to sustainable development in Latin America and the Caribbean (LAC) region and in particular its transportation sector. Risk Management provides an appropriate framework for assessing and mitigating the impacts of climate change and other climate-related natural hazards on transportation systems and choosing actions to enhance their resilience. However, analysts and policymakers involved in transportation planning, policy, and investment face significant challenges in managing the risks triggered by the effects of climate change. Climate change impacts the lifespan of roads, airports, and railroads as they have time horizons that surpass 40 years, thus making it harder (if not impossible) to forecast with confidence all relevant future events that will affect such infrastructure. In addition, the climate has already changed, so the return frequency of storms, for example, and other extreme events may now be different than suggested by the historical record in ways that are not always currently well understood. Implementing Risk Management under conditions of such uncertainty can prove difficult. Decision Making Under Deep Uncertainty (DMDU) enables Risk Management under conditions of Deep Uncertainty, that is when risks cannot confidently be quantified. This guidebook is aligned with the Disaster and Climate Change Risk Assessment Methodology for IDB projects (IDB 2018) and introduces and provides guidance on applying methods for Decision Making Under Deep Uncertainty (DMDU) to transportation planning. It presents the methodological steps that are necessary for the implementation of DMDU methodologies and reviews several such methods, including scenario planning, Adaptive Pathways, and robust decision making (RDM). This review is geared towards supporting the incorporation of DMDU methods into IDBs transportation sector funding and planning processes.
APA, Harvard, Vancouver, ISO, and other styles
7

Hunter, Fraser, and Martin Carruthers. Iron Age Scotland. Society for Antiquaries of Scotland, September 2012. http://dx.doi.org/10.9750/scarf.09.2012.193.

Full text
Abstract:
The main recommendations of the panel report can be summarised under five key headings:  Building blocks: The ultimate aim should be to build rich, detailed and testable narratives situated within a European context, and addressing phenomena from the longue durée to the short-term over international to local scales. Chronological control is essential to this and effective dating strategies are required to enable generation-level analysis. The ‘serendipity factor’ of archaeological work must be enhanced by recognising and getting the most out of information-rich sites as they appear. o There is a pressing need to revisit the archives of excavated sites to extract more information from existing resources, notably through dating programmes targeted at regional sequences – the Western Isles Atlantic roundhouse sequence is an obvious target. o Many areas still lack anything beyond the baldest of settlement sequences, with little understanding of the relations between key site types. There is a need to get at least basic sequences from many more areas, either from sustained regional programmes or targeted sampling exercises. o Much of the methodologically innovative work and new insights have come from long-running research excavations. Such large-scale research projects are an important element in developing new approaches to the Iron Age.  Daily life and practice: There remains great potential to improve the understanding of people’s lives in the Iron Age through fresh approaches to, and integration of, existing and newly-excavated data. o House use. Rigorous analysis and innovative approaches, including experimental archaeology, should be employed to get the most out of the understanding of daily life through the strengths of the Scottish record, such as deposits within buildings, organic preservation and waterlogging. o Material culture. Artefact studies have the potential to be far more integral to understandings of Iron Age societies, both from the rich assemblages of the Atlantic area and less-rich lowland finds. Key areas of concern are basic studies of material groups (including the function of everyday items such as stone and bone tools, and the nature of craft processes – iron, copper alloy, bone/antler and shale offer particularly good evidence). Other key topics are: the role of ‘art’ and other forms of decoration and comparative approaches to assemblages to obtain synthetic views of the uses of material culture. o Field to feast. Subsistence practices are a core area of research essential to understanding past society, but different strands of evidence need to be more fully integrated, with a ‘field to feast’ approach, from production to consumption. The working of agricultural systems is poorly understood, from agricultural processes to cooking practices and cuisine: integrated work between different specialisms would assist greatly. There is a need for conceptual as well as practical perspectives – e.g. how were wild resources conceived? o Ritual practice. There has been valuable work in identifying depositional practices, such as deposition of animals or querns, which are thought to relate to house-based ritual practices, but there is great potential for further pattern-spotting, synthesis and interpretation. Iron Age Scotland: ScARF Panel Report v  Landscapes and regions:  Concepts of ‘region’ or ‘province’, and how they changed over time, need to be critically explored, because they are contentious, poorly defined and highly variable. What did Iron Age people see as their geographical horizons, and how did this change?  Attempts to understand the Iron Age landscape require improved, integrated survey methodologies, as existing approaches are inevitably partial.  Aspects of the landscape’s physical form and cover should be investigated more fully, in terms of vegetation (known only in outline over most of the country) and sea level change in key areas such as the firths of Moray and Forth.  Landscapes beyond settlement merit further work, e.g. the use of the landscape for deposition of objects or people, and what this tells us of contemporary perceptions and beliefs.  Concepts of inherited landscapes (how Iron Age communities saw and used this longlived land) and socal resilience to issues such as climate change should be explored more fully.  Reconstructing Iron Age societies. The changing structure of society over space and time in this period remains poorly understood. Researchers should interrogate the data for better and more explicitly-expressed understandings of social structures and relations between people.  The wider context: Researchers need to engage with the big questions of change on a European level (and beyond). Relationships with neighbouring areas (e.g. England, Ireland) and analogies from other areas (e.g. Scandinavia and the Low Countries) can help inform Scottish studies. Key big topics are: o The nature and effect of the introduction of iron. o The social processes lying behind evidence for movement and contact. o Parallels and differences in social processes and developments. o The changing nature of houses and households over this period, including the role of ‘substantial houses’, from crannogs to brochs, the development and role of complex architecture, and the shift away from roundhouses. o The chronology, nature and meaning of hillforts and other enclosed settlements. o Relationships with the Roman world
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Agile systems development methodologies' 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