The Agile Manifesto (AM) provides principles guiding agile software development as an alternative to traditional software development processes. While attempts have been madeto adapt processes to the ...agile context, representation of AM principles remains underdeveloped and subjective. The Semat (Software Engineering Method and Theory) Essence kernel offers a common ground for representing software development endeavors. In this paper, we represent some AM principles using the language provided by the Semat Essence kernel to establish a common ground. Additionally, we define constraints in OCL (Object Constraint Language) to enhance the Semat Essence kernel, enabling the introduction of time management in our representation. Such a representation will allow us for adapting and assessing different processes in an agile context.
This article reviews scientific studies of factors influencing colocated development teams' performance and proposes five factors that strongly affect performance. In the process, it compares these ...propositions with the Agile Manifesto's development principles. The Web extra at https://extras.computer.org/extra/mso2016040106s1.pdf details the sources and research methods the authors employed.
Resumo A transformação ágil, como é denominada nas empresas que adotaram em algum nível organizacional a nova prática de trabalho, está sendo aplicada pelas empresas que pretendem rever os próprios ...valores presentes na cultura organizacional, e como uma nova forma de construir e manter seus produtos. Este artigo teve como objetivo identificar as práticas e os valores da cultura organizacional e a gestão da mudança podem auxiliar na transformação cultural com adoção dos métodos ágeis. Foi aplicado questionário on-line (322 respondentes) e realizadas 7 entrevistas com profissionais que estão passando pela mudança organizacional com a adoção dos métodos ágeis. Os dados foram analisados mediante análise estatística e de conteúdo. Observaram-se um maior igualitarismo nos diversos níveis, autonomia para os profissionais, preocupação com o trabalho coletivo, entre outros. constatou-se as principais motivações em busca de melhorias nos processos, acelerar a entrega de software, melhorar o alinhamento de TI e os negócios, aumentar a produtividade. Já as melhorias na adoção dos métodos ágeis englobaram inovação, satisfação do usuário, qualidade, valor do negócio, processos e produtividade. A adoção de métodos ágeis afeta a cultura organizacional com os princípios e valores ágeis, gerando impactos positivos para as pessoas e a capacidade de inovação nas empresas.
Abstract Agile transformation, as it’s called in companies that have adopted the new work practice at some organizational level, is being applied by companies that intend to review their own values present in the organizational culture, and as a new way to build and maintain their products. This article aimed to identify the practices and values of organizational culture and change management can assist in cultural transformation with the adoption of agile methods. An online questionnaire was applied (322 respondents) and 7 interviews were conducted with professionals who are undergoing organizational change with the adoption of agile methods. The data were analyzed using statistical and content analysis. Greater egalitarianism was observed at different levels, autonomy for professionals, concern with collective work, among others. it was found the main motivations in search of process improvements, accelerate software delivery, improve IT and business alignment, increase productivity. Improvements in the adoption of agile methods included innovation, user satisfaction, quality, business value, processes and productivity. The adoption of agile methods affects the organizational culture with agile principles and values, generating positive impacts for people and the capacity for innovation in companies.
Purpose
The application of agility principles and methodologies on Enterprise Architecture (EA) is a promising field. This paper aims to provide an in-depth study of the Agile Enterprise Architecture ...(AEA) by studying EA practitioners’ perspectives to propose a foundational framework for AEA.
Design/methodology/approach
The authors formulate a foundational framework that defines the AEA motivators, enablers and blockers using the agile manifesto as one of the AEA enablers where a total of 156 EA stakeholders with at least one year of experience in enterprise architecture were surveyed, and a set of hypotheses was analyzed and tested based on the proposed framework. The authors also develop a quantitative method to evaluate the agility index of the EA based on the introduced framework.
Findings
The research results show with significance that enterprise architects perceive positively the application of the agility methodologies on the enterprise architecture. This perception is primarily affected by the enterprise size, the EA dependency and the agile methodologies awareness. The findings also indicate that AEA is primarily motivated by the Business and IT Change Ready and Responsive EA. Finally, an EA Agility Index (EAAI) was designed to assess the agility application of the EA based on the three forces, i.e. motivators, enablers and blockers.
Research limitations/implications
Because of the chosen research approach and the sample size, the research results may lack generalizability. Also, EAAI designed was not thoroughly tested.
Practical implications
The paper includes implications for the design and development of an EA Agility Index, and the need to increase the awareness of the agility methodologies to overcome the blocker of the unfamiliarity with the agile methodologies implying that the current business models in enterprise must be more aligned with the agile methodologies.
Originality/value
While there are efforts to develop AEA frameworks, one of the major findings of the literature review conducted is that there is evident research gap in the literature on the perception and associated factors of the EA stakeholders on having an agile enterprise architecture. This paper attempts to fill this gap.
Scrum: A Systematic Literature Review Sassa, Adrielle Cristina; Isabela Alves de Almeida; Tábata Nakagomi Fernandes Pereira ...
International journal of advanced computer science & applications,
2023, Letnik:
14, Številka:
4
Journal Article
Odprti dostop
This study presents a Systematic Literature Review on an agile project management tool. The study offers a brief comparison between traditional and agile project management methodologies. Their ...respective concepts and characteristics are laid out to highlight and explain their main differences. The agile methods include quantitative and qualitative data, showing Scrum framework characteristics. This study highlights the importance of project management in function of its emergence as a response to problems encountered during improperly conducted projects. Furthermore, this study provides relevant information for professionals in the Industrial Engineering area and computer science. The results allowed us to conclude that Scrum is an agile framework for empirical-based project development; it was developed in the 1990s by Jeff Sutherland. It is a flexible and adaptable methodology. Scrum research peaked in 2020, and continues to be studied, mainly in the field of computer science. Finally, Brazil is well-positioned in third place for works published.
Software Development is a complex process, in which every software product is a knowledge representation of all the involved people. In agile software development, knowledge is prone to vaporise, ...because documentation is not a priority as indicated in the agile manifesto. This condition generates problems such as poor understanding of the requirements, knowledge transfer deficiency among developers, time wasted by developers while searching for knowledge. The objective of this work is to reduce architectural knowledge vaporisation by means of knowledge condensation to support expertise location (high-level knowledge at a given time). This through an ontology that will condensate the knowledge in the code phase. This study presents the description of an ontology development process following the Methontology Framework. Results show that the proposed ontology does not present incongruence or inconsistency and answers the competency questions correctly. The main contribution of this study is the ontology which brings several benefits such as a shared concept of the knowledge in the code phase and a way to link the artefacts (resources used by developers in the project) and the experts (artefacts provider).
► A grounded theory of how people manage the process of software development. ► Perspectives mismatches between individuals and groups impede the process. ► Reconciling Perspectives is a four-stage ...process for removing impediments. ► Early stages depends on the ability of individuals to engage and interact with others. ► Later stages require moderation of interaction to focus on getting the job done.
Social factors are significant cost drivers for the process of software development. In this field study we generate a grounded theory of how people manage the process of software development. The main concern of engineers involved in the process of software development is getting the job done. To get the job done, people engage in a four-stage process of Reconciling Perspectives. Reconciling Perspectives represents an attempt to converge individuals’ points of view or perspectives about a software project. The process emphasizes the importance of individuals’ abilities to both reach out and engage in negotiations and create shelter from environmental noise to bring a software project to fruition.