To see the other types of publications on this topic, follow the link: Agile systems development methodologies.
Dissertations / Theses on the topic 'Agile systems development 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 systems development methodologies.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Kalubila, Muriel Chibwe. "The contingent use of agile systems development methodologies / M.C. Kalubila." Thesis, North-West University, 2012. http://hdl.handle.net/10394/9778.
Full 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.Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.
2
Garcia, Erik Roberto. "Resource dependencies in parallel development of military systems : a comparison of waterfall and agile development methodologies." Thesis, Massachusetts Institute of Technology, 2014. http://hdl.handle.net/1721.1/105297.
Full textAbstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, 2014.DVD-ROM contains supplemental models: four .mdl files and two .vdf files.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 63-64).
The United States Department of Defense has been plagued with failing programs that are over budget, behind schedule, and exhibit poor performance during testing. Once a program has cost, schedule, or capability issues, follow-on development efforts adopt the underlying issues only to reinforce poor performance. To address these issues that lead to firefighting, one option is to use an Agile software development process to introduce capabilities earlier in the development process for effective testing. Two System Dynamics models compare Agile with the traditional Waterfall development approach to determine: if Agile development reduces the conflict between cost, schedule, and capability constraints; if Agile development reduces firefighting; and will Agile development impact other development tasks. Based on the simulation of each model, Agile did improve the dynamics of parallel development cycles by maximizing the productivity of the entire development team. Under the same System and Software Engineering team size and development release schedule, Agile development increases the quantity of requirements introduced within a development cycle. However, Agile development emphasized less on maturing new technologies leading to considerably less innovative builds. Thesis Supervisor:
by Erik Roberto Garcia.
S.M. in Engineering and Management
3
Noruwana, Nimrod. "How do South African organisations adopt agile methodologies for software development in practice?" Master's thesis, University of Cape Town, 2010. http://hdl.handle.net/11427/11708.
Full textAbstract:
Includes bibliographical references (leaves 81-90).Before organisations adopt agile methods, they need to ensure that they are prepared for the change. They also need to understand the problems they are trying to address by adopting agile methods. Agile methods deviate substantially from traditional methods of systems development (Tolfo & Wazlawick, 2008). This, therefore, makes it difficult for organisations to adopt agile methods even though they might see them attractive, as the adoption of such methods has an effect on organisational culture. If the culture cannot accommodate an agile approach, then the organisation will not be able to adopt agile (Lindvall, Basisli, Boehm, Costa, Dangle, Shull, Teseriero, Williams & Zelkowitz, 2002). Having a culture that is conducive to the adoption of agile methods is almost unanimously perceived by agile experts to be a necessary factor for the introduction of agile methodologies (eWorkshop, 2002). It is also important to understand the phases organisations go through during the process of adopting agile methods.
4
Delcheva, Yana. "Challenges during the transition to Agile methodologies : A holistic overview." Thesis, Internationella Handelshögskolan, Högskolan i Jönköping, IHH, Informatik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-40692.
Full text
5
Tabrez, Shams, and Islam Jan. "Documentation and Agile Methodology." Thesis, Uppsala universitet, Institutionen för informatik och media, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-212653.
Full 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.
6
Wagener, Ruhan Pieter. "Investigating critical success factors in agile systems development projects / Ruhan Wagener." Thesis, North-West University, 2012. http://hdl.handle.net/10394/9251.
Full 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.Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.
7
Mazengera, Bruce Mwai Analinafe. "The use of agile systems development methodologies in the telecommunication industry in South Africa / B.M. Mazengera." Thesis, North-West University, 2009. http://hdl.handle.net/10394/5039.
Full 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.Thesis (M.Sc. (Computer Science))--North-West University, Potchefstroom Campus, 2010.
8
Grey, Johannes. "An investigation of the suitability of agile system development methodologies for the development of data warehouses / J. Grey." Thesis, North-West University, 2006. http://hdl.handle.net/10394/1596.
Full text
9
Tavares, João Luís Boleto. "Metodologias híbridas no desenvolvimento de sistemas embebidos." Master's thesis, Instituto Superior de Economia e Gestão, 2019. http://hdl.handle.net/10400.5/20038.
Full textAbstract:
Mestrado em Gestão de ProjetosNos últimos 20 anos, as metodologias ágeis têm vindo a afirmar-se como uma referência metodológica nos projetos de desenvolvimento de software. Esta realidade alicia muitos gestores a identificarem a necessidade de implementar esta abordagem no desenvolvimento de sistemas embebidos. Todavia, esta tarefa torna-se complexa devido à natureza deste tipo de projetos. Por esta razão têm surgidos propostas de utilização de metodologias híbridas, que são uma abordagem de desenvolvimento que combina práticas ágeis e tradicionais. No entanto, a sua utilização atual tem sido relatada como pouco estruturada, não havendo um enquadramento claro dos benefícios para o desenvolvimento destes sistemas específicos. Assim, este estudo pretende aprofundar o conhecimento atual sobre as práticas correntes no âmbito da utilização das metodologias, explorando e mapeando-as, em particular no que toca às metodologias híbridas. Foram realizadas quatro entrevistas semi-estruturadas para ganhar um maior entendimento sobre o contexto que leva à utilização de metodologias híbridas no desenvolvimento de sistemas embebidos. Posteriormente, foi aplicado um questionário a 132 profissionais da área dos quais se 68 forneceram respostas válidas. A análise dos resultados revelou que as metodologias mais utilizadas em Portugal não diferem das anteriormente reportadas na literatura. Porém, foi possível estabelecer uma dependência estatística entre as metodologias Scrum e Waterfall, confirmando a existência e utilização da metodologia híbrida Water-Scrum-Fall
Across the last 20 years, agile methodologies have substantially increased their influence on software and systems development. This reality encourages many managers to identify the need to implement this approach in embedded systems development projects. However, this task becomes very complex due to the nature of such development projects. For this reason, efforts have been made to use hybrid methodologies, which are a development approach that combines agile and traditional practices. Nevertheless, this use has been reported as unstructured and without a clear framework for the benefits to the development of these specific systems. Thus, this study intends to expand the current knowledge about current practices in the use of methodologies, exploring and mapping them, namely concerning hybrid methodologies. Four semi-structured interviews were conducted to acquire a deeper understanding of the reasons that lead to the use of hybrid methodologies in the development of embedded systems. Subsequently, a questionnaire was applied to 132 professionals in the area of embedded system development, from which 68 provided valid answers were collected. The analysis of the results revealed that the most used methodologies in Portugal do not differ from those previously reported in the literature. Still, it was possible to establish a statistical dependence between Scrum and Waterfall methodologies, confirming the existence and application of the Water-Scrum-Fall hybrid methodology.
info:eu-repo/semantics/publishedVersion
10
Gislen, Mikael. "Dysfunctional aspects of Software Development : An analysis of how lip-service, deception and organisational politics may side-track the result of well-intended methodologies." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5445.
Full textAbstract:
This paper tries to identify and understand the human social obstacles for developing quality software. These include lip-service, cutting corners, deception and effects of internal politics. These obstacles can undermine the good intentions behind the software methodologies. The paper draws from the literature in different disciplines and uses an ethnographic research methodology to create a rich picture of the concerning aspects in the framework of one software development company in India. What stands out among the findings are that internal audits has mainly focused on finding errors in documentation procedures but study of the actual practices has often been shallow. In addition the understanding of business risks by the internal auditors have often been weak. Context. The human based obstacles affecting Software Development Methodology analysed in the context of an ISO 9000 quality system in an Indian Software Development company working mainly with Swedish companies. Objectives. Identifying and increasing the understanding of intrinsic negative social aspects such as lip service, cheating and politics which are affecting the results of Software Development Methodologies and if possible suggest some means to mitigate them. In particular to create a deeper understanding of why people cheat and pay lip service to methodologies and to try to understand the political aspects of methodology and quality systems. There are other positive social aspects, but they are not considered since the objective is about understanding the negative aspects and possibly mitigate them. Methods. Ethnographic research using analysis of ISO 9000 and design artefacts, semi-structured interviews, participation in internal audits, Results. Most focus in audits was on documentation and very less focus on underlying methodologies, some indications of lip-service to process and processes were also mainly managed on a higher level in the organization while the understanding and practices were less well established on lower level. It was hard to get a grip on the internal political aspects since the perception of the subject in the informants view was that it is mainly malicious and therefore embarrassing to speak about. Some conflicts between internal quality goals and customers’ needs were also identified. Conclusions. An ethnographic research methodology gives a rich picture. The analysis gives deeper understanding of the problem areas, but not necessary solutions. The author suggests that at the heart of the problem is a difference in world view. Software professionals generally tend to resolve [technical] problems using a reductionist approach, while these intricate challenges cannot easily be resolved by this approach. A more holistic systemic approach is required and while the software methodology is useful to structure the development it does not resolve these dysfunctions. They have to be resolved on another level. It was also found that further studies is required in particular to better understand Internal politics, the effect of Positive and Negative Incentives, the effect of software metrics on quality performance and subjectivity in customers’ perception and expectation.Uppsatsen försöker förstå mänskliga sociala hinder för att utveckla programvara med hög kvalitet. Dessa hinder inkluderar "läpparnas bekännelser", ta genvägar, vilseleda och internpolitik. Sådana hinder kan underminera utvecklingsmetoder. Denna uppsats bygger på literatur från olika discipliner och använder etnografisk forskningsmetodik för att skapa en rik bild av dessa oroande aspekter inom ramen för ett IT-företag i Indien. Vad står ut är att intern kvalitetsrevision fokuserar för mycket på att finna fel i dokumentationsprocesser medan revision av hur utvecklingsarbetet faktiskt sker har varit för ytligt. Dessutom har de interna revisorernas förståelse av affärsrisker varit svag.
11
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 generalTiivistelmä 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
12
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.
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
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.
15
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:
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.
16
Baumeister, Joachim. "Agile development of diagnostic knowledge systems." Doctoral thesis, [S.l.] : [s.n.], 2004. http://deposit.ddb.de/cgi-bin/dokserv?idn=979655226.
Full text
17
Freitas, Tiago Fernando Alves de. "Agile practices in embedded systems development." Master's thesis, Universidade de Aveiro, 2015. http://hdl.handle.net/10773/18569.
Full textAbstract:
Mestrado em Engenharia de Computadores e TelemáticaAs metodologias ágeis ganharam popularidade depois de um grupo de profissionais em diferentes métodos de desenvolvimento se juntar e criar um manifesto ágil. Estas metodologias foram criadas com o intuito de melhorar a forma de desenvolver software, tendo como foco principal a satisfação do cliente. Cada vez mais estão a ser usadas em diversos projetos substituindo a abordagem mais tradicional que atualmente ainda está muito presente. Por exemplo, Waterfall é uma metodologia tradicional onde todo o desenvolvimento é planeado deixando pouco espaço para alterações por parte do cliente. O interesse das empresas nestas metodologias tem aumentado. As empresas querem saber mais sobre esta nova forma de desenvolvimento e quais as vantagens que estas vão ter comparando com o seu atual método de desenvolvimento, que geralmente é um método tradicional. A aplicação de metodologias ágeis na área de programação para sistemas embutidos é diferente dos sistemas de informação. O desenvolvimento deste tipo de sistemas tem de ter em conta a parte do hardware e software. No contexto da empresa Exatronic, esta dissertação tem como objetivo investigar a abordagem ágil de forma a recomendar práticas que podem ser adaptadas por esta empresa e com elas obter melhores resultados. A empresa disponibilizou um projeto já terminado para as praticas escolhidas serem aplicadas e simuladas, tendo em conta a plataforma de desenvolvimento Atmel Studio e tipo de processadores Atmel usados pela empresa. As práticas recomendadas foram duas, integração contínua e desenvolvimento orientado por testes, pois são as únicas onde é possível criar um ambiente para a sua utilização e simulação. Por fim, são analisadas as vantagens do uso destas praticas no projeto da empresa.
Agile methodologies gained popularity after a group of professionals in different development methods join and create an agile manifesto. These methodologies were created in order to improve the way to develop software, focusing mainly on customer satisfaction. They are increasingly being used in several projects, replacing the more traditional approach currently very present. For example, Waterfall is a traditional approach in which all development is planned, leaving little space for customer changes. The interest of companies in these methodologies has increased. Companies want to know more about this new way of development and what advantages they will have compared to their current development method, which is usually a traditional one. The application of agile methodologies in embedded systems is different from the informational systems. The development of such systems has to take into account the part of hardware and software. In the context of Exatronic company, this dissertation aims to investigate the agile approach in order to recommend practices that could be adapted in the company. Exatronic provided a finished project for the selected practices be implemented and simulated, taking into account the Atmel Studio development platform and the Atmel processors used by the company. The recommended practices were two, continuous integration and test driven development, because they are the only ones where is possible to create an environment for its use and simulation.
18
Tavares, Hugo Rafael Mendes. "Development methodologies for embedded systems." Master's thesis, Universidade de Aveiro, 2013. http://hdl.handle.net/10773/12748.
Full textAbstract:
Mestrado em Engenharia Eletrónica e TelecomunicaçõesO presente documento aborda algumas metodologias de desenvolvimento de projetos e de sistemas embutidos, com enfoque em algumas técnicas para melhorar os produtos e serviços de modo a satisfazer as necessidades dos clientes. Ao longo dos últimos anos, os requisitos funcionais de sistemas compostos por software registaram um aumento extensivo, devido ao avanço de várias tecnologias usadas em dispositivos. Num mundo cada vez mais competitivo, o nível de procura para o desenvolvimento de sistemas de gestão mais eficientes com o objetivo de garantir vantagem competitiva também aumentou. De forma a competir em mercados exigentes, as organizações precisam de adotar estratégias, visando a criação de valor das suas principais funções empresariais de modo a garantir a satisfação dos clientes. A competição pelo mercado exige às organizações que estas procurem alternativas para melhorar as suas metodologias de desenvolvimento. Desta forma, foi organizado o necessário para o desenvolvimento de software embutido no âmbito do desenvolvimento de processos por forma a resolver os métodos atuais, analisando criticamente essas metodologias. Este trabalho foi também desenvolvido em ambiente organizacional, providenciado pela empresa Exatronic. No fim, obtém-se um conjunto de princípios para uma metodologia de desenvolvimento para este tipo de sistemas, com a possibilidade de ser aplicada às atividades da empresa.
Over the past few years, the functional requirements of systems comprised of software have increased extensively, due to the advancement of various technologies used in devices. In an ever increasingly competitive environment, the level of demand for the development of more efficient management systems as a means to achieve high levels of competitive advantage is also increasing. In order to compete in highly unpredictable markets, organizations need to adopt appropriate strategies, aiming at creating value out of their main business functions to guaranty high levels of customer service. Markets competition is driving organizations to find alternatives to improve their development methodologies. The object of study focuses on a topic regarding the methodologies for project development and embedded development necessary to answer customer needs of products and services. The goal is to organize what needs to be done in embedded software development from the standpoint of development process by addressing current methodologies and critically analysing them. This work was also developed in an organizational environment, provided by the organization Exatronic. In the end, principles for a development methodology for this type of systems is obtained, with the possibility to be applied within the organization's activity.
19
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.
20
Cao, Lan. "Modeling Dynamics in Agile Software Development." Digital Archive @ GSU, 2005. http://digitalarchive.gsu.edu/cis_diss/4.
Full textAbstract:
Agile software development challenges the traditional way of software development and project management. In rapidly changing environments, changing requirements and tight schedule constraints require software developers to take a different approach toward the process of software development. However, beyond a few case studies, surveys and studies focused on specific practices such as pair programming, the effectiveness and applicability of agile methods have not been established adequately. The objective of my research is to improve the understanding of and gain insights into these issues. For this purpose, I develop a system dynamic simulation model that considers the complex interdependencies among the variety of practices used in agile development. The model is developed on the basis of an extensive review of the literature as well as quantitative and qualitative data collected from real projects in seven organizations. The development of the model was guided by dynamic hypotheses on customer involvement, refactoring and quality of design. The model was refined and validated using data from independent projects. The model helps in answering important questions on the impact of customer behavior, cost of making changes and economics of pair programming. Experimentation with the model suggests that the cost of change is not constant; instead, its value changes cyclically and increases towards the later phase of development. Also, the results of simulation show that with no pair programming, fewer tasks are delivered and it costs more to deliver a task when compared to development with pair programming. Further, customer behavior has a major impact on project performance. The quality of customer feedback is found to be very critical to the successful of an agile software development project. The primary contribution of this research is the simulation model of agile software development that can be used a tool to examine the impact of agile practices and management policies on critical project variables including project scope, schedule, and cost. This research provides a mechanism to study agile development as a dynamic system of practices rather than using a static view and in isolation. The results from this study are expected to be of significant interest to practitioners of agile methods by providing them a simulation environment to examine the impact of their practices, procedures and management policies.
21
Blomkvist, Stefan. "User-centred design and agile development of IT systems." Licentiate thesis, Uppsala : Deptartment of Information Technology, Uppsala University, 2006. http://www.it.uu.se/research/publications/lic/2006-012/2006-012.pdf.
Full text
22
Shams, Siamak. "Information systems : operationalization of agile software development 2003 – 2007." Thesis, Brunel University, 2007. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.556992.
Full text
23
Patel, V. "A framework for evaluating information systems development methodologies." Thesis, London South Bank University, 1987. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.378945.
Full text
24
Nyfjord, Jaana. "Towards integrating agile development and risk management." Doctoral thesis, Kista : Department of Computer and Systems Sciences (together with KTH), Stockholm University, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:su:diva-8138.
Full text
25
Saleh, Mehdi. "Built-in software quality in Agile development." Thesis, Uppsala universitet, Institutionen för informatik och media, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-413344.
Full textAbstract:
Abstract Waterfall and Agile are the two most popular software development methodologies. Waterfall as the traditional one, is a progressive method. The progress flows in one direction, and upon the completion of previous process. Agile is another software development methodology with more iterative approach and possible change of requirements; with incremental delivery. Agile introduces freedom to requirement change and iterative delivery. However, such a liberty should not disrate software quality. Especially in automotive industry that deals with human safety and security. In such an iterative environment, there is a higher risk to compromise on quality checks before each delivery, due to short intense lead times. There will not be enough time for intensive quality assurance activities after each iteration. The solution to downsize the intensive quality check after each iteration, is to improve development quality during the development and building quality into development processes. This is what we refer as “Built-in quality”; the quality that is built during software artefacts development on a continuous basis. This study conducted at Volvo Cars during Agile transformation time and the main objective was to connect and emphasize the importance of built-in quality in agile software development. In this study we look at existing challenges that decrease quality of software artifacts during the development. Thus, by prevailing those challenges we can improve the software quality during iteration delivery. Such an improvement decreases the amount of intensive quality check after each iteration. Additionally, we look at guidelines and tools that used by different development teams to improve software artifacts’ quality. We also investigate how quality assurance engineer can support builtin quality during agile transformation.
26
Chen, Xi. "Component-based control system development for agile manufacturing machine systems." Thesis, De Montfort University, 2003. http://hdl.handle.net/2086/13263.
Full textAbstract:
It is now a common sense that manufactures including machine suppliers and system integrators of the 21 st century will need to compete on global marketplaces, which are frequently shifting and fragmenting, with new technologies continuously emerging. Future production machines and manufacturing systems need to offer the "agility" required in providing responsiveness to product changes and the ability to reconfigure. The primary aim for this research is to advance studies in machine control system design, in the context of the European project VIR-ENG - "Integrated Design, Simulation and Distributed Control of Agile Modular Machinery".
27
Ehlers, Kobus. "Agile software development as managed sensemaking." Thesis, Stellenbosch : University of Stellenbosch, 2011. http://hdl.handle.net/10019.1/6455.
Full textAbstract:
Thesis (MPhil (Information Science))--University of Stellenbosch, 2011.ENGLISH ABSTRACT: The environment in which all organisations currently operate is undoubtably dynamic. Regardless of the nature, size or geographical location of business, companies are being forced to cope with a rapidly changing world and increasing levels of unpredictability. This thesis tracks the history of software development methodologies leading up to agile development (chapter 2). Agile development has appeared in response to the limitations of traditional development approaches and evolved to address the particular demands of a changing world (chapter 3). The theory of sensemaking is used to gain insight into the functioning of agile development. Sensemaking is introduced and a working definition of this concept is formulated (chapter 4). This research does not argue that agile development is the same as sensemaking, but rather that it can be better understood through sensemaking. Agile development can be seen as a type of sensemaking, but sensemaking is also a generic, universal cognitive ability. The structure and design of agile development is well aligned with sensemaking, and one can understand its nature and the type of management needed to support agile development better from this perspective. In fact, agile development directly supports and facilitates several important elements of the sensemaking process. For successful sensemaking to occur, certain organisational conditions need to be present. The term "managed sensemaking" is introduced to expand this notion. After performing an analysis of agile development (chapter 5), certain pertinent implications and challenges facing organisations are considered (chapter 6). By framing these implications in terms of sensemaking, practical management suggestions can be provided based on a good fit between the problem that agile development is meant to solve and the cognitive requirements of the process leading to a solution. The research conducted in this process opens the door to further research opportunities (chapter 7) and allows for the application of sensemaking in the context of software development methodologies. This study provides insight into the prevalence and functioning of agile methodologies, in software engineering contexts, by leveraging the theory of sensemaking to provide an explanation for the underlying worldview and processes constituting this approach.
AFRIKAANSE OPSOMMING: Die omgewing waarin alle organisasies tans funksioneer in ongetwyfeld dinamies. Maatskappye word genoop om die uitdagings van 'n vinnig-veranderende wêreld die hoof te bied, ongeag die aard, grootte of geografiese ligging van die besigheid. Hierdie tesis volg die geskiedenis van sagteware-ontwikkelingsmetodologiee tot by agile development (hoofstuk 2). Agile development het verskyn as 'n reaksie op die beperkings van tradisionele ontwikkelingsbenaderings en evolueer om aan te pas by huidige uitdagings (hoofstuk 3). Die teorie van sensemaking word gebruik om insig te verkry in die funksionering van agile development. Sensemaking word ingelei en 'n werksdefinisie word geformuleer (hoofstuk 4). Hierdie navorsing argumenteer nie dat agile development dieselfde is as sensemaking nie, maar eerder dat dit beter verstaan kan word deur sensemaking. Agile development kan wel gesien word as 'n tipe sensemaking, maar sensemaking is ook 'n generiese, universele kognitiewe vermoe. Die struktuur en ontwerp van agile development is goed belyn met sensemaking, en 'n mens kan die aard daarvan en tipe bestuur benodig om agile develop- ment te ondersteun beter verstaan vanuit hierdie perspektief. Tewens, agile development ondersteun en fasiliteer verskeie belangrike elemente van die sensemaking proses direk. Vir suksesvolle sensemaking om plaas te vind, word sekere organisatoriese toestande benodig. Die term "managed sensemaking" word ingelei om hierdie idee uit te brei. Na 'n analise van agile development (hoofstuk 5) word sekere dwingende implikasies en uitdagings, wat organisasies in die gesig staar, oorweeg (hoofstuk 6). Deur hierdie implikasies te plaas in sensemaking-terme kan praktiese bestuursvoorstelle aangebied word, gegrond op 'n goeie passing tussen die probleem wat agile development probeer aanspreek en die kognitiewe vereistes van die proses wat lei na 'n oplossing. Die navorsing wat onderneem is in hierdie proses ontsluit moontlikhede vir verdere studies (hoofstuk 7) en skep die moontlikheid vir die toepassing van sensemaking in die konteks van sagtewareontwikkelingsmetodologiee. Hierdie studie bied insig in die voorkoms en funksionering van agile methodologies in sagteware-ingenieurwese omgewings deur die teorie van sensemaking te hefboom om 'n verduideliking vir die onderliggende wereldbeeld en prosesse aan te bied.
28
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
29
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.
30
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.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.
31
Gena, Kriti. "Suitability of Model Based Systems Engineering for Agile Automotive Product Development." The Ohio State University, 2020. http://rave.ohiolink.edu/etdc/view?acc_num=osu1595500667122794.
Full text
32
D'Angelo, Laura. "Evaluation of code generation in agile software development of embedded systems." Thesis, Uppsala universitet, Avdelningen för datorteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-353798.
Full textAbstract:
Generating code from software models is considered to be a new generation leap within software development methods. The objective of this M.Sc. project is to evaluate how different approaches to modelling and code generation affect embedded systems software development and propose recommendations on how to improve software development. Two product areas at Saab Surveillance EW Systems in Järfälla, Stockholm, are used as study objects. A research overview is made to highlight themes regarding modelling, code generation and software development in general. Based on these, interviews are held with system engineers and software developers at each product area, where they use different modelling and code generation approaches. The two development processes are described thoroughly. Challenges and advantages related to each area’s approach are investigated. Software development within product area A is affected by the product complexity and the larger scale of the development, including projects running over a longer time with more teams involved. Recommendations include enabling code generation by aligning it with other investments on process improvement and limiting the approach to generating some system components. Software developers within product area B can use full code generation, enabled by the limited product complexity. The product area is affected by software standards and external requirements on the process. Recommendations include extending the modelling approach to make it easier to trace functionality from system to software level. Conclusions are that both product areas can apply modelling and code generation to more software development activities to improve their respective development processes.
33
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.
34
Jonasson, Ingi. "Developing the Information Systems of Tomorrow : competencies and methodologies." Thesis, University of Skövde, Department of Computer Science, 2000. http://urn.kb.se/resolve?urn=urn:nbn:se:his:diva-493.
Full textAbstract:
Information systems are getting more and more multimedia-based as well as network-based. This evolution, as well as an increased rate of change, put new demands on methods and competencies required for developing future information systems. In this work, we give an overview of the different types of information systems and methods for information systems development, especially with respect to multimedia aspects. Multimedia systems development is discussed particularly with respect to the dual processes of software engineering and content development. Possible future directions are pointed out, in which information systems development seems to become an even more multidisciplinary effort. As a result we present a list of competencies required for multimedia information systems development as well as possible research areas of interest. These research areas cover the following issues regarding the development of multimedia information systems: project management, conceptual modelling, content maintenance, requirement treatment and development approaches.
35
Tan, Kia Miang Richard. "Application of information systems development methodologies to business process reengineering." Thesis, Henley Business School, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.302576.
Full text
36
Boström, Gustav. "Simplifying development of secure software : Aspects and Agile methods." Licentiate thesis, KTH, Numerical Analysis and Computer Science, NADA, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-3913.
Full textAbstract:
Reducing the complexity of building secure software systems is an important goal as increased complexity can lead to more security flaws. This thesis aims at helping to reduce this complexity by investigating new programming techniques and software development methods for implementing secure software. We provide case studies on the use and effects of applying Aspect-oriented software development to Confidentiality, Access Control and Quality of Service implementation. We also investigate how eXtreme Programming can be used for simplifying the secure software development process by comparing it to the security engineering standards Common Criteria and the Systems Security Engineering Capability Maturity Model. We also explore the relationship between Aspect-oriented programming and Agile software development methods, such as eXtreme Programming.
37
Ouriques, Raquel. "Understanding and Supporting Knowledge Management in Agile Software Development." Licentiate thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-18509.
Full textAbstract:
Background. Agile Software Development (ASD) promises agility and flexibility in dealing with uncertainty by prioritizing interaction between people supported by informal communication and knowledge sharing. The lack of practices to manage the knowledge as a resource might jeopardize the application of knowledge in the production of goods and service. The utilization of Knowledge Management (KM) strategies can significantly support achieving and sustaining competitive advantage and brings several benefits to software development. However, how to manage knowledge in ASD is still not well understood or investigated. Objectives. The main objective of this thesis is to contribute to the software engineering field by providing a different perspective on directions that KM can take to improve knowledge-based resource (KBR) management in ASD. The detailed objectives are: (i) Understand the current ASD environment regarding KM; (ii) Identify KBRs in ASD and its implications for KM; and (iii) Provide an initial set of variables to evaluate knowledge criticality of knowledge items in ASD. Method. We used a mixed-methods approach to address the objective of this thesis. The methods selected to conduct the studies include systematic literature review, grounded theory, and improvement case study. The data collection comprised a literature review, semi-structured interviews, and practitioners’ feedback through static validation. Results. From our SLR we observed that that KM strategies in ASD promote mainly knowledge transfer through practices that stimulate social interaction to share tacit knowledge in the project layer, increasing the risk of losing knowledge by keeping the knowledge localized inside a few individual’s minds. When it comes to coordination, practitioners utilize KBRs in their routines, through social collaboration within teams’ environment/settings. However, this process is nonsystematic, which brings inefficiency to KBR utilization resulting in knowledge loss. It can generate negative implications to the course of the software development, including meaningless searches in databases, frustration because of recurrent problems, and unawareness of knowledge sources. To support decision making related to knowledge retention, we have developed an initial version of the method to evaluate the criticality (KCEM) of a knowledge item, which is divided into two categories, relevance, and scarcity. Conclusion. The current results of this thesis are of particular interest. However, we recognize that the work is unfinished. As a complement to this thesis, we have planned our long-term objective, which is to contribute to creating scalable KM solutions for companies adopting ASD.We divide this long-term objective into three studies: Carry out a complementary study to apply KCEM in different companies; explore efficient ways of storing codified knowledge in combination with the KCEM, and investigate how to define metrics to evaluate the outcomes of KM practices.S.E.R.T.E.R.T. Research Profile
38
Pringle-Wood, Wayne Austen. "Agile software development as a response to complexity." Thesis, Stellenbosch : Stellenbosch University, 2014. http://hdl.handle.net/10019.1/86373.
Full textAbstract:
Thesis (MPhil)--Stellenbosch University, 2014.ENGLISH ABSTRACT: Organisations are faced with ever increasing complexity. While there are many responses to complexity just as there are many definitions of complexity this thesis highlights the use of agile software development as a useful method. The case of agile software development is influenced by its people first approach and minimal process implementation to implement constraints in which phenomena of complexity can be understood. Chapter 1 introduces why complexity is relevant in the organisation today and the issues associated with complexity. A basic introduction to agile software development and why it is a response to complexity is tabled. Chapter 2 investigates the concepts of complexity. To highlight the difference between linear and non-linear systems and reductionistic thinking the ideas that not all things are complex is explored. Key concepts of complex systems are described to come to a better understanding of what entails a complex system. Information theory and dynamic systems are discussed including system attributes such as attractors and bifurcations. Finally the theory of complex adaptive systems is presented and a classification of all complexity theories is tabled. Chapter 3 is centred on agile software development, presenting practices and processes as a understanding of how agile software development is applicable to complexity. Three agile methods are identified. Chapter 4 presents the ideas of modelling and limits to understanding. Models of complex systems are useful but are limited, due to the properties of complex systems. The concept of mental models leads to models of organisations and how leaders need to help with transformation of these models towards models that are more aligned to agile type thinking. Chapter 5 looks at the core concepts, and practices of agile applied to complexity and why these are relevant in responding to complexity. Towards the end of chapter the role of narrative is explored in the terms of problem definition and solutioning in complex systems. Chapter 6 concludes the thesis with insights where agile software development is an appropriate response to complexity and the conditions in which it is not.
AFRIKAANSE OPSOMMING: Organisasies staar toenemende kompleksiteit in die gesig en alhoewel daar verskeie maniere bestaan om kompleksiteit teen te werk, asook verskeie definisies van wat kompleksiteit is, focus die tesis op aanpasbare ("agile") sagteware ontwikkeling as n bruikbare metode. Met eienskappe soos “mense/verbruiker/gebruiker – eerste” benadering asook minimale proses implementering, verskaf aanpasbare sagteware ontwikkeling die raamwerk waar binne die konsep kompleksiteit verstaan kan word. Hoofstuk 1 bespreek die kwessies rondom kompleksiteit en die relevansie daarvan in organisasies vandag. Verder word aanpasbare sagteware ontwikkeling kortliks bespreek en hoe dit gebruik kan word om kompleksiteit te verstaan, word getoon. Hoofstuk 2 ondersoek die verskillende konsepte random kompleksiteit. Daar word gekyk na linêre en nie-linêre stelsels asook die oortuiging dat nie alle dinge kompleks is nie word geondersoek. Sleutel kenmerke van komplekse stelsels word beskryf om sodoende ‘n better begrip te kry van wat ‘n komplekse stelsel behels. Informasie teorie en dinamiese stelsels word bespreek, insluitend kenmerke soos “attraktors” en “bifurkasies”. Laastens, word die teorie rondom komplekse aanpasbare stelsels bespreek en ‘n klassifikasie van alle komplekse teorieë word uiteengesit. Hoofstuk 3 fokus op “agile software development” en hoe sulke praktyke en prosesse toepaslik is op kompleksiteit. Daaropvolgend word drie aanpasbare metodes ge-identifiseer en individueel bespreek. Hoofstuk 4 verduidelik die idees rondom modellering en grense van begrip. Modelle van komplekse stelsels kan nuttig wees, maar weens die eienskappe van komplekse stelsels, is die nuttigheid beperk. Die konsep van mentale modelle lei tot modelle van organisasies en hoe leiers hierdie modelle moet transformer na modelle wat meer in-lyn is met agile denkwyses. Hoofstuk 5 kyk na die kern konsepte en praktyke waar “agile” toegepas word tot kompleksiteit en waarom dit relevant is om kompleksiteit teen te werk. In die tweede helfde van die hoofstuk word die rol van narratief ondersoek in terme van probleem-identifisering en die soek na oplossings in komplekse sisteme. Hoofstuk 6 sluit af met insigte tot aanpasbare sagteware ontwikkelingsmetodes as toepaslike oplossing tot kompleksiteit asook die toestande waaronder dit geld.
39
Norman, Ronald Jules. "Integrated development environments in support of information systems design methodologies and systems analysts' productivity." Diss., The University of Arizona, 1987. http://hdl.handle.net/10150/184275.
Full textAbstract:
Integrated development environment products, called CASE technology by practitioners, are being purchased by enterprises to assist systems analysts with the analysis and design of information systems. This work surveys users of a commercially available CASE product. Ninty-one users from 47 enterprises in the U.S. and Canada responded to the personal computer based survey. This work analyses the perceptions of the respondents in an attempt to determine productivity improvement over manual methods. Using the perceptions of the respondents, the component parts of the CASE product were rank ordered in terms of improved productivity. In addition to this, a psychometric preference scaling method was used to interpret the relatedness of the component parts to each other, again based on the perceptions of the respondents.
40
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.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.
41
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.
42
Esterhuyse, Jacques. "The use of object oriented systems development methodologies in data warehouse development / J. Esterhuyse." Thesis, North-West University, 2008. http://hdl.handle.net/10394/3661.
Full textAbstract:
Research has shown that data warehouses potentially offer great investment opportunities to business. To benefit from this, business needs to invest large sums of money. Such investments are very risky, as no guarantee of the success of these ventures can be given.
Object-oriented development has proved successful for developing operational systems in industry. This study researches object-oriented techniques to discover whether these techniques could be used successfully in data warehousing.
A literature study focuses on the definition of an information systems development methodology and defines the components of such methodology. A further literature study on four popular object-oriented methodologies determines the commonalities of these methodologies. In conclusion, a literature study on data warehouse methodologies is done to discover the phases and techniques used in developing data warehouses.
Based on the literature, a method is proposed to build a data warehouse harnessing object-oriented phases and techniques. The proposed method is applied as an interpretive experiment, followed by an evaluation of the data warehouse implemented.Thesis (M.Sc. (Computer Science))--North-West University, Potchefstroom Campus, 2009.
43
Hebermehl, Janis. "Methodologies and Value of using SYSML in a Spacecraft Development Environment." Digital Commons at Loyola Marymount University and Loyola Law School, 2007. https://digitalcommons.lmu.edu/etd/389.
Full textAbstract:
Systems architecting has been evolving for the last several decades. There have been significant advances in systems engineering and development technologies to directly address large, complex systems that present formidable risks and difficulties in their design, construction, deployment and evolution. These advances have focused on the earliest period of design decision-making and evaluation, referred to as the architectural level of system development. The architectural level of systems development consists of making decisions about overall design goals, requirements, structure, and development strategies. Many analysis and development innovations have resulted from this attention to the architectural level. Among these innovations are architecture modeling languages with associated tools and environments; architecture frameworks, model languages, tools; and techniques for architecture analysis, evaluation, and architecture-based reuse. Boeing has capitalized on these advancements by investing in the development of processes and tools.
This paper presents a recommended system architecture approach and processes for implementing an architectural modeling framework (i.e. DODAF), language (i.e. SysML), and tool. It will provide a frame of reference within which to address implementation and adoption decisions. To these ends, this project is intended to determine the value of implementing SysML in a spacecraft development environment.
44
Rajamundry, Ajay Kumar, and Bogdan Gabriel Onete. "Capturing domain knowledge from very small enterprises, during agile development - a Case Study." Thesis, Högskolan i Jönköping, Tekniska Högskolan, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-45306.
Full textAbstract:
Very Small Enterprises (VSEs) are currently the backbone of all industries, since they account for roughly 80% of the world’s economy. In some countries, they account for over 95% of all companies and enterprises. As such, VSEs are a fundamental element in any given industry. Because of this, understanding how VSEs function and how, as a software developer, work and think is crucial to facilitate the software development process. A software unaware VSE (SUVSE) is a company which has little tangency with understanding software in general. The problem lies in how to properly and efficiently communicate with SUVSE, due to their limitations, as well as the general lack of knowledge regarding software development. This report will cover the topic of challenges faced when working with a very small company for gathering domain knowledge (DK) and facilitating the communication and exchange of meaningful information, in the context of developing a software product, using agile methodologies. In the report, some of the more popular agile methodologies will be covered and chosen, in addition to existing ISO standards for VSEs. The purpose of the research is to answer the following questions: What topics are software unaware very small enterprise (SUVSE) aware of, in the software development process? Which aspects of the software development process must be known by a software unaware domain expert of a very small enterprise (VSE), so that a software development team can capture the required domain knowledge (DK)? How is the software unaware very small enterprises (SUVSEs) understanding of the software development process affected by their involvement in an agile development methodology? To fulfill the purpose of the study, a case study was performed using 3 techniques to gather data: questionnaire, observation and interview. The participants were employees and CEOs from a few VSEs, contacted either via phone or face-to-face meetings. The study showed the problems faced when working with SUVSE, what steps should be performed to facilitate communication with domain experts for gathering DK, and how the VSE can benefit from the knowledge and experience gained because of actively participating in the software development process. It concludes with practices on how to improve communication between software developers and VSE stakeholders to optimize the exchange of meaningful data and knowledge in the context of VSEs, and recommends future work based on the findings.
45
Ndlela, Mandlakazi. "Exploring How Business Analysts Contribute To The Dynamic Capabilities Of Agile Software Development Teams." Master's thesis, Faculty of Commerce, 2021. http://hdl.handle.net/11427/32953.
Full textAbstract:
Today's organisations are characterised by high competition and a volatile business environment which continues to be a predicament for agile software development managers and practitioners. Software development frameworks that are designed to help organisations respond to these environments include a group of flexible methodologies known as Agile Software Development. However, reliance on mainly software techniques and tools might not be sufficient, hence the need to consider the capabilities of individual team members, particularly those of Business Analysts. Given that agile methodologies do not explicitly advocate the relevance of Business Analyst role, literature reveals ongoing debates regarding the role of Business Analysts in Agile Software Development teams. This can be attributed, in part, to a knowledge gap concerning the manner in which Business Analysts contribute to overall team capabilities, particularly those which are essential in enabling teams to respond to environmental changes. The purpose of this study was to address this gap by investigating how Business Analysts contribute to the Dynamic Capabilities of Agile Software Development teams. Adopting a deductive approach, this study adapted and applied a research model based on the Dynamic Capabilities theory to explore the value of business analysts in agile teams. This study is interpretive and was executed using a qualitative, single case-study research strategy directed at an Agile Software Development team in the financial services industry. Data was collected through face-to-face, semi-structured interviews; a group interview; nonparticipant observation; documentation; and physical artefacts. The thematic analysis technique was used to analyse the data. Findings reveal that there are several factors that allow Business Analysts to contribute to the Dynamic Capabilities of Agile Software Development teams which include: sharing business operations tacit knowledge; promptly sharing insights about requirement changes and assisting team members in completing tasks; as well as actively participating in sprint planning meetings. The findings also showed that Business Analysts experience difficulty in contributing to Dynamic Capabilities when they lack system, industry, and business rules knowledge. This study provides a useful contribution in two ways. Firstly, it proposes a model that can be applied by researchers to help explore ways in which individuals influence team dynamic capabilities. Secondly, this contribution is important for practitioners as it highlights how the knowledge, skills, and behaviours of Business Analysts may support or hinder their ability to contribute to the Dynamic Capabilities of Agile Software Development teams. This study can be used to inform the design of capacity development programmes for individual team members and Business Analysts, and thus help managers to curate teams which will best promote Dynamic Capabilities. Although substantial data was collected, this research was limited, to some extent, by restricted access to classified and confidential documents. It is proposed that future researchers consider applying a multiple case-study strategy to allow for comparative analysis between teams that operate in different contexts.
46
Shaikh, M. U. "The analysis and comparison of system development methodologies in software engineering." Thesis, University of Liverpool, 1986. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.233888.
Full text
47
Rathor, Shekhar. "Facilitators for Software Development Agility." FIU Digital Commons, 2016. http://digitalcommons.fiu.edu/etd/3059.
Full textAbstract:
Software development methodologies provide guidelines and practices for developing information systems. They have evolved over time from traditional plan-driven methodologies to incremental and iterative software development methodologies. The Agile Manifesto was released in 2001, which provides values and principles for agile software development. Over the last few years, agile software development has become popular because its values and principles focus on addressing the needs of contemporary software development. IT and Business teams need agility to deal with changes that can emerge during software development due to changing business needs. Agile software development practices claim to provide the ability to deal with such changes. Various research studies have identified many factors/variables that are important for agile software development such as team autonomy, communication, and organizational culture. Most of these empirical studies on agile software development focus on just a few variables. The relationships among the variables is still not understood. The dimensions of agility and the relationship between agility and other variables have not been studied quantitatively in the literature. Also, there is no comprehensive framework to explain agile software development. This research study addresses these research gaps.
This study analyzed a comprehensive research model that included antecedent variables (team autonomy, team competence), process variables (collaborative decision making, iterative development, communication), delivery capability, agility, and project outcomes (change satisfaction, customer satisfaction). It presents key dimensions of agility and quantitatively analyzes the relationship between agility and other variables. The PLS analysis of one hundred and sixty survey responses show that process variables mediate the relationship between antecedent variables and delivery capability and agility. The findings show that the delivery capability of the teams contributes to agility, antecedents and process variables contribute to agility, and delivery capability for better customer satisfaction. These results will help IS practitioners to understand the variables that are necessary to achieve agility for better project outcomes. Also, these quantitative findings provide better conceptual clarity about the relationship between various key variables related to agile software development.
48
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.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.
49
Charatan, Quentin. "A unified systems development paradigm which synthesises Object-Oriented Methodologies and VDM." Thesis, London South Bank University, 1996. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.336382.
Full text
50
Zhu, Weihua. "Design and development of novel routing methodologies for dynamic roadway navigation systems." Diss., [Riverside, Calif.] : University of California, Riverside, 2009. http://gateway.proquest.com/openurl?url_ver=Z39.88-2004&rft_val_fmt=info:ofi/fmt:kev:mtx:dissertation&res_dat=xri:pqdiss&rft_dat=xri:pqdiss:3350082.
Full textAbstract:
Thesis (Ph. D.)--University of California, Riverside, 2009.Includes abstract. Available via ProQuest Digital Dissertations. Title from first page of PDF file (viewed March 12, 2010). Includes bibliographical references (p. ). Also issued in print.