We are proudly a Ukrainian website. Our country was attacked by Russian Armed Forces on Feb. 24, 2022.
You can support the Ukrainian Army by following the link: https://u24.gov.ua/.
Even the smallest donation is hugely appreciated!
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Agile 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 methodologies":
1
Sharma, Poorti. "Impact of Agile Methodologies in Project Success." International Journal for Research in Applied Science and Engineering Technology 10, no. 5 (May 31, 2022): 3728–30. http://dx.doi.org/10.22214/ijraset.2022.43204.
Abstract: The Agile Manisfesto of software development put forth a groundbreaking mindset on delivering value and collaborating with customers when it was created in 2001. Agile methodology that utilizes iterative development and prototyping are vitally used in variety of industry projects as a light weight development method which can satisfy to changes of requirements. Traditional waterfall approach is not much efficient to manage the rapid change in requirements. The purpose of this study is to present the impacts of agile methodology in project success. Most studies have reported that when comparing structured methodologies with agile methodologies, agile does improve software quality, other studies have contradicted and questioned the claimed benefits , while others argued that there is not enough empirical evidence. This study aims at investigating the impact that agile method on project success in an organization. The selected studies were published between 2018 to 2022. Index Terms: Agile methodology, agile practices, impact of agile, project success
2
Moses, Joseph. "Agile Writing." International Journal of Sociotechnology and Knowledge Development 7, no. 2 (April 2015): 1–13. http://dx.doi.org/10.4018/ijskd.2015040101.
Scrum methodologies that support cross-functional writing teams to develop polished increments of writing instead of lengthy drafts of documents stand to improve productivity and learning within organizations. Scrum methodologies may be deployed in higher education as well as in nonacademic settings to achieve purposeful knowledge transfer across disciplines and across academic/industry borders. Key to scrum is an emphasis on productivity within fixed time frames, with productivity facilitated by learning that emerges in cross-functional teams. Higher education is similarly a domain in which productivity in fixed time frames takes the measure of student learning. Across the disciplines, scrum methodologies show promise for improving the quality of collaborative problem-solving in writing projects in college and at work.
3
Alsaqqa, Samar, Samer Sawalha, and Heba Abdel-Nabi. "Agile Software Development: Methodologies and Trends." International Journal of Interactive Mobile Technologies (iJIM) 14, no. 11 (July 10, 2020): 246. http://dx.doi.org/10.3991/ijim.v14i11.13269.
<p>Software engineering is a discipline that undergone many improvements that aims to keep up with the new advancements in technologies and the modern business requirements through developing effective approaches to reach the final software product, agile software development is one of these successful approaches. Agile software development is a lightweight approach that was proposed to overcome the convolutional development methods’ limitations and to reduce the overhead and the cost while providing flexibility to adopt the changes in requirements at any stage, this is done by managing the tasks and their coordination through a certain set of values and principles.</p><p>In this work, a comprehensive review that outlines the main agile values and principles, and states the key differences that distinguish agile methods over the traditional ones are presented. Then a discussion of the most popular agile methodologies; their life cycles, their roles, and their advantages and disadvantages are outlined. The recent state of art trends that adopts agile development especially in cloud computing, big data, and coordination are also explored. And finally, this work highlights how to choose the best suitable agile methodology that must be selected according to the task at hand, how sensitive the product is and the organization structure.</p>
4
Ogala, Justin Onyarin, and Ese Sophia Mughele. "Agile Software Development Methodologies in Cloud Computing." Advances in Multidisciplinary and scientific Research Journal Publication 1 (July 30, 2022): 67–80. http://dx.doi.org/10.22624/aims/rebk2022-p7.
Department of Computer Science Faculty of Computing, University of Delta, Agbor, Nigeria E-mails: justin.ogala@unidel.edu.com; s.mughele@unidel.edu.ng ABSTRACT In the software sector, agile development approaches have a lot of promise. Agile development methodologies are highly realistic in their awareness of the fact that business requirements change all the time. By executing software releases iteratively and collecting user feedback more often, agile development approaches maximize the benefits of cloud computing. This study is a cloud computing and Agile Methods analysis. This article examines Agile management and development approaches, as well as their benefits when used in conjunction with cloud computing. By executing software releases iteratively and obtaining user feedback very often, agile development practices maximize the benefits of cloud computing. The basic proposition of this study is that Small and medium enterprises should use a framework that guides their migration to cloud computing to reduce all the issues that come with cloud computing infrastructures Keywords: Agile Methodologies, Cloud Computing, Software Development, Integration
5
Eldanasory, Naglaa, Engy Yehia, and Amira M. Idrees. "A Literature Review on Agile Methodologies Quality, eXtreme Programming and SCRUM." Future Computing and Informatics Journal 7, no. 2 (December 31, 2022): 24–32. http://dx.doi.org/10.54623/fue.fcij.7.2.3.
Agile methodologies have become one of the most applied methods in the software development industry. However, agile methodologies face some challenges such as less documentation and wasting time considering changes. This review presents how the previous studies attempted to cover issues of agile methodologies and the modifications in the performance of agile methodologies. The paper also highlights unresolved issues to get the attention of developers, researchers, and software practitioners
6
Truong, Dothang, and Thawatchai Jitbaipoon. "How Can Agile Methodologies Be Used to Enhance the Success of Information Technology Projects?" International Journal of Information Technology Project Management 7, no. 2 (April 2016): 1–16. http://dx.doi.org/10.4018/ijitpm.2016040101.
Dynamic and unpredictable business environments in the information technology (IT) sector have led to a rapid growth of agile methodologies. Organizations claim that using agile methodologies can enhance the success of IT projects in such environments. However, fluctuating patterns of successful and failed agile IT projects recently raise a question about a path to successful IT projects using agile methodologies. The purpose of this research is to examine agile driven factors and relationships between them and IT project success. Data collected from a pilot survey of agile practitioners were used to confirm important agile driven factors: Agile Team Capability, IT Development Agility, and Agile Culture. The research also tested a structural model that examined indirect impacts of IT development agility and agile culture on project success via a mediation of agile team capability. Theoretical and practical implications are also discussed.
7
Munteanu, V. P., and P. Dragos. "The Case for Agile Methodologies against Traditional Ones in Financial Software Projects." European Journal of Business and Management Research 6, no. 1 (February 16, 2021): 134–41. http://dx.doi.org/10.24018/ejbmr.2021.6.1.741.
Agile methodologies have emerged to challenge traditional ones and overcome their limitations. Increasingly, software development organizations are scaling agile practices in order to meet the requirements of the quickly changing and regularly developing business environment. The main objectives of this study are to investigate the main differences between the traditional project management methodologies and agile methodologies, as well as to identify some key advantages and challenges of applying agile development in a financial software environment. The findings clearly show that using Agile methodologies in a financial software development environment increases the efficiency and transparency of the development process, as well as the stakeholders’ satisfaction, but the project managers must know how to adapt different Agile frameworks to the given context of their organization.
8
Kamthan, Pankaj. "On the Nature of Collaborations in Agile Software Engineering Course Projects." International Journal of Quality Assurance in Engineering and Technology Education 5, no. 2 (April 2016): 42–59. http://dx.doi.org/10.4018/ijqaete.2016040104.
If there is a constant in software development, then it is that its ecosystem is a variable. The agile methodologies are part of a relatively recent shift from predictive to adaptive approach towards software development. This change has had a notable impact on software engineering education (SEE). In this article, a glimpse into the state-of-the-art of incorporating agile methodologies in software engineering courses is presented. In doing so, the reasons for including a project component in software engineering courses, and for committing to agile methodologies in software engineering projects in those courses, are given. The significance of collaboration in the execution of agile methodologies, in general, is underscored, and the pivotal role of collaboration in agile course projects, in particular, is emphasized. To lend an understanding to the notion of collaboration in agile methodologies, a conceptual model for collaboration is proposed and elaborated. The types of collaborations that can occur in agile course projects are classified and discussed. The use technological means for facilitating collaboration, including the Social Web and especially the Wiki, is highlighted.
9
Rocha, Fábio Gomes, Sanjay Misra, and Michel S. Soares. "Guidelines for Future Agile Methodologies and Architecture Reconciliation for Software-Intensive Systems." Electronics 12, no. 7 (March 28, 2023): 1582. http://dx.doi.org/10.3390/electronics12071582.
Background: Several methodologies have been proposed since the first days of software development, from what is now named traditional/heavy methodologies, and later their counterpart, the agile methodologies. The whole idea behind agile methodologies is to produce software at a faster pace than what was considered with plan-based methodologies, which had a greater focus on documenting all tasks and activities before starting the proper software development. Problem: One issue here is that strict agilists are often against fully documenting the software architecture in the first phases of a software process development. However, architectural documentation cannot be neglected, given the well-known importance of software architecture to the success of a software project. Proposed Solution: In this article, we describe the past and current situation of agile methodologies and their relation to architecture description, as well as guidelines for future Agile Methodologies and Architecture Reconciliation. Method: We propose a literature review to understand how agile methodologies and architecture reconciliation can help in providing trends towards the success of a software project and supporting software development at a faster pace. This work was grounded in General Systems Theory as we describe the past, present, and future trends for rapid systems development through the integration of organizations, stakeholders, processes, and systems for software development. Summary of results: As extensively discussed in the literature, we found that there is a false dichotomy between agility and software architecture, and then we describe guidelines for future trends in agile methodologies and reconciliation of architecture to document agile architectures with both architectural decisions and agile processes for any system, as well as future trends to support organizations, stakeholders, processes, and systems.
10
Dingsøyr, Torgeir, Sridhar Nerur, VenuGopal Balijepally, and Nils Brede Moe. "A decade of agile methodologies: Towards explaining agile software development." Journal of Systems and Software 85, no. 6 (June 2012): 1213–21. http://dx.doi.org/10.1016/j.jss.2012.02.033.
Dissertations / Theses on the topic "Agile methodologies":
1
IBBA, SIMONA. "Agile methodologies and blockchain development." Doctoral thesis, Università degli Studi di Cagliari, 2019. http://hdl.handle.net/11584/260671.
The blockchain is one of the most interesting technologies developed in recent years. Blockchain is a ledger, a register, a decentralized and public shared database, reachable by accessing a peer-to-peer network. Each unit of the register represents a block. The blocks are linked together in the same order in which they were created and are connected using cryptographic algorithms that make them and the information stored therein not modifiable.
Software development needs to be supported by architectural models or blockchain oriented meta-models. The introduction of smart contracts, small computer programs stored inside the Ethereum blockchain, modifies the typical software engineering methodologies. The distributed applications developed on blockchain technologies, can in fact follow rules different from used for the development of the normal centralized applications. The blockchain is instead based on a totally different assumption: the information stored on the blockchain and therefore the smart contracts can not be modified or deleted without compromising the integrity of the blockchain itself. Moreover the smart contracts run in an isolated environment and their results must be the same whatever node they run in. They cannot access the external world that changes with time, but can access and send messages to the blockchain itself that is immutable.
Such an innovative context entails new challenges in software engineering. Greater emphasis on specific security and testing practices, new development tools, specific modeling languages and new metrics to evaluate software quality are needed. These new metrics are required to measure complexity, communication, decentralized systems, but also resource consumption (e.g. the so-called gas in the ethereum system).
In this scenario Agile methodologies, that are suited to system whose requirements are not completely understood, or tend to change, could be a good strategy of software development for blockchain applications. Some of the characteristics of the Agile methodologies are in fact present in decentralized applications (DApps).
One of the most interesting applications based on blockchain are the Initial Coin Offerings (ICOs). An ICO is an innovative way to raise funds and launch a startup. It is also an opportunity to take part in a project, or in a DAO (Decentralized Autonomous Organization).
This fund-raising tool contains however some critical issues, such as the use of tokens that have no intrinsic value and do not generate direct liquidity, and the role of investors in the startup’s management. The Lean software development, an approach that maximizes the value given to the customer, and aims to eliminate waste and optimize across organizations, could be helpful to face these critical aspects.
The ICOs and, more generally the decentralized applications are based on smart contracts. Considering the technological break through introduced by blockchain it is important to know characteristics and measures and quality parameters of the development process and its phases, as well as metrics to help ensure that the development process is under control to meet the product’s quality goals. This thesis analyzes the software development process of blockchain-based applications. In particular this work analyzes the following aspects.
• Investigating software engineering activities related to ICOs, recognize the ICOs developed using Agile methods and make a comparison between the characteristics of ICOs and those of Agile ICOs.
• Evaluating the lean startup approach as a methodology for the implementation of an ICO.
• Analizyng smart contracts deployed on the Ethereum blockchain relatively to smart contracts features, their interaction with the blockchain, the role of the development community, and the source code characteristics.
2
Spasibenko, Nikolay, and Besiana Alite. "Project Suitability for Agile methodologies." Thesis, Umeå universitet, Handelshögskolan vid Umeå universitet, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-18428.
Software projects are known for their failure rate, where many are being delivered late, over budget or being canceled while in development. The reason to it is changing requirements and intangibility of the software. Being so abstract it is difficult to imaging all the aspects of the software at the requirements stage. Also technology is playing a major role since processing power, storage space, and data transfer speeds are improving from year to year. Agile methodologies are addressing projects with unclear requirements making process of implementing new specifications along the project much easier and less costly. However the success rate of the software projects did not improve much since the introduction of Agile methodologies. This thesis is looking at what type of projects fit different methodologies and what are factors which practitioners should take into account when selecting methodology for a particular project, The thesis opens up with introduction which sets the research question and provides a brief background to the research topic. In subsequent chapter literature review is conducted to find out what does literature and other researchers have said on the same topic. Third chapter discusses underlying research philosophy and discusses the data collection tools. Next chapter discusses the findings of the research. Interviews has been conducted with project management professionals from Sweden, US, UK and Canada. It was identified through the analysis of patters that Agile methodologies are not well suited for projects involving databases, embedded development and computationally complex projects. Through the analysis of the questionnaire several project characteristics were identified which suit Agile methodologies better than traditional ones: unclear requirements, high risk of failure etc… In the last chapter the thesis concludes the findings and its theoretical and practical implications.
3
Burman, Emil. "Agile in action : Hybrid methodologies in practice." Thesis, Umeå universitet, Institutionen för informatik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-107894.
In recent years an increase of agile methodologies and their implementation in mainstream software engineering projects have been seen, but this implementation has reportedly changed agility in practice into a hybrid form of agility and more classic methodologies. With a lack of research regarding these hybrid methodologies this multiple case study empirically analyses the practice of methodologies from two different conglomerates and places the results in the Information Technology Management framework (ITMF) to answer the research question; How are hybrid agile methodologies enacted in practice in mature agile teams and why are they enacted in such a way? The result show that the organizations work agile within a waterfall framework, a hybrid form of requirement handling into agile development followed by waterfall testing. The hybrid methodologies are imposed by external factors such as the sales department and traditional economic reporting. This study acknowledges a need for a greater understanding of the engagement between external actors and software development.
4
MANNARO, KATIUSCIA. "Adopting agile methodologies in distributed software development." Doctoral thesis, Università degli Studi di Cagliari, 2008. http://hdl.handle.net/11584/265978.
From the second half of the '90s, some software engineering practitioners introduced a new group of software development methodologies called Agile Methodologies (Ams): they have been developed to overcome the limits of the traditional approaches in the software development. FLOSS (Free Libre Open Source Software) has been proposed as possible different solution to the software crisis that is afflicting the ICT worldwide business. If the AMs improve the quality code and allow to respond quickly to requirement changes, FLOSS approach decreases the development costs and increases the spreading of competences about the software products. A debate is shaping about the compatibility of these two approaches.
Software development teams have been spreading around the world, with users in Europe, management in the USA and programmers in the USA and India. The scattering of team members and functions around the world introduces barriers to productivity, cultural and languages differences can lead to misunderstanding of requirements, time zone differences can delay project schedules.
Agile methods can provide a competitive advantage by delivering early, simplifying communication and allowing the business to respond more quickly to the market by changing the software. Trying to distribute a development project in an agile way isn't easy and will involve compromises. The goal of this thesis is to determine the application of the AMs in several contexts so to define which of these can be used effectively in non traditional software projects as the distributed development.
5
Kaikkonen, H. (Harri). "Supporting rapid product development with agile development methodologies." Doctoral thesis, Oulun yliopisto, 2018. http://urn.fi/urn:isbn:9789526219332.
Abstract Management of product development activities has become increasingly important, as cycle times of product development have shortened. Smaller product development projects are often conducted rapidly at companies based on customer or sales requests to answer the need for faster cycle times. However, this is often done without fully realizing the impact of the new projects on the larger project portfolio or organizational effectiveness. The main objective of this dissertation is to increase knowledge on the use of agile development methods in small, rapid product development projects, and on the implementation of a rapid product development model. The dissertation is formulated as a qualitative, inductive study based on the research results of four original publications and a summary combining the results. The results of the dissertation show that it is beneficial to separate a rapid product development process for certain types of customer- or sales-initiated projects. A new rapid development model with principles and guidelines is introduced to help organizations facilitate this separation. The implementation of the model can be supported with agile development practices, of which self-managing teams are studied in more detail. There is significant overlap between case companies’ perceived success factors for rapid development and self-management. The results imply that a functional rapid development model can be utilized as a strategic asset at companies. The results also provide empirical evidence that agile development practices can be utilized in product development. In addition to providing empirical evidence in scientific discussion about combining product development and agile software development practices, the results can be used to create better definitions of product development processes in general Tiivistelmä Tuotekehityksen johtamisesta ja hallinnasta on tullut entistä haastavampaa ja tärkeämpää, kun tuotekehitysprojektien läpimenoajat ovat lyhentyneet. Yritykset tekevät kasvamassa määrin lyhyitä tuotekehitysprojekteja asiakaspyyntöjen tai myynnin aloitteesta vastatakseen markkinoiden vaatimuksiin nopeasta kehityksestä. Tällaisten nopeiden tuotekehitysprojektien käynnistäminen ja toteutus tehdään usein ymmärtämättä yksittäisen projektin vaikutusta koko projektiportfolioon tai organisaation tehokkuuteen. Tämän väitöskirjan päätavoitteena on tutkia ohjelmistokehityksestä tunnettujen ketterien kehitysmenetelmien käyttöä nopeissa tuotekehitysprojekteissa ja uudenlaisen nopean tuotekehityksen mallin käyttöönotossa. Tutkimus on tehty laadullisena ja induktiivisena tutkimuksena perustuen neljään itsenäiseen tutkimusartikkeliin ja näiden tulokset kokoavaan kokoelmaosaan. Tutkimus osoittaa, että yrityksille on hyödyllistä erottaa erillinen prosessi tietyntyyppisille nopeille tuotekehitysprojekteille. Tutkimuksen tuloksena esitellään malli, joka tukee tätä erottamista periaatteiden ja ohjeiden avulla. Tätä mallia pystytään tukemaan ketterillä kehitysmenetelmillä, joihin liittyen on erityisesti tutkittu itseohjautuvia kehitystiimejä. Case-yritysten havainnoimilla nopean tuotekehityksen menestystekijöillä ja itseohjautuvien tiimien ominaisuuksilla on havaittavissa suurta päällekkäisyyttä. Tulokset osoittavat, että hyvin käytetty ja määritetty nopean tuotekehityksen malli voi olla strateginen kilpailuetu yrityksille. Tulokset lisäävät myös empiiristä tietoa ketterien menetelmien käytöstä tuotekehityksessä ja hyödyntävät siten ajankohtaista tieteellistä keskustelua. Tuloksia voidaan myös hyödyntää muiden tuotekehitysprosessien käyttötarkoituksen tarkempaan määrittämiseen
6
Alnatheer, Ahmed. "The investigation of security issues in agile methodologies." Thesis, University of Southampton, 2014. https://eprints.soton.ac.uk/374168/.
This thesis is about an empirical study on the effects of using predominant security mechanisms for integration into Agile methodologies. Claims uncovered throughout our review of literature and research are presented along with our findings, analysis, and interpretation of the qualitative and quantitative phases which underscore the gap in the literature in the past few years. In this thesis the researcher uses the issues raised in the literature and incorporates empirical findings from practitioners working in the field to form a cohesive and complete investigation into the predominant security practices that are suitable to be included into Agile. Current security issues related to and applicable to popular Agile methodologies such as Scrum and eXtreme Programming (XP) are examined along with their effects on the process and the final product are researched, quantified, analyzed, interpreted, and summarized. This is done to gain a more practical and in-depth understanding of the security issues and effectiveness of methods proposed for use in the Agile software development field today. The research considered their potential for inclusion (and possible integration) into Agile methods from multiple perspectives utilizing a mixed method approach of in-depth empirical interviews, empirical surveys, and an academic experiment to test those findings. In this manuscript we present the research along with the findings obtained with our conclusions and the future direction of the research. The contribution of this work is to identify and empirically classify outstanding issues that were agreed upon by practitioners and experts in the field. The most popular of these turned out to be the addition of the security engineer or experienced developers to the Agile team to bolster the resulting software’s security assurance argument. Others aimed at modifying aspects of Agile that were deemed necessary for security include documentation, risk analysis, or the need for better tools. Building software with security in mind and the use of software security controls were also important findings from our qualitative phase of the study. This along with our own findings formed the basis of the comprehensive survey of practitioners to gauge the suitability and feasibility of those issues and solutions for possible inclusion into Agile. The significant findings from our survey suggested that the most suitable mechanisms are the addition of a dedicated Security Engineer and the use of more experienced developers to the Agile team, and the use of software security controls. Based on these results we put together an experimental trial to test the effect of more experienced developers on the Agile team on the process, the final product (which is the software produced), and the people involved (which are stakeholders in Agile projects). The statistically significant result of the experiment was in the affirmation of the hypothesis which stated that the inclusion of more experienced developer(s) to the Agile team increased the team’s overall awareness of security compared to the less experienced team(s).
7
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.
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.
8
MENDOZA, DANIELA MILAGROS QUENAYA. "MANAGING SOFTWARE PROJECTS USING AGILE METHODOLOGIES: A CASE STUDY." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2011. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=17680@1.
COORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIOR PROGRAMA DE SUPORTE À PÓS-GRADUAÇÃO DE INSTS. DE ENSINO Hoje em dia, entregar software com qualidade, nos prazos previstos e
respeitando os custos é um grande diferencial para empresas dedicadas a esta
atividade. A constante procura de produtividade e qualidade em projetos de
software originou diversos modelos de gerenciamento que procuram auxiliar esta
área com metodologias e formas de organização de trabalho. O modelo mais
conhecido na área de gerenciamento de software é o Modelo em Cascata,
caracterizado pela rigidez e fases bem definidas nos processos. Uma vez
encontrados problemas com os modelos rígidos surgiram como alternativa de
gerenciamento os métodos ágeis, caracterizados pela agilidade, iteratividade e
adaptabilidade para diversos projetos. Diante isto o presente trabalho analisa o
problema do gerenciamento de projetos de desenvolvimento de software, e propõe
um modelo de referencia de gerenciamento de projetos de software considerando
a abordagem tradicional de gerenciamento de projetos assim como a abordagem
ágil. A pesquisa analisa a compatibilidade das metodologias ágeis com o
Capability Maturity Model Integration (CMMI) que é um modelo de maturidade
nos processos de desenvolvimento de software. Finalmente a pesquisa apresenta
um estudo de caso, que permitiu observar as forças e fraquezas dos métodos
estudados, concluindo que as praticas ágeis contribuem na melhoria e
gerenciamento de projetos de software. Today, delivering quality software, on time and respecting costs is a key
differentiator for companies dedicated to this activity. The constant search for
productivity and quality in software project management led to several models that
seek to help this area with methods and forms of work organization. The best
known model in the area of software management is the Waterfall Model,
characterized by stiffness and well-defined phases in the process. Once found
problems with rigid models have emerged as alternative management of agile
methods, characterized by agility, and adaptability to various iterative projects.
Given that this paper analyzes the problem of managing software development
projects, and proposes a reference model for managing software projects
considering the traditional approach of project management as well as the agile
approach. The research examines the compatibility of agile methodologies with
the Capability Maturity Model Integration (CMMI) is a maturity model in
software development processes. Finally the research presents a case study, which
allowed us to observe the strengths and weaknesses of the methods studied,
concluding that such practices contribute to improved and agile project
management software.
9
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.
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.
10
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.
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.
Asim Abdel Rahman El Sheikh. Business intelligence and agile methodologies for knowledge-based organizations: Cross-disciplinary applications. Hershey, PA: Business Science Reference, 2012.
Bibik, Ilya. "Overview of Agile Methodologies." In How to Kill the Scrum Monster, 7–13. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-3691-8_2.
Nogués, Albert, and Juan Valladares. "Agile Methodologies for BI Projects." In Business Intelligence Tools for Small Companies, 29–56. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-2568-4_2.
Laplante, Phillip A., and Mohamad H. Kassab. "Requirements Specification and Agile Methodologies." In Requirements Engineering for Software and Systems, 195–218. 4th ed. New York: Auerbach Publications, 2022. http://dx.doi.org/10.1201/9781003129509-8.
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.
Mnkandla, Ernest, and Barry Dwolatzky. "A Selection Framework for Agile Methodologies." In Extreme Programming and Agile Processes in Software Engineering, 319–20. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24853-8_50.
Bojorque, Rodolfo, and Fernando Pesántez. "Curriculum Design Based on Agile Methodologies." In Advances in Intelligent Systems and Computing, 84–94. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-93882-0_9.
Salza, Pasquale, Paolo Musmarra, and Filomena Ferrucci. "Agile Methodologies in Education: A Review." In Agile and Lean Concepts for Teaching and Learning, 25–45. Singapore: Springer Singapore, 2018. http://dx.doi.org/10.1007/978-981-13-2751-3_2.
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.
Conference papers on the topic "Agile methodologies":
1
Mnkandla, E., and B. Dwolatzky. "Agile Methodologies Selection Toolbox." In International Conference on Software Engineering Advances (ICSEA 2007). IEEE, 2007. http://dx.doi.org/10.1109/icsea.2007.14.
Grewal, Harprit, and Frank Maurer. "Scaling Agile Methodologies for Developing a Production Accounting System for the Oil & Gas Industry." In AGILE 2007 (AGILE 2007). IEEE, 2007. http://dx.doi.org/10.1109/agile.2007.50.
Peres, Angela Lima, Tiago Da Silva, Fernando Selleri Silva, Felipe Furtado Soares, Carlos Rosemberg, and Silvio Romero. "AGILEUX Model: Towards a Reference Model on Integrating UX in Developing Software Using Agile Methodologies." In 2014 Agile Conference (AGILE). IEEE, 2014. http://dx.doi.org/10.1109/agile.2014.15.
Lenarduzzi, Valentina, Maria Ilaria Lunesu, Michele Marchesi, and Roberto Tonelli. "Blockchain applications for agile methodologies." In XP '18 Companion: 19th International Conference on Agile Software Development. New York, NY, USA: ACM, 2018. http://dx.doi.org/10.1145/3234152.3234155.
., Shubh, and Priyanka Gandhi. "SWOT Analysis of Agile Methodologies." In Proceedings of the International Conference on Advances in Computer Science and Electronics Engineering. Singapore: Research Publishing Services, 2012. http://dx.doi.org/10.3850/978-981-07-1403-1_484.
Moreira, Marcio Aurelio Ribeiro, and Allan Kardec Silva Soares. "RISK MANAGEMENT IN AGILE METHODOLOGIES." In 11th CONTECSI International Conference on Information Systems and Technology Management. TECSI, 2014. http://dx.doi.org/10.5748/9788599693100-11contecsi/rf-577.
Hamzane, Ibrahim, Allae Erraissi, Banane Mouad, and Abdessamad Belangour. "Proposed metamodels transformation from Predictive methodologies to Agile methodologies." In 2020 International Conference on Decision Aid Sciences and Application (DASA). IEEE, 2020. http://dx.doi.org/10.1109/dasa51403.2020.9317183.
Line, Steve, and Eric Birkhauser. "Applying Agile Design Methodologies for Design Competitons." In Footbridge 2022 (Madrid): Creating Experience. Madrid, Spain: Asociación Española de Ingeniería Estructural, 2022. http://dx.doi.org/10.24904/footbridge2022.232.
Developing a highly creative and complex design response in a short time frame requires inspired work from many contributors from concept to submission. Agile design methodologies are uniquely suited for design completions, employing a very collaborative, iterative design process where the design is continuously developed to foster design innovation through collaborating with the team’s diverse group of technical experts with the common purpose of finding the best design solutions. Agile design processes have been highly developed for software design and many agile methodologies are applicable for the built environment. The values and principles of agile design are being increasingly appropriated to developing building architecture and can be adopted by bridge designers alike.<p>This session explores how design thinking complimented with agile design processes was conducted for the INWMG Footbridge Competition</p>
9
Tenemaza, Maritzol, and Carlos Sarzosa. "Agile Methodologies in the Fashion Industry." In Intelligent Human Systems Integration (IHSI 2022) Integrating People and Intelligent Systems. AHFE International, 2022. http://dx.doi.org/10.54941/ahfe1001050.
In the document, we expose the application of the agile SCRUM and Kanban methodologies in an Ecuadorian textile company to improve the control of production processes. We have considered a company that produces clothing for all its subsidiaries in Ecuador. The participating groups were previously trained, both on methodologies, as well as on the tool developed and made available to control the production process. The methodological process was adapted to the jargon recognized by the participants. Data analytics were integrated to generate order management indicators, such as production and sales through key performance indicators (KPI). This experiment is attractive for textile companies, as well as for other lines because the methodologies allow organizing management, identifying bottlenecks for timely decision-making.
10
Fox, David, Jonathan Sillito, and Frank Maurer. "Agile Methods and User-Centered Design: How These Two Methodologies are Being Successfully Integrated in Industry." In Agile 2008 Conference. IEEE, 2008. http://dx.doi.org/10.1109/agile.2008.78.
Wayant, Nicole. Adapting agile philosophies and tools for a research environment. Engineer Research and Development Center (U.S.), September 2022. http://dx.doi.org/10.21079/11681/45442.
There exist myriad project management methodologies, but none is focused solely on scientific research. Research projects are unique compared to other types of projects, including software development, manufacturing, and drug trials; research projects inherently have unplanned risks. These risks provide a challenge to managing resources, developing schedules, and providing team ownership while still achieving project goals. To help mitigate the risks and the challenges associated with scientific research, a methodology to manage research projects needs to be developed.
