To see the other types of publications on this topic, follow the link: Agile methodologies.
Dissertations / Theses on the topic 'Agile methodologies'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research 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.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
IBBA, SIMONA. "Agile methodologies and blockchain development." Doctoral thesis, Università degli Studi di Cagliari, 2019. http://hdl.handle.net/11584/260671.
Full textAbstract:
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.
Full textAbstract:
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.
Full textAbstract:
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.
Full textAbstract:
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.
Full textAbstract:
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<br>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/.
Full textAbstract:
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.
Full textAbstract:
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.<br>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.
Full textAbstract:
COORDENAÇÃO DE APERFEIÇOAMENTO DO PESSOAL DE ENSINO SUPERIOR<br>PROGRAMA DE SUPORTE À PÓS-GRADUAÇÃO DE INSTS. DE ENSINO<br>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.<br>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.
Full textAbstract:
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.
Full text
11
Soliński, Adam. "Analysis of the application and integration of methodologies by software development companies." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2924.
Full textAbstract:
Context. In recent years there has been observed a significant shift from plan-driven development towards agile, which is considered as a vast improvement to processes. However, it has also been spotted that agile methodologies are hardly ever applied in their pure form. Moreover, hybrid processes as combinations of plan-driven and agile practices emerge. In addition, agile adoption has been reported to result in both: benefits and limitations. Objectives. In this study the following matters are investigated: 1) the commonness of plan driven and agile practices usage, 2) common practices combinations, 3) patterns for agile adoption over time, 4) hybrid development models and 5) the actual effects of agile adoption in terms of benefits and limitations as perceived by practitioners. Methods. The thesis presents an empirical investigation of software development organizations. The objectives are achieved through a targeted survey based on existing evidence and a multidimensional data analysis. The mean for obtaining data is a web-based questionnaire with an interactive board with practices and time indication sliders (to capture applied development models and practices adoption strategies) and hierarchical cumulative voting (to measure the relative significance of benefits and limitations). The data analysis is supported by hierarchical cluster analysis and an extended hierarchical voting analysis framework (EHV-F). Results. In total, 45 practitioners have been successfully surveyed. The commonness of 7 plan-driven and 14 agile practices usage was investigated. The relative significance of agile adoption benefits (32 factors in 10 categories) and limitations (23 factors in 7 categories) was measured with respect to global view (all respondents and perspectives), different agile adoption strategies as well as distinguished development models. Conclusions. It is concluded that agile practices dominate over plan-driven, however, hybrid approaches, being combinations of plan-driven and agile practices, are frequently applied. It is also concluded that some practices are commonly used together since they facilitate each other (e.g. continuous integration with testing which facilitate short iterations and releases). Some agile practices are still unsuccessfully applied and eventually abandoned (e.g. pair programming), what should be further investigated by researchers. Incremental agile adoption strategy was found to be the most beneficial approach. It is also concluded that agile adoption leads first of all to improved quality of working life, increased knowledge transfer and improved verification and validation processes. On the other hand, agile adoption is very demanding since it requires high professional skills from development teams as well as managers. Hence, more resources should be devoted to training on agile for all the parties involved in development. Agile is still commonly considered to be poorly scalable. Moreover, the quality of design with agile methods is not considered as a benefit at all. These areas should be further investigated by researchers.
12
Bennett, Andrew L. "An Empirical Longitudinal Analysis of Agile Methodologies and Firm Financial Performance." Thesis, The George Washington University, 2018. http://pqdtopen.proquest.com/#viewpdf?dispub=10982630.
Full textAbstract:
<p> Agile Software Development methods such as Scrum, SAFe, Kanban, and Large Scale Agile (LeSS) promise substantial benefits in terms of productivity, customer satisfaction, employee satisfaction, quality project management overhead, and time to market. As Agile methods have become widespread in the software development industry and begin to take root in the overall business community, there is an increasing need to understand the firm level impact of the implementation of these methods. To build the most effective business case for organizations in and out of the software development industry, it is imperative that a case be made to show that the implementation of Agile frameworks has constituted a competitive advantage. This study investigated the organization level performance impact of switching from traditional methods to the use of Agile frameworks. The results showed that changing from a traditional methodology to an Agile framework resulted in higher return on assets and lower operating expense ratios. The interaction between time and methodology for OER, ROA, or revenues in Table 6 did not show a significant difference, indicating that the null hypothesis cannot be rejected. Thus, we cannot say whether performance differs as a function of type of agile methodology. That said, the non-parametric sign test shows that the median improvement in Operating Expense Ratios were highest for Scrum while SAFe seemed to show a slightly higher improvement in Return on Assets. On the whole, Scrum seems to outperform SAFe in terms of operating efficiency (as measured by OER) but lags in terms of ROA.</p><p>
13
Moratilla, Temprado Enrique, and Bendito Enrique Ruz. "Lean Software Development and Agile Methodologies for a small Software development organization." Thesis, Högskolan i Borås, Institutionen Ingenjörshögskolan, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-20077.
Full textAbstract:
Lean Software Development is a new approach to provide a quality philosophy in software development companies. Lean offers a set of principles that helps companies to identify inefficient processes and waste. Therefore, by applying these principles, we can reduce costs, by shorting development time, incrementing productivity.In this study a software company with seven employees is analyzed. The company develops software and wants to increase its maturity and the quality of its processes. Currently, it has few documented processes. Furthermore, the company want a common way of working for every project. The challenge relies in adapting the set of principles provided by Lean to this particular case of study.We seek to analyze the current situation of the company to find out about the problems and limitations of the current way of working. After that we will state recommendations about the use of Lean combined with Agile practices such as Scrum and XP.As a result we present a proposal for implementation adapted from these philosophies to the needs and characteristics of the company.We have found that there are several ways in which the company can benefit from the implementation of Lean practices in combination with Scrum and XP. The result is a new framework that can be applied for other small software development companies in a similar situation.
14
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 textAbstract:
Includes bibliographical references (leaves 81-90).<br>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.
15
Espinoza, Cuadros Anelit Nelva, and Marcavillaca Miriam Rosalinda Criollo. "Modelo de Producción para la Reducción de Tiempos de Entrega de Pedido en una empresa metalmecánica de Lima Metropolitana basado en Six Sigma." Bachelor's thesis, Universidad Peruana de Ciencias Aplicadas (UPC), 2020. http://hdl.handle.net/10757/652075.
Full textAbstract:
El principal problema que enfrenta un fabricante de tableros eléctricos es la alta tasa de demora en entrega de pedidos. El factor predominante que han dado lugar al retraso de la entrega de pedidos es el cuello de botella que se genera en el proceso productivo. Para resolver este problema, se desarrolló una propuesta innovadora utilizando la metodología DMAIC (Definir, Medir, Analizar, Mejorar y Controlar), la cual esta orientada a la mejora de procesos utilizada por Six Sigma [1] [2]. Para respaldar este análisis, se realizará una simulación, buscando una reducción considerable del cuello de botella y, por consecuencia, el aumento de productividad, mejorando el tiempo de entrega de pedidos. Al implementar la metodología DMAIC Six Sigma, se mejorará el tiempo de entrega de pedidos a 96%, mejorando así la calidad del proceso de producción y generando beneficios económicos.<br>The main problem faced by a manufacturer of electrical panels is the high rate of late delivery of orders. The predominant factor that has led to the delay in order delivery is the bottleneck generated in the production process. To solve this problem, an innovative proposal was developed using the DMAIC (Define, Measure, Analyze, Improve and Control) methodology, which is oriented to the process improvement used by Six Sigma [1] [2]. To support this analysis, a simulation will be carried out, looking for a considerable reduction of the bottleneck and, consequently, the increase of productivity, improving the time of delivery of orders. By implementing the DMAIC Six Sigma methodology, the order delivery time will be improved to 96%, thus improving the quality of the production process and generating economic benefits.<br>Trabajo de investigación
16
Amaral, Rodrigo André Cardoso. "A adoção de metodologias ágeis em projetos de uma empresa de eletricidade : estudo de caso." Master's thesis, Instituto Superior de Economia e Gestão, 2020. http://hdl.handle.net/10400.5/20985.
Full textAbstract:
Mestrado em Gestão de Sistemas de Informação<br>O mundo em que vivemos está em constante mudança. Devido a isso, os projetos são cada vez mais complexos e imprevisíveis, sendo difícil planear a longo prazo.
As Metodologias Ágeis têm vindo, cada vez mais, a despertar um maior interesse e um grande número de empresas tem vindo a adotar esta framework para atuar em projetos.
Num ambiente em que tudo muda rapidamente, os requisitos de um projeto também podem mudar. Por isso, no início de um projeto, é complicado fornecer todos os requisitos desejados, até porque estes podem mudar durante o decorrer do mesmo.
Devido a estes fatores, muitas empresas estão a gerir os seus projetos através de Metodologias Ágeis, uma vez que estas metodologias vão mais ao encontro das necessidades de um projeto complexo, num ambiente de incerteza.
Tendo em consideração a crescente importância da Metodologia Ágil, a presente dissertação desenvolve um estudo sobre a adoção da framework Agile e metodologia SCRUM, numa empresa do ramo da eletricidade. Para tal, foi estudado um projeto da empresa em questão, tendo sido efetuadas entrevistas de modo a obter dados relevantes para o estudo.
Concluiu-se que a adoção feita pela empresa não segue o padrão do SCRUM, tendo sido feitas algumas adaptações que levam em consideração a grande dimensão da empresa. Apesar dessas adaptações visarem o bom funcionamento dos projetos, foram identificados alguns pontos de melhoria, tendo o investigador sugerido neste documento medidas para melhorar a utilização da metodologia e consequentemente o sucesso dos projetos.<br>The world we live in is constantly changing. As a result, projects are increasingly more complex and unpredictable, and it's difficult to plan for the long term.
The interest in Agile Methodologies have been arising and many companies have adopted this framework to act throughout projects.
In an environment where everything changes quickly, the requirements of a project can also change. Therefore, at the beginning of a project, it's difficult to provide all the desired requirements, especially because these may change as the project progresses.
Given these factors, many companies are managing their projects using Agile Methodologies, as these methodologies more closely meet the needs of a complex project in an uncertain environment.
Considering the growing importance of Agile Methodologies, this dissertation develops a study on the adoption of Agile framework and SCRUM methodology, in a company of the electricity industry. For this purpose, a study was developed in a project of the company in question, and interviews were conducted in order to gather relevant data for said study.
It was concluded that the adoption made by the company does not follow all the standards of SCRUM, given there have been made some adaptations that take into account the dimension of the company. Although these adaptations were aimed at the good functioning of the projects, some improvement points were identified, and the researcher suggested measures to improve the methodology and consequently the success of the projects.<br>info:eu-repo/semantics/publishedVersion
17
Igou, Amy. "Evolving Software Development Methodologies: The Search for Accounting Clarity." OpenSIUC, 2014. https://opensiuc.lib.siu.edu/dissertations/953.
Full textAbstract:
For many years, most IT departments used the same software development methodology called waterfall. This methodology outlines distinct phases for project completion; each phase needing to be completed prior to the start of the next. The primary accounting standard for allocating costs for software development is written in the language of waterfall. Costs are either capitalized or expensed depending on the type of activity that was performed. IT departments have been moving toward a new group of software development methodologies called agile. These methodologies do not follow the phases of waterfall. This makes the current accounting standard for software development difficult to interpret and determine the appropriate transaction. This further hinders IT organizations attempts to better quantify business value of software projects. To examine this issue, a new construct called accounting clarity is introduced in this research. Accounting clarity is an agreement between IT and accounting regarding the treatment of software development costs. This study shows that it is essential for both IT and accounting to work together to determine a solution. The accounting clarity construct is developed from the “ilities” of software quality models and the Capability Maturity Model (CMM) Level 3 key process area (KPA) of intergroup coordination. Intergroup coordination provides the concepts for accounting clarity as the two groups must coordinate to determine the appropriate accounting treatment. The “ilities” are characteristics that should be followed and measured throughout a software development project to ensure long term maintainability of software. This study proposes that accounting clarity should be one of the "ilities" in the software quality model. A portion of the study of accounting clarity examines the relationship between accounting clarity and project control, proposing a positive relationship between the two variables. Then the study examines factors that help to increase accounting clarity. These factors were derived from teamwork and coordination literature. To test the hypothesized relationships, a survey methodology was used. Individuals working on agile software development projects were participants in the survey. This study contributes to both the IT and accounting literature. The research provides a framework to examine other contexts in which the current accounting standards are unclear. As changes happen more frequently in business, this is more likely to occur on a frequent basis. The study has practical implication for software development as it highlights the importance of understanding the accounting implications prior to the project and continuously throughout the lifespan of the software. Adding accounting clarity to the “ilities” of software quality helps software development teams include this in project plans with any software development methodology.
18
Soares, Lourenço Piuma. "Cultura organizacional e adoção de práticas ágeis : uma análise exploratória." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2011. http://hdl.handle.net/10183/31950.
Full textAbstract:
A adoção de metodologias ágeis tem se provado uma atividade sensível a cultura das organizações que as aplicam. Nos dez anos que se sucederam ao Agile Manifesto, projetos ágeis se desenvolveram a partir de tentativas conduzidas em situações ideais até grandes iniciativas adaptadas para as mais diversas condições. Por outro lado, a cultura organizacional tem se provado determinante na maneira que organizações abordam os desafios que se apresentam. Este trabalho tem por objetivo explorar a relação entre os pressupostos culturais básicos das organizações e práticas ágeis selecionadas. Para isso, se buscou identificar, através de revisão da literatura, pressupostos básicos significativos, práticas ágeis representativas e como se dá a interação entre esses, mapeando correlações através de uma survey. Essa se trata de um questionário respondido por funcionários da consultoria de TI ThoughtWorks a partir de sua experiência em projetos ágeis em clientes. A partir do resultado da survey foram exploradas as correlações identificadas – inclusive no que diz respeito à experiência e satisfação dos clientes com metodologias ágeis – e as observações foram validadas com consultores especialistas em métodos ágeis e em cultura organizacional. Procurou-se, assim, oferecer um mapa inicial para investigar a relação entre cultura organizacional e práticas ágeis que pode sugerir abordagens para introdução de práticas ágeis baseadas no perfil cultural da organização aonde se busca introduzi-las.<br>Companies adopting Agile methodologies have proven sensible to cultural differences. Ten years after the Agile Manifesto, agile projects have grown from small teams operating in specific situations to big cross-national initiatives. Organizational culture, in the other hand, is considered a determining factor in the way an organization perceives the world and interacts with it. In this paper, the relation between basic cultural assumptions of an organization will be matched up against a few selected agile practices. To achieve that, it looked into the literature to map these basic assumptions and representative agile practices, aiming to establish correlations between them through the results of a survey. This survey is a questionnaire answered by employees of the IT consultancy firm ThoughtWorks based on their experience in agile projects in client‟s organizations. Based on the survey results, some correlations were identified and analysed – including some regarding client experience and satisfaction with agile – and the observations were submitted to consultants, specialist in both agile practices and organizational culture for confirmation of the findings. It aimed to offer an initial map to investigate relations between organizational culture and agile practices looking to suggest new approaches for the introduction of agile practices based on the cultural profile of the target organization.
19
Ghahestani, Shervin, and Pauline Korssell. "Agil transformation för produktutveckling i mjukvarubranschen : Ett arbete om upplevda utmaningar och fördelar med agilt arbetssätt." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-290047.
Full textAbstract:
Allt fler aktörer uppkommer på den redan konkurrenskraftiga marknaden vilket ställer höga krav på utveckling av nya innovativa produkter för företag inom mjukvarubranschen. Detta leder till att företag måste förändra sin struktur och sitt arbetssätt för att kunna anpassa sin produktutveckling efter kunderna och marknaden. Ett sätt för företag att kunna fortsätta vara konkurrenskraftiga och bemöta marknadens behov är att implementera agila arbetssätt. Syftet med detta arbete är att bidra till ökad kunskap kring hur produktutvecklingsprocessen för en agil transformation från beslut till implementation kan ske i mjukvarubranschen. Arbetet har undersökt tre frågeställningar relaterade till agil transformation i mjukvarubranschen. Inledningsvis genomfördes en litteraturstudie för att erhålla en ökad förståelse för produktutveckling i mjukvarubranschen och för det agila arbetssättet. Vidare utfördes en kvalitativ semistrukturerad intervjuundersökning med fyra respondenter från tre företag där samtliga arbetar med agila arbetssätt och produktutveckling inom mjukvarubranschen. Den kvalitativa studien undersökte vilka utmaningar och potentiella fördelar en agil transformation kan generera samt vad som kännetecknar en lyckad agil transformation. Utifrån resultatet av denna studie utformades ett antal kategorier som kan användas som riktlinjer för hur en organisation kan gå tillväga vid en agil transformation i mjukvarubranschen. Studien visar att en agil transformation är en komplex och tidskrävande process. Utmaningar med agil transformation innefattar att ett agilt arbetssätt ofta blir beroende av en nyckelperson, det kräver en hög samverkan och ökad förståelse för varandras arbetsuppgifter samt ett anpassningsbart tankesätt som är mottagligt för förändring. Däremot genererar den agila transformationen fördelar så som en ökad produktivitet och användarnöjdhet, minskat antal defekter och en kortare ledtid hos samtliga företag. För att lyckas med en agil transformation visar studien på att ett företags medarbetare bör vara mottagliga för förändring och att motivet till transformationen borde komma inifrån organisationen. Sammanfattningsvis resulterade den agila transformationen i en förbättrad mjukvaruutveckling.<br>A large number of businesses are emerging on the already competitive market which places high demands on the development of new innovative products for companies in the software industry. As a result, companies must change the structure of the organization and their methods. Due to this, they have to customize their product development in order to meet the requirements of the customers and the markets demand and maintain their competitiveness. One way for companies to stay competitive is by implementing agile working methodologies. This study aims to contribute with knowledge and investigate the processes of an agile transformation from decision-making to implementation in the software industry. The study has examined three problem statements related to the agile transformation in the software industry. Initially a literature review was performed to gain an insight into product development in the software industry and the agile working methodologies. Furthermore, a semi structured qualitative interview was conducted which involved four respondents from three companies that work with agile working methodologies and product development in the software industry. This qualitative study examined the challenges and possible opportunities that an agile transformation generates as well as the characteristics of a successful transformation. Based on the result of this study, several categories were chosen and treated as guidelines for how an organization in the software industry can approach the agile transformation and proceed with it successfully. The results of the study demonstrate that an agile transformation is a complex and time-consuming process. The many challenges involving the agile transformation includes that the agile working methodology often becomes dependent of a single key person, it also requires collaboration, an increased understanding of each other’s work as well as an adaptable mindset that is receptive towards change. However, the agile transformation enables advantages amongst all the companies such as an increased productivity and user satisfaction, decreased number of defects as well as a reduced leadtime. To succeed with an agile transformation, it is of importance that a company’s employees are receptive towards change and that the motive behind the transformation comes internally within the organization. In conclusion, the agile transformation improved and strengthened the companies’ software development.
20
Azizi, Nima, and Mohammed Aysar Taqi. "Applying Agile methodologies within the context of traditional project governance : - A study of the Volvo Group experience." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsmiljö Informationsteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-27632.
Full textAbstract:
The nature of software development has changed in last decade. Waterfall or traditional command and control methods have been replaced by Agile methodologies. Agile came as a “solution” to the disadvantages of the waterfall methodology, but using Agile has its own challenges. Due to the attractive characteristics of Agile such as flexibility and short time-to-market, Agile development has been increasingly popular and the number of organisations which have started to move to Agile is growing every day. Implementing new methodologies in any organisation is always a big challenge, especially for large-scale organisations due to their complexity, many different interacting interfaces, strong organisational culture, etc. The nature of these challenges and obstacles changes from different perspectives within an organisation, and each of these perspectives needs to be studied and investigated to ensure a successful transition from traditional approaches to Agile. In this thesis we focus on the project manager and project governance perspectives. We aim to define the success and failure factors that play a key role in moving from traditional approaches to Agile approaches in large-scale organisations. To address these challenges we conducted literature reviews on the latest research in implementing Agile methodologies. To collect our data we used a combination of qualitative and quantitative research methods. We explored both IT project manager and Chief project manager opinions and experiences of the organisations by conducting interviews and questionnaires in our research. The results reveals the difficulty to find proper product owners in the Agile projects. It is challenging to set a product owner who has Agile knowledge and is expert in the project domain. Specialized training and coaching for product owners is mentioned as one of the solutions that could be provided for this challenge. “Distributed teams”, “Lack of focus on the business side” and “Weak coaching and support” are some of the other critical areas which have been presented by the participants in the interviews and survey in this study. The main conclusion is that in order to have a successful transition to Agile approaches, the Agile mind-set should be set in all different part in an organizations, not only the development side and also that everyone have to understand “Why” Agile is beneficial. Also the communication of lessons learnt and feedback should be strong and effective in order to avoid repetition of the same mistakes. In addition, specialized training and coaching for different roles within the period of the development is necessary to ensure the successful adoption of Agile.<br>Synen på mjukvaruutveckling har förändrats under det senaste decenniet; Vattenfalls- eller traditionella kommando- och styrmetoder har ersatts av Agila metoder. Agila utvecklingsmetoder kom som en "lösning" till nackdelarna med vattenfalls metodiken, men användning av Agila metoder har sina egna utmaningar. På grund av Agila metoders attraktiva egenskaper såsom flexibilitet och kort tid till marknaden, har denna typ av utveckling blivit alltmer populärt och antalet organisationer som har börjat flytta till Agila metoder växer varje dag. Att genomföra nya metoder i en organisation är alltid en stor utmaning. Särskilt för stora organisationer på grund av deras komplexitet, med tanke på många olika samverkande gränssnitt, stark organisationskultur, etc. Karaktären på dessa utmaningar och hinder ändras från olika perspektiv inom en organisation, och vart och ett av dessa perspektiv behöver studeras och undersökas för att säkerställa en framgångsrik övergång från traditionella metoder till Agila metoder. I denna avhandling fokuserar vi på projektledare och projektförvaltningsperspektiv. Vi strävar efter att definiera framgångs- och misslyckande faktorer som spelar en nyckelroll i att flytta från traditionella metoder till Agila metoder i storskaliga organisationer. För att möta dessa utmaningar genomfört vi dessutom en litteraturstudie av den senaste forskningen om införande av Agila metoder. För att samla våra data vi använt en kombination av kvalitativa och kvantitativa forskningsmetoder. Vi utforskade både projektledare för IT och chefs-projektledare sidor av organisationer genom intervjuer och enkäter i vår forskning. Resultaten visar den kritiska roll produktägare utgör i Agila projekt. Det är en utmaning att tillsätta en korrekt produktägaren som har Agile kunskap och är expert i projektet domänen. Specialiserad utbildning och coaching för produktägare nämns som en av de möjliga lösningar som finns för denna utmaning. "distribuerade team", "brist på fokus på affärssidan" och "Svag coachning och support" är några av de andra viktiga områden som har lagts fram av deltagarna i intervjuerna och undersökning i denna studie. Den viktigaste slutsatsen är att för att få en lyckad övergång till Agila metoder bör Agilt tänkande tillämpas i alla delar i en organisations, inte bara utvecklingssidan, utan alla måste förstå "varför" Agila metoder är fördelaktigt. Även överföring av lärdomar och återkoppling bör vara stark och effektiv för att undvika återkommande samma misstag. Dessutom, specialiserad utbildning och coaching för olika roller och inom den tidsfrist för utvecklingen är nödvändig för att säkerställa ett framgångsrikt antagande av Agila arbetsmetoder.
21
Flores, Julian, and Adam Trevarthan. "Agile Methodology Implementation in a Remote Digital Environment : A Case Study of a Large Scale Insurance Company." Thesis, Linköpings universitet, Företagsekonomi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-176700.
Full textAbstract:
Through this case study, we sought to analyze a U.S. based insurance company’s implementation of agile methodologies in a remote digital environment in comparison to using agile in a typical physical environment work setting. We wanted to gain an in-depth perception through questioning if this company changed how they use agile methodologies during the COVID-19 pandemic, what the benefits and drawbacks of using agile methodologies are in a remote digital environment, if individual project roles were impacted with remote use of agile methodologies, and what is the reasoning of the company regarding the use of agile methodologies remotely after the pandemic? A semi-structured interview was done with six respondents that work with agile methodologies in an IT Division at a large scale U.S. insurance company to gain insight into our questions through a qualitative study. According to the respondents, they were satisfied with how the company implemented agile methodologies remotely, but some felt it was a wake-up call that agile methodologies were not the best methodology that their project team could employ. These results can be used for future organizations not just to see how they can better implement agile methodologies in a remote setting and how they can better use agile methodologies to foster better communication, Knowledge Transfer, and Competence Development with their employees.
22
Burzala, Matúš. "Nasazení metodiky SCRUM při vývoji software." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2021. http://www.nusl.cz/ntk/nusl-444610.
Full textAbstract:
Diplomová práca sa zaoberá porovnaním metodiky použitej na projekte vývoja software a metodiky SCRUM. V rámci práce sú zmapované všetky role, udalosti a artefakty projektu u ktorých sú následne identifikované ich odlišnosti od definície metodiky SCRUM. Práca ďalej obsahuje návrh toho, čo je potrebné upraviť, alebo zmeniť, aby sa dosiahla správna aplikácia metodiky SCRUM a tým pádom aj optimalizácia vývojového procesu.
23
Thummadi, B. Veeresh. "SOFTWARE DESIGN METHODOLOGIES, ROUTINES AND ITERATIONS: A MULTIPLE-CASE STUDY OF AGILE AND WATERFALL PROCESSES." Case Western Reserve University School of Graduate Studies / OhioLINK, 2014. http://rave.ohiolink.edu/etdc/view?acc_num=case1396363465.
Full text
24
Mé, Hugo Miguel Machado. "A influência da cultura organizacional na gestão de projetos Ágeis : caso de estudo." Master's thesis, Instituto Superior de Economia e Gestão, 2019. http://hdl.handle.net/10400.5/19319.
Full textAbstract:
Mestrado em Gestão de Projetos<br>As metodologias ágeis têm vindo a despertar cada vez mais o interesse, por parte das empresas que atualmente atuam em mercados cada vez mais competitivos, exigentes, imprevisíveis e que estão em constante mutação.
Para competir e sobreviver às condições de contingência num determinado contexto empresarial e num determinado ambiente operacional, uma organização deverá ser rápida, eficiente e altamente flexível à mudança.
As práticas e os métodos ágeis são o caminho utilizado por muitas organizações para introduzirem modificações complexas, evolutivas e duradouras para ganhar agilidade organizacional e, assim, obter uma ferramenta poderosa para ultrapassar concorrentes, num mercado dinâmico e imprevisível. Requer escalabilidade, adaptação, localização e adoção numa organização.
A literatura tem demonstrado que a transformação da cultura organizacional é necessária para o processo de transformação ágil.
Através de um caso de estudo procurou-se identificar as barreias e os desafios que uma organização possui para transformar a sua cultura organizacional numa cultura ágil. Este estudo mostra que esta mudança cultural acontece através das pessoas, com o apoio da administração e com a transmissão dos valores e princípios ágeis. Os resultados obtidos demonstram que o mindset, a comunicação, a estrutura e a dimensão da empresa são as barreiras e os desafios encontrados nesta transformação.<br>Agile methodologies are increasingly encouraging interest from companies that are currently operating in more competitive, demanding, unpredictable and ever-changing markets.
To compete and survive contingency conditions in a given business context and operating environment, an organization must be fast, efficient, and highly flexible to change.
Agile practices and methods are the path many organizations use to make complex, evolutionary, and lasting modifications to gain organizational agility and thus gain a powerful tool for overcoming competitors in a dynamic and unpredictable marketplace. It requires scalability, adaptation, localization and adoption in an organization.
The literature has shown that the alteration of organizational culture is necessary for the agile transformation process.
Through a case study we sought to identify the barriers and challenges that an organization must transform its organizational culture into an agile culture. This study shows that this cultural change happens through people, with the support of management and the transmission of agile values and principles. The results show that the mindset, communication, structure and size of the company are the barriers and challenges encountered in this transformation.<br>info:eu-repo/semantics/publishedVersion
25
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 textAbstract:
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.<br>Thesis (M.Sc. (Computer Science))--North-West University, Potchefstroom Campus, 2010.
26
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 textAbstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, 2014.<br>DVD-ROM contains supplemental models: four .mdl files and two .vdf files.<br>Cataloged from PDF version of thesis.<br>Includes bibliographical references (pages 63-64).<br>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:<br>by Erik Roberto Garcia.<br>S.M. in Engineering and Management
27
NYMAN, NICK. "Threat Awareness in Agile Environments : Creating a Developer-Driven Threat Modeling Process for Agile Software Development Teams." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-276440.
Full textAbstract:
Agile principles for software development are now the industry standard for innovative projects. Agile is often hailed for being flexible, but there is also a commonly held 'truth' that agile principles and software security do not work well together. For this reason it is not uncommon to place all security responsibilities with a separate team, which goes against the agile principles of being team-centered and may affect flexibility or timeframe of a project. Additionally, software security is difficult and requires extensive experience and knowledge, something that varies a lot among software developers. This study presents a threat modeling process tailored for the specific needs and capabilities of the agile developer team. The process combines features of attack trees and abuser stories with other supplementary techniques in a pedagogical instruction manual to create an accessible and easy-to-get-started method intended to be driven by the developers themselves. The process has been developed through extensive review of extant threat modeling methods and the circumstances of the agile team, and trialed through user tests at an agile ITorganization in the financial services.<br>Agila principer för mjukvaruutveckling är nu industristandard för innovativa projekt. Agila metoder hyllas ofta för sin flexibilitet men det finns också en vidspridd uppfattning att agila metoder och mjukvarusäkerhet inte går bra ihop. Av den anledningen är det inte ovanligt att säkerhetsansvar och -uppgifter drivs av en separat säkerhetsgrupp, vilket går emot de agila principerna om fokus på utvecklarteamet. Detta kan få effekter både för projektets flexibilitet och dess tidsram. Dessutom är IT-säkerhet ett svårt ämne som kräver både erfarenhet och avsevärd kunskap, något som funnits variera mycket bland mjukvaruutvecklare. Den här studien presenterar en hotmodelleringsprocess som skräddarsytts för utvecklarteamets specifika behov och styrkor. Processen kombinerar funktioner från attackträd och abuser stories med andra, komplementära tekniker i en pedagogisk instruktionsmanual för att leverera en lättillgänglig och snabbstartad metod menad att drivas av utvecklarna själva. Processen har utvecklats genom omfattande studier av etablerade hotmodelleringsprocesser, samt den agila teammiljön, och testats och vidareutvecklats genom användartester hos en agil IT-organisation inom finansbranschen.
28
Kurtagic, Anessa. "Working With Agile Methodologies During The Covid-19 Pandemic : A qualitative study of an agile teams' transition to remote work from home as a result of the Covid-19 pandemic." Thesis, Linnéuniversitetet, Institutionen för informatik (IK), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-106923.
Full textAbstract:
Remote work was already an ongoing trend amongst software developers, but the sudden and unexpected occurrence of the COVID-19 pandemic made it normal due to the obligations for many people to stay and work from home. To go from the safeness of the work office with an always-working Internet connection and colleagues around to exchange ideas with, to working from home can be a big change from one day to another. Without a good structure or adjustment from the organization, this would lead to a decrease in good work results, communication issues and difficulty for managers to keep track of what is done and by whom. To facilitate this, commonly used methods are the Agile Methodologies. Beck et al. (2001) make it significant in the 12 principles of Agile that the most efficient and effective method of conveying information is by face-to-face conversation for the best results. Investigating the work that was done face-to-face previous to the pandemic but is now done remotely from home within agile teams is therefore of much relevance today. This thesis was intended to investigate and learn how the use of agile methodologies has facilitated the sudden transition to remote work from home and affected the aspects of communication and work results within an agile development team. The study was conducted using the qualitative method with interviews consisting of seven open-response and two closed-response questions with respondents in agile teams from a software development company in Sweden. The analysis was made thematically in relation to Bridge’s Transition Model, and in relation to previous research. The study identified three themes to answer the research question based on the theoretical framework; The Change, Communication and Work Results. The results of the study show that the use of Agile Methodologies indeed has simplified the sudden transition to remote work from home, which was called The Change, as many of the agile practices already were done online previous to the pandemic. The study has also concluded that the use of Agile Methodologies has positively affected the aspects of communication and work results in an agile team, as it was found that forms of communication became more creative as they occurred more frequently while working from home, and it ultimately led to more valuable end-results.<br>Distansarbete var redan en pågående trend bland mjukvaruutvecklare, men den plötsliga och oväntade förekomsten av COVID-19-pandemin gjorde det normalt på grund av restriktionerna för många människor att arbeta hemifrån. Att gå från arbetskontorets säkerhet med en alltid fungerande internetuppkoppling och kollegor runt om för att diskutera idéer med, till att arbeta hemifrån kan vara en stor förändring från en dag till en annan. Utan en bra struktur eller anpassning från organisationen skulle detta leda till en minskning av goda arbetsresultat, dålig kommunikation och svårigheter för chefer att hålla reda på vad som görs och av vem. Vanliga metoder att använda för att underlätta detta är de agila metoderna. Beck et al. (2001) gör det tydligt i de 12 principerna för Agile att den mest effektiva metoden för att förmedla information i ett projekt är genom konversationer face to face, för bästa resultat. Att undersöka det arbete som innan pandemin gjordes face to face men nu görs på distans hemifrån inom agila team är därför av stor relevans idag. Denna studie var avsedd att undersöka och få kunskap om hur användningen av agila metoder har underlättat den plötsliga övergången till distansarbete hemifrån och påverkat aspekterna av kommunikation och arbetsresultat inom ett agilt utvecklingsteam. Studien genomfördes med hjälp av den kvalitativa metoden med intervjuer bestående av sju öppna frågor och två slutna svarfrågor med respondenter i agila team från ett mjukvaruutvecklingsföretag i Sverige. Analysen gjordes tematiskt i förhållande till Bridge’s Transition Model och i förhållande till tidigare forskning. Studien identifierade tre teman för att besvara forskningsfrågan utifrån det teoretiska ramverket; The Change, Communication och Work Results. Resultaten av studien visar att användningen av agila metoder har förenklat den plötsliga övergången till distansarbete hemifrån, eftersom många av de agila aktiviteterna redan gjordes online före pandemin. Studien har också dragit slutsatsen att användningen av agila metoder har påverkat aspekterna kommunikation och arbetsresultat positivt i ett agilt team, eftersom det visade sig att kommunikationsformer blev mer kreativa eftersom kommunikationen blev mer frekvent inträffande när de arbetade hemifrån, och det ledde slutligen till mer värdefulla slutresultat i projekt.
29
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 textAbstract:
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.<br>Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.
30
Matos, Patrícia Coelho de. "Inovação em contexto de agilidade." Master's thesis, Instituto Superior de Economia e Gestão, 2019. http://hdl.handle.net/10400.5/19239.
Full textAbstract:
Mestrado em Gestão de Projetos<br>O objetivo do presente trabalho é identificar as principais diferenças entre metodologia de gestão de projetos tradicional e Agile aplicada a empresas de desenvolvimento de software e perceber como e porquê a metodologia de trabalho Agile aplicada ao desenvolvimento de software pode criar um ambiente mais propício à inovação. Estamos hoje expostos a uma oferta de produtos e serviços originários de múltiplos países. A globalização é um fenómeno que faz parte do nosso dia-a-dia. Preços mais competitivos e qualidade superior é o que o consumidor do séc. XXI procura. Hoje são poucas as diferenças que encontramos num produto/serviço quando o comparamos com a concorrência. Poucas são as caraterísticas distintivas, embora sejam essas que o consumidor procura. É neste ponto que encontramos a importância do conceito de inovação nas empresas. O consumidor passou a ser o centro de uma organização e, deste modo, a procura da satisfação das suas necessidades e desejos é o objetivo principal. Para atingir o objetivo do presente trabalho foi desenvolvida uma investigação qualitativa com entrevistas semiestruturadas a dois gestores de projetos, ambos com experiência profissional na área de desenvolvimento de software. Como resultado, pode-se identificar como a metodologia Agile, a melhor metodologia indicada para o desenvolvimento de software sendo a mesma metodologia como a mais indicada para a criação de um ambiente de inovação.<br>The aim of this paper is to identify the main differences between traditional and Agile project management methodology applied to software development companies and to understand how and why the Agile work methodology applied to software development can create a more innovation-friendly environment. We are today exposed to an offer of products and services from multiple countries. Globalization is a phenomenon that is part of our daily lives. More competitive prices and superior quality is what the consumer of the century. XXI search. Today there are few differences that we find in a product / service when compared to the competition. There are few distinctive features, although these are what the consumer is looking for. This is where we find the importance of the concept of innovation in companies. The consumer has become the center of an organization and thus the pursuit of the satisfaction of their needs and desires is the main objective. In order to achieve the objective of this work, a qualitative research was conducted with semi-structured interviews with two project managers, both with professional experience in software development. As a result, we can identify as the Agile methodology, the best methodology indicated for software development being the same methodology as the most suitable for creating an innovation environment.<br>info:eu-repo/semantics/publishedVersion
31
Chavez, Leandro Cesar Augusto. "Aplicación de herramientas del TPM para disminuir paradas de planta por mantenimiento en empresa de fabricación de emulsiones acuosas." Bachelor's thesis, Universidad Peruana de Ciencias Aplicadas (UPC), 2020. http://hdl.handle.net/10757/651565.
Full textAbstract:
En el presente trabajo de investigación se hace un estudio de la problemática de una empresa del rubro químico, la cual cuenta con un proceso básico y empírico de mantenimiento, en el que no se aplica planificación . Este proceso es muy importante ya que es un proceso de apoyo al proceso central. Debido a ello se propone la implementación de un sistema de gestión de mantenim iento, utilizando la filosofía del TPM (mantenimiento productivo total).
En el primer capítulo se realiza un marco teórico, en el cual se desarrollan conceptos concisos de sistemas de gestión de mantenimiento, e strategias en la cual se desarrollan los conceptos de los tipos de mantenimientos, ciclos de vida de los equipos y fallas. Asimismo, indica que se hace énfasis en conceptos desarrollos e implementación del TPM, basados en libros, publicac iones de revisitas, papers, etc.
En el segundo capítulo se describe el estado actual de la empresa en la cual se desarrolla la investigación, observando la misión, visión y valores de la misma. Asimismo, de acuerdo a herramientas de ingeniería, cómo histogramas, diagramas causa – efecto, Pareto se pueden encontrar las posi bles causas del problema final.
En el capítulo 3 se desarrolla la metodología de solución al problema encontrado en el capítulo previo, definiendo el panorama de la tesis según la metodología a trabajar, el desarrollo de las actividades, teniendo presente los recursos y definir como optimizar los mismos utilizando aspectos de tecnología e innovación, con el fin de ser más productivos en el proyecto en curso.
Asimismo, se revisarán los resultados de los análisis, actividades, recursos propuestos, para validar el desarrollo de la tesis se deben simular los resultados haciendo las comparaciones del antes y el después de la mejora, utilizando un software simulador; lo cual se deberá reflejar la mejora propuesta en costos, es decir impacto económico.
Por último, se realizarán las recomendaciones y conclusiones del estudio realizado, de acuerdo los objetivos planteados.<br>In this thesis a study is made of the problem of a company in the chemical field, in which they only have an empirical basic maintenance area, in which optimal maintenance controls are not carried out, which is reflected in costs and low productivity. Due to this, the implementation of a maintenance management system is proposed, using the philosophy of TPM (total productive maintenance).
In the first chapter a theoretical framework is made, in which concise concepts of maintenance management systems are developed, strategies in which the concepts of maintenance types, equipment life cycles and failures are developed. It also indicates that emphasis is placed on concepts of development and implementation of the TPM, based on books, magazine publications, papers, etc.
The second chapter describes the current state of the company in which the research is carried out, observing its mission, vision and values. Also, according to engineering tools, how histograms, cause - effect diagrams, Pareto can find the possible causes of the final problem.
In chapter 3 the methodology for solving the problem found in the previous chapter is developed, defining the thesis panorama according to the methodology to be worked, the development of the activities, taking into account the resources and defining how to optimize them using aspects of technology and innovation, in order to be more productive in the ongoing project.
Likewise, the results of the analysis, activities, proposed resources will be reviewed, to validate the development of the thesis, the results must be simulated by making comparisons of the before and after the improvement, using a simulator software; This should reflect the proposed improvement in costs, that is, economic impact.
Finally, the recommendations and conclusions of the study will be carried out, according to the objectives set.<br>Trabajo de Suficiencia Profesional
32
Pinto, Luara Montiel. "Gestão ágil de projetos : uma perspectiva dos intervenientes em projetos quanto à aplicabilidade da abordagem ágil a projetos não relacionados ao desenvolvimento de software." Master's thesis, Instituto Superior de Economia e Gestão, 2018. http://hdl.handle.net/10400.5/16649.
Full textAbstract:
Mestrado em Gestão de Projetos<br>A gestão de projetos está crescendo cada vez mais dentro das organizações e para que as empresas possam obter resultados satisfatórios em seus projetos, se faz necessária uma constante busca pela inovação e atualização. As metodologias ágeis surgiram como uma alternativa aos métodos tradicionais para gestão de projetos de desenvolvimento de produtos de software, com princípios e valores que buscam mais agilidade, maior qualidade no desenvolvimento dos produtos e menos burocracia. O intuito desta pesquisa é traçar linhas gerais sobre o tema com vistas a possibilitar futuras investigações, assim como contribuir com os profissionais da área de gestão de projetos, com o objetivo de analisar a possível aplicabilidade da abordagem ágil a projetos não relacionados ao desenvolvimento de software. A pesquisa realizada neste estudo foi do tipo exploratória, com abordagem metodológica quantitativa e qualitativa, e contou com a participação de intervenientes em projetos, através de suas perceções e experiências com a abordagem ágil. Em seguida, foram realizadas análises acerca dos resultados levantados e finalmente respondidas às questões de investigação. Dos resultados levantados, destaca-se que a abordagem ágil está sendo aplicada a diferentes tipos de projetos, também fora da área da Tecnologia, e as práticas ágeis estão sendo utilizadas e adaptadas conforme a necessidade do cliente e do projeto. Além destas, outras conclusões obtidas neste estudo poderão ser úteis para futuras investigações e criação de hipóteses.<br>Project management is growing more and more within organizations and for companies to achieve satisfactory results in their projects, a constant search for innovation and updating is necessary. Agile methodologies have emerged as an alternative to traditional methods for project management related to software product development, with principles and values that seek more agility, higher product development quality and less bureaucracy. The aim of this research is to outline the subject in order to make possible future researches, as well as to contribute with project managers, with the objective of analyzing the possible applicability of the agile approach to projects not related to software development. The research carried out in this study was exploratory, with a quantitative and qualitative methodological approach, and involved project participants, through their perceptions and experiences with the agile approach. Then, analyzes were carried out on the results obtained and finally answered to the research questions. From the results obtained, it is worth noting that the agile approach is being applied to different types of projects, also outside the area of Technology, and that the agile practices are being used and adapted according to the needs of the client and the project. Besides these, other conclusions obtained in this study may be useful for future investigations and hypothesis creation.<br>info:eu-repo/semantics/publishedVersion
33
Řezníček, Miroslav. "Hodnocení projektu Implementace BI v poradenské společnosti." Master's thesis, Vysoká škola ekonomická v Praze, 2011. http://www.nusl.cz/ntk/nusl-114265.
Full textAbstract:
This diploma thesis deals with the implementation of Business Intelligence in small and medium-sized companies and furthermore focuses on an agile project management and introduces possibilities for this approach. The aim of the project is to present an agile methodology of Business Intelligence implementation and comparison of processes of a real project with the procedures proposed in this methodology and eventually propose improvements. The thesis is divided into three main parts. The first part is an introduction to the theory, in which the concept of Business Intelligence is introduced and important terms as transactional and analytical systems, data warehouse, data mart, etc. are described, being followed by research of previous works focused on Business Intelligence implementation. The introduction to the theory is closed with introducing CRISP-DM methodology for SMEs and agile methodologies as Scrum and Extreme Programming. The objectives of the thesis and some sub-goals are achieved through the analysis of the agile methodology "Agile Data Warehousing for Business Intelligence implementation" in the second part of the thesis. The final main section is a comparison with a real project, in which certain improvements are also proposed for future use. The benefit of this thesis is especially the unusual view at the implementation of Business Intelligence through agile approach and proposed methods for future use in small and medium-sized companies. The benefits are also described particularly for business companies in the area of financial advice.
34
Koutsoumpos, Vasileios, and Iker Marinelarena. "Agile Methodologies and Software Process Improvement Maturity Models, Current State of Practice in Small and Medium Enterprises." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4284.
Full textAbstract:
Abstract—Background: Software Process Improvement (SPI) maturity models have been developed to assist organizations to enhance software quality. Agile methodologies are used to ensure productivity and quality of a software product. Amongst others they are applied in Small and Medium – sized Enterprises (SMEs). However, little is known about the combination of Agile methodologies and SPI maturity models regarding SMEs and the results that could emerge, as all the current SPI models are addressed to larger organizations and all these improvement models are difficult to be used by Small and Medium – sized firms. Combinations of these methodologies could lead to improvement in the quality of the software products, better project management methodologies and organized software development framework. Objectives: The aim of this study is to identify the main Agile methodologies and SPI maturity models applied in SMEs, the combinations of these methodologies, and the results that could emerge. Through these combinations, new software development frameworks are proposed. What is more, the results of this study can be used as a guide with the appropriate combination for each SME, as a better project management methodology or as improvement in the current software engineering practices. Methods: A Systematic Literature Review was conducted, resulting in 71 selected relevant papers ranging from 2001 to 2013. Besides, a survey has been performed from June 2013 to October 2013, including 49 participants. Results: Seven Agile methodologies and six different SPI maturity models were identified and discussed. Furthermore, the combination of eight different Agile methodologies and Software Process Improvement maturity models is presented, and as well as their benefits and drawbacks that could emerge in Small and Medium – sized firms. Conclusion: The majority of the Agile methodologies and SPI maturity models are addressed to large or very large enterprises. Thus, little research has been conducted for SMEs. The combinations of the Agile methodologies and SPI maturity models are usually performed in experimental stages. However, it has been observed that such type of combination could present numerous benefits, which can also be applicable in SMEs as well. The combinations that are most common are the CMMI and XP, CMMI and Scrum, CMMI and Six Sigma, and the PRINCE2 and DSDM.<br>0034-636835645
35
Capovilla, Lodovica <1994>. "The role of experiments in the quest for product/market fit: structuring business uncertainty through Agile methodologies." Master's Degree Thesis, Università Ca' Foscari Venezia, 2019. http://hdl.handle.net/10579/15811.
Full textAbstract:
Technological-based ventures are currently facing times of high uncertainty under conditions of lack of resources and time pressure. This leads them to “leaps of faith” decisions, highly endangering their chances to success and durability. Prior research discusses that, although under these conditions business models must be tested fast and thoroughly, classic planning methods are very likely to be inconsistent. The present paper’s objective is to understand how experimentation-led business model development processes are carried out in the face of uncertainty, with a particular focus on whereas and how the implementation of Agile methodologies within the venture contributes to its effectiveness in achieving product/market fit. Given the challenges in scaling up such methodologies, it attempts to answers questions regarding their evolution too. Through a qualitative grounded-based research conducted on five diverse Italian ventures, this paper contributes in unifying the gap between BMI, Entrepreneurial Approaches and the product/market fit milestone, towards strategic agility. Aside from extending current literature by re-framing unclear concepts such as product/market fit and discovery-driven learning, this paper adds several managerial implications, especially valuable for scaling-up ventures. Indeed, it highlights the benefits and challenges of implementing Agile methodologies to fuel the business validation process through customer feedback, especially in the start-up phase. In particular, it suggests ventures how to evolve their practices when entering the scaling-up phase, and to combine Agile with more human-centered processes to secure customer orientation, organizational flexibility and, ultimately, strategic agility.
36
PORRU, SIMONE. "Achieving Quality through Software Maintenance and Evolution: on the role of Agile Methodologies and Open Source Software." Doctoral thesis, Università degli Studi di Cagliari, 2017. http://hdl.handle.net/11584/249560.
Full textAbstract:
Agile methodologies, open source software development, and emerging new technologies are at the base of disruptive changes in software engineering. Being effort estimation pivotal for effective project management in the agile context, in the first part of the thesis we contribute to improve effort estimation by devising a real-time story point classifier, designed with the collaboration of an industrial partner and by exploiting publicly available data on open source projects. We demonstrate that, after an initial training on at least 300 issue reports, the classifier estimates a new issue in less than 15 seconds with a mean magnitude of relative error between 0.16 and 0.61. In addition, issue type, summary, description, and related components prove to be project-dependent features pivotal for story point estimation. Since story points are the most popular effort estimation metric in the agile context, in the second study presented in the thesis we investigate the role of agile methodologies in software maintenance and evolution, and prove its undoubted influence on the refactoring research field over the last 15 years. In the later part of the thesis, we focus on recent technologies to understand their impact on software engineering. We start by proposing a specialized blockchain-oriented software engineering, on the basis of the peculiar challenges the blockchain sector must confront with and statistical data retrieved from a corpus of open source blockchain-oriented software repositories, identified relying upon the 2016 Moody’s Blockchain Report. We advocate the need for new professional roles, enhanced security and reliability, novel modeling languages, and specialized metrics, along with new research directions focusing on collaboration among large teams, testing, and specialized tools for the creation of smart contracts. Along with the blockchain, in the later part of this work we also study the growing mobile sector. More specifically, we focus on the relationships between software defects and the use of the underlying system API, proving that our findings are aligned with those in the literature, namely, that the applications which are more connected to API classes are also more defect-prone. Finally, in the last work presented in the dissertation, we conducted a statistical analysis of 20 open source object-oriented systems, 10 written in the highly popular language Java and 10 in the rising language Python. We leveraged two statistical distribution functions–the log-normal and the double Pareto distributions–to provide good fits, both in Java and Python, for three metrics, namely, the NOLM, NOM, and NOS metrics. The study, among other findings, revealed that the variability of the number of methods used in Python classes is lower than in Java classes, and that Java classes, on average, feature fewer lines of code than Python classes.
37
Kupka, Jaromír. "Analýza projektu implementace penzijní reformy." Master's thesis, Vysoká škola ekonomická v Praze, 2012. http://www.nusl.cz/ntk/nusl-165254.
Full textAbstract:
This thesis is devoted to the theme of a new information system of the pension company. The first part is the input into the subject. It defines the scope of the thesis and defines the objectives that the author wants to achieve in the thesis. The second part is focused on the analysis of project methodologies and selection of an appropriate methodology for this type of project. The third part of the thesis is focused on the analysis of agile methodologies and selection of the appropriate methodology for a particular project. The fourth part is devoted to the analysis of Scrum methodology. Conclusions of this part are the arguments for deploying agile approach for a specific project. In the fifth part of the thesis the author returns to mistakes at the level of project management, which negatively affected the time plan and financial plan of the project. The final part summarizes the results of analyzes, summarizes the objectives and identifies the expected benefits of the thesis.
38
Tošner, Jiří. "Aplikace agilní metodiky Scrum a využití podpůrných softwarových nástrojů." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2015. http://www.nusl.cz/ntk/nusl-225252.
Full textAbstract:
Agile software development methodologies are very popular for their efficiency and flexibility. This thesis focuses on agile software development methodology called Scrum. Basic description and comparison of traditional and agile methodologies is mentioned at first. Attention is paid to methodology Scrum which is shown on an example of usage by a specific company. It is convenient to use some software tool for organization of Scrum methodology. Therefore, an overview of the most common tools and basic comparison of software tools for organizing this methodology is presented. Conclusion of this thesis is recommendation for improvements for the investigated team, based on issues which were identified.
39
AKHTER, TASMIAH, and TOBIAS ÅKERLIND. "Agile IT Infrastructure Transformation : A Case Study of a Nordic Incumbent Telco." Thesis, KTH, Industriell ekonomi och organisation (Inst.), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-236041.
Full textAbstract:
In a growing digital economy, where demands for network services and competition from various communication-over-the-network service providers intensify, telecommunication companies need to keep up in an ever-changing environment. As there is a need to reduce time-to-market for new network services, agility becomes restrained by having to operate within large legacy IT infrastructure environments. While agile methodologies in modern time have attained recognition in the field of software development for the way they help to manage changing customer demands and deliver early value incontinuous increments, it is yet uncertain how agile methodologies can best be adopted for IT infrastructure deliveries to achieve the same purpose. Hence, this study explores how legacy IT infrastructure can be transformed in an agile way into modernized infrastructure landscapes supporting the business with fast enough development, release and deployment of new network services in demand. More precisely, the study investigates how larger IT infrastructure transformation projects can be executed by the help of agile practices. In order to investigate this, the study carries out a case study at Telia Company, a large Nordic incumbent telecommunications company possessing a big legacy of IT infrastructure. The study conducts internal interviews with Telia employees as well as external interviews with agile experts. Also, benchmarking is conducted with a well-established Swedish bank to better understand the challenges and how agile practices can best be applied.The study concludes that agile practices influenced by agile frameworks Scrum and Kanban can advantageously be applied at team level for more agile execution. However, the surrounding organizational business landscape greatly sets the limits for agile deliveries, due to dependencies on cooperation from the business side in the execution phase and the need to be aligned with business needs and stakeholder requirements. Further, the study also shows that the application of agile practices at team level in combination with a close dialogue with stakeholders and a scaled agile approach requiring investing in automation, is the key for more agile infrastructure deliveries. In this way, aligned end-to-end delivery processescan be better developed and infrastructure needs better understood and implemented at the right time. As a contribution, the study proposes a model with inspiration from agile frameworks Scrum, Kanban and SAFe, for how this may work in practice.<br>I en växande digital ekonomi, kännetecknad av intensifierad efterfrågan på nätverkstjänster och konkurrens från diverse aktörer som erbjuder kommunikationstjänster över nätverket, behöver telekommunikationsföretag hålla uppe takten i den snabbföränderliga omgivningen. Samtidigt som det finns behov av att minska tid till marknad för nätverkstjänster, blir snabbheten återhållsam på grund av att man måste jobba i miljöer med stora IT infrastrukturs-arv. Agila metoder har i modern tid blivit erkända inom mjukvaruutveckling för hur de hjälper att hantera föränderliga kundbehov och kontinuerligt leverera tidigt värde inkrementellt. Dock råder det fortfarande ovisshet kring hur agila metoder kan tillämpas bäst inom IT infrastrukturs-leveranser för att uppnå samma ändamål. Följaktligen utforskar denna studie hur IT infrastrukturs-arv agilt kan bli transformerade till moderniserade infrastrukturs-landskap som stödjer verksamheten med tillräckligtsnabb utveckling, lansering och spridning av efterfrågade nätverkstjänster. Mer exakt undersökerstudien hur större IT infrastrukturs-projekt kan bli genomförda med hjälp av agila arbetssätt efter en initial projektplanering. För att undersöka detta genomförs en fallstudie på Telia Company, som är ett etablerat nordiskt telekommunikationsföretag och som har ett stort arv av IT-infrastruktur. Studien inkluderar interna intervjuer med Telia anställda såväl som externa intervjuer med agila experter. Även en benchmarkundersökning med en väletablerad svensk bank utförs för att bättre förstå utmaningarna och hur agila arbetssätt kan bli tillämpade på bästa sätt. Studien drar slutsatsen att agila arbetssätt med influens av de agila ramverken Scrum och Kanbanmed fördel kan bli tillämpade på team-nivå för mer agila verkställanden. Dock begränsas agila leveranser till stor del av det omgivande verksamhetslandskapet. Detta på grund av beroenden av samarbeten från verksamheten i olika utförande-moment och behovet av att vara sammanvävd med verksamhetsbehov och intressentkrav i leveranserna. Sammanfattningsvis menar studien att tillämpningen av agila arbetssätt på team-nivå i kombination med en nära dialog med intressenter samt ett initiativ för att skala agilt, är nyckeln för mer agila infrastrukturs-leveranser. För att uppnå detta, krävs även investering inom automation. På så vis kan end-to-end-strukturerade leveransprocesser bli bättre utvecklade och infrastrukturs-behov bättre förstådda och implementerade i rätt tid. Som ett bidrag föreslår studien en modell för hur detta kan fungera i praktiken, med inspiration från de agila ramverken Scrum, Kanban och SAFe.
40
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
41
Kulhánková, Barbora. "Behaviour Driven Development a Scrum v korporátním prostředí." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-204867.
Full textAbstract:
Agile software development methodologies these days are not used only in small enterprises or startups, they are getting spread around large enterprises as well. An evidence of this fact could be, that Scrum is nowadays the most commonly used approach to software development. So this thesis focuses on usage of agile approaches, Scrum methodology in particular, in large enterprises. Author presents an approach called Behaviour Driven development and proposes how this approach could help dealing with imperfections or barriers of Scrum when used in large enterprises. The major outcome of this thesis is author's own methodology called ScrumFlow, based on Scrum methodology and extended by Behaviour Driven Development approaches. ScrumFlow methodology is published on a website and available for free.
42
Růt, Václav. "Vybrané agilní metodiky v praktických aplikacích." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-203881.
Full textAbstract:
The thesis focuses on concrete application of the selected agile methodologies on the designed new software development methodology in the company Firma 2.0. The theoretical section briefly characterizes agile methodologies in general and then focuses on their representative sample, and thus Scrum, Kanban, SAFe and LeSS and the DevOps movement, which build a framework for the practical section. The selected components, which are used in the second part, are emphasized. Importantly, all of the methodologies are based on the agile manifesto and thanks to that are mutually combinable. The practical section introduces the company Firmy 2.0 together with its existing software development methodology, which is currently insufficient. The shortages are described as bottlenecks of the methodology itself as well as issues of process management of the company. The newly designed software methodology eliminates those drawbacks and integrates new elements and terminology in order to better correspond with the current processes in the company. The main contribution of the thesis is seen in the new design of software development methodology for a small company, which can also be potentially used outside of the company Firma 2.0, associated with a sound theoretical background.
43
Eshtiagh, Peyman. "An evaluation of test processes in an agile environment." Thesis, KTH, Skolan för teknikvetenskaplig kommunikation och lärande (ECE), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-155399.
Full textAbstract:
The aim of this thesis is to improve the reliability and quality of new requested functionality, and existing modules, at Fortum HR System Solutions. This was conducted through an evaluation of the test processes by implementing principles of Software Testing and Test Management. For the study to successfully improve the testing performed at HR System Solutions, existing test processes were analyzed. The analysis was conducted by evaluating the current test processes using theoretical test evaluation styles called maturity models. The methodology of choice was the Testing Maturity Model (TMM), which was adapted to the nature of HR System Solutions requirements, experience and needs. The evaluation used qualitative methods together with pedagogical principles to conduct interviews and workshops to consolidate the theoretical evaluation. Interviews and workshops were conducted within the team of HR System Solutions, where all members of them team contributed to the thesis at some point. An external interview also took place for comparative study. Results of the evaluation, interviews and workshop were compiled and analyzed accordingly. With the analyzed results in place, flaws in the testing processes were apparent. A generalization of the flaws led to the conclusion in the form of a suggestion. The conclusive suggestion was for Fortum HR System Solutions to establish a test committee/group role within the team. Considering the current economical and organizational situation this job role would be a divided job role appointed to current members of the HR System Solutions team. The research creates a walkthrough on a potential method on understanding inefficiencies within testing processes of a company and providing a cause-based solution.<br>Undersökningen är inriktad på att förbättra tillförlitligheten och kvalitén på ny begärd funktionalitet, och befintliga moduler, på Fortum HR System Solutions. Detta genomfördes genom en utvärdering av testprocesser genom implementation av principer inom Software Testing samt Test Management. För att förbättra testningen som utförs på HR System Solutions var det nödvändigt att analysera de befintliga testprocesserna. Analysen genomfördes genom att utvärdera de nuvarande testprocesserna med hjälp av teoretiska utvärderingsmetoder som kallas Maturity Models. Den valda metoden var Testing Maturity Model (TMM) som tillämpades med avseende på HR System Solutions förutsättningar, erfarenheter och behov. Utvärderingen använder sig av kvalitativa metoder samt pedagogiska principer för att genomföra intervjuer och workshops stärka den teoretiska utvärderingen från TMM. Intervjuer och workshops genomfördes inom HR System Solutions arbetslag, där alla medlemmar bidrog till examensarbetet. Även en extern intervju gjordes i jämförande syfte. Resultatet av utvärderingen sammanställdes och analyserades i enlighet med de förnämnda teoretiska ramvärken. Med hjälp av analyserna visade sig bristerna hos HR System Solutions testprocesser. En generalisering av bristerna gjordes, vilket ledde till slutsatsen i form av ett förslag. Det slutliga förslaget innebar att Fortum HR System Solutions behöver upprätta en testkommitté/grupp inom arbetslaget. Undersökningen visar en potentiell metod för att förstå ineffektiviteten inom testprocesser i ett företag, och tillhandahålla en orsaks-baserad lösning.
44
Мірошнікова, Ірина Анатоліївна, Ирина Анатольевна Мирошникова, Iryna Anatoliivna Miroshnikova, Богдан Володимирович Гайдабрус, Богдан Владимирович Гайдабрус, and Bohdan Volodymyrovych Haidabrus. "Flexible Methodologies in the Management and Realization of the Project Portfolio Internal Diversification of Enterpris." Thesis, Sumy State University, 2016. http://essuir.sumdu.edu.ua/handle/123456789/47033.
Full textAbstract:
The questions of the feasibility of using flexible methodologies in the diversification projects was consider in this work. It is shown, that in a related diversification of projects, the most effective approach to project management is the using of agile methodologies.
45
Calderón, Pereda Giancarlo Daniel, Rodriguez Daymo Rodrigo Chavez, Medina Claudio Martin Leon, and Rodríguez Hilda Magally Vasquez. "Propuesta de implementación de una PMO apoyándose en un framework Lean-Agile para una empresa de servicios compartidos." Master's thesis, Universidad Peruana de Ciencias Aplicadas (UPC), 2021. http://hdl.handle.net/10757/657232.
Full textAbstract:
En el siguiente trabajo de investigación tiene como objetivo elaborar una propuesta de implementación de una PMO apoyándose en un framework Lean - Agile para una empresa de servicios compartidos, el cual brinde el soporte en la Gestión de Proyectos en el área de TI de la empresa, debido a la cantidad de proyectos que se reciben en el área de TI; por lo cual esta propuesta permitirá mejorar el desempeño en la gestión de los proyectos en la empresa.
Basado en los principios Ágiles, acompañado de las buenas prácticas Lean, el framework propuesto estará compuesto por los servicios que brindará la PMO, de acuerdo con el análisis de interesados que se realizó como parte del diagnóstico para la identificación de los mismos.
Cada servicio contará con la organización necesaria a partir de entregables y lineamientos ágiles que permita a la empresa obtener una mejor planificación, desarrollo y ejecución para la realización de proyectos y lograr la concreción de los objetivos trazados y metas propuestas para cada uno de ellos. Todo esto de acuerdo a un plan de implementación de esta propuesta, así como también se realiza una evaluación financiera donde se indicará los beneficios financieros y no financieros, el cual mostrará la viabilidad de la propuesta.<br>The following research aims as main objective to develop a proposal for the implementation of a PMO based on a Lean - Agile framework for a shared services company, which will provide support in Project Management of the IT area of the company, which is due to the several projects received by the IT area. This proposal will allow to improve performance in project management of the company.
Based on Agile principles, followed by good Lean practices, the proposed framework will be composed of services that the PMO will provide, in accordance with the stakeholder analysis that was carried out as part of an identifying diagnosis.
Each service will have the necessary organization, based on deliverables and agile guidelines that allow the company to obtain better planning, development and execution to carry out projects and achieve the objectives stated and goals proposed for each of them.
All this according to an implementation plan for this proposal, as well as a financial evaluation is carried out indicating the financial and non-financial benefits, which will show the viability of the proposal.<br>Trabajo de investigación
46
Chidyiwa, Octavia. "An investigation of the best-practices for implementing an Ecommerce software engineering project comparing two common methodologies, viz. Agile and Traditional." University of the Western Cape, 2020. http://hdl.handle.net/11394/7925.
Full textAbstract:
Masters of Science<br>In a world where technology is advancing at a very rapid pace, global competition has significantly increased, and this is putting pressure on software companies to produce quality software. It has therefore become critically important to manage well the implementation of software engineering projects by employing effective methods that ensure the best product is produced. The most popular software project implementation methodologies are the Traditional methods and Agile methods. This research explored these two methodologies by comparing the strength and weakness of both approaches. The research was conducted using a constructionist epistemology with a critical inquiry using the grounded theory methodology, applying both quantitative and qualitative methods to the case studies. Findings were collected through participant observation using a designed questionnaire targeting a selected sample of the study population. This sample of the population consisted of Ecommerce organizations in the Western Cape province of South Africa to establish which of the Traditional or Agile methods would best lead to the successful implementation of Ecommerce software engineering projects. The research results showed that the Agile methodology was the preferred and recommended approach. Very few participants of the research supported the Traditional approach to still be considered and used for projects with well-known end goals. An Ecommerce website prototype for a local Cape Town business was constructed as following the Agile approach to measure and validate the findings of the research. The prototype was built successfully from conception to the final delivery product and on time confirming the Agile approach as best for Ecommerce software development. In conclusion, the Agile methodology is the choice approach based on reviewed literature, the research results, and the prototype construction. These results will help in critical decision making regarding an appropriate development methodology to follow for the Ecommerce industry in the Western Cape.
47
COSTA, Larissa Nepomuceno. "Investigação sobre o uso de teletrabalho no contexto de metodologias ágeis." Universidade Federal de Campina Grande, 2018. http://dspace.sti.ufcg.edu.br:8080/jspui/handle/riufcg/1612.
Full textAbstract:
Submitted by Lucienne Costa (lucienneferreira@ufcg.edu.br) on 2018-08-30T18:58:34Z
No. of bitstreams: 1
LARISSA NEPOMUCENO COSTA – DISSERTAÇÃO (PPGCC) 2018.pdf: 1744146 bytes, checksum: 0bcd79f3d6e7fdb18cb617ae84dec90f (MD5)<br>Made available in DSpace on 2018-08-30T18:58:34Z (GMT). No. of bitstreams: 1
LARISSA NEPOMUCENO COSTA – DISSERTAÇÃO (PPGCC) 2018.pdf: 1744146 bytes, checksum: 0bcd79f3d6e7fdb18cb617ae84dec90f (MD5)
Previous issue date: 2018-02-01<br>O teletrabalho é um modo de trabalho especial, há muitos anos utilizada no Brasil
e no mundo, onde o teletrabalhador desenvolve suas atividades remotamente, fora do
local de trabalho tradicional. Existem poucas pesquisas e estudos de caso na literatura
sobre a experiência de teletrabalho em ambientes de desenvolvimento de software que
utilizam metodologias ágeis. A intenção deste trabalho é investigar o impacto da
implantação do teletrabalho em projetos de desenvolvimento de software que utilizam
métodos ágeis na percepção dos teletrabalhadores, gerentes e telegerentes e indicar
recomendações práticas que orientem a adoção do teletrabalho. Foi executado um estudo
de caso, envolvendo dois projetos de desenvolvimento de software, com o intuito
de investigar o impacto da introdução do teletrabalho na qualidade e produtividade
de projetos reais. Ainda foi elaborada uma pesquisa qualitativa em que seus resultados
foram importantes ao gerar as diretrizes para a implantação do teletrabalho em
projetos de desenvolvimento de software. Os resultados deste trabalho mostram que,
de acordo com a percepção dos gerentes e desenvolvedores, a produtividade da equipe
aumentou e a qualidade do código não foi afetada. Também é importante dar atenção
à comunicação, utilizando ferramentas de áudio e vídeo que minimizem o tempo de
resposta das iterações entre a equipe. Além disso, foram apresentadas recomendações
e diretrizes práticas para orientar a fase de implantação do teletrabalho em projetos
de desenvolvimento de software usando metodologias ágeis.<br>Remote working is a special working method, used in Brazil and in the world
for many years, in which the teleworker develops his activities remotely, outside the
traditional workspace. Few researches and case studies on the teleworking experience
in software development environments that use agile methodologies can be found in
the literature. This work aims to investigate the impact of teleworking in software
development projects that use agile methods in the perception of teleworkers, managers
and tele-managers and indicate practical recommendations that guide the adoption of
this method. A case study involving two software development projects was carried out
in order to investigate the impact of the introduction of teleworking on the quality and
productivity of real projects. A qualitative research was also developed, and its results
were important to generate the guidelines for implementing teleworking in software
development projects. The results of this work show that, according to the perception
of the managers and developers, the productivity of the team increased and the quality
of the code was not affected. It is also important to pay attention to communication,
using audio and video tools that minimize the response time of the interactions between
the team. Furthermore, recommendations and practical guidelines were presented to
guide the implementation phase of teleworking in software development projects using
agile methodologies.
48
Kubalcová, Monika. "ITIL v prostředí agilního vývoje software metodikou Scrum." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2014. http://www.nusl.cz/ntk/nusl-235418.
Full textAbstract:
This thesis follows concept of integration ITIL library and agile methodology Scrum into the IT company developing IT services. After theoretical analysis of both concepts and analysis of chosen company, we will develope methodology, which will tie both process approaches and ensure their perfect synergy. As a methodology support, web application was developed. It evaluates effectivness of processes using key informations and their plot representation. Proposed methodology was presented in the AVG Technologies, which used described processes as template for its internal proceses. Main result of the thesis is set of templates describing processes, which could be specified and applied in companies using Scrum together with ITIL for their development.
49
Uchytil, Albert. "Nástroj pro podporu řízení agilních vývojových týmů." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2019. http://www.nusl.cz/ntk/nusl-399182.
Full textAbstract:
This thesis describes an implementation of a support tool for an agile development team management. In the beginning, it describes a theoretical background for the tool. The thesis also focuses on the selection of the implementation technology, after that it focuses on designing a technical solution and provides an architectural design of the information system itself. It also describes a user testing process and reviews it afterwards. The system is inspired by the latest version of the PMI standard. The conclusion summarizes the work and discusses possible improvements of the created prototype.
50
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 textAbstract:
Mestrado em Gestão de Projetos<br>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<br>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.<br>info:eu-repo/semantics/publishedVersion