Dissertations / Theses: 'Agility in Software Development'

1

Rathor, Shekhar. "Facilitators for Software Development Agility." FIU Digital Commons, 2016. http://digitalcommons.fiu.edu/etd/3059.

Full text

Abstract:

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.

APA, Harvard, Vancouver, ISO, and other styles

2

Maruping, Likoebe Mohau. "Essays on agility in software development teams process and governance perspectives /." College Park, Md. : University of Maryland, 2006. http://hdl.handle.net/1903/3415.

Full text

Abstract:

Thesis (Ph. D.) -- University of Maryland, College Park, 2006.
Thesis research directed by: Business and Management. Title from t.p. of PDF. Includes bibliographical references. Published by UMI Dissertation Services, Ann Arbor, Mich. Also available in paper.

APA, Harvard, Vancouver, ISO, and other styles

3

Roman, Greice de Carli. "Characterizing the presence of agility in large-scale agile software development." Pontif?cia Universidade Cat?lica do Rio Grande do Sul, 2016. http://tede2.pucrs.br/tede2/handle/tede/7518.

Full text

Abstract:

Submitted by Caroline Xavier (caroline.xavier@pucrs.br) on 2017-06-30T18:19:05Z No. of bitstreams: 1 DIS_GREICE_DE_CARLI_ROMAN_COMPLETO.pdf: 9835425 bytes, checksum: aa605361de91b916006af4710a54365b (MD5)
Made available in DSpace on 2017-06-30T18:19:05Z (GMT). No. of bitstreams: 1 DIS_GREICE_DE_CARLI_ROMAN_COMPLETO.pdf: 9835425 bytes, checksum: aa605361de91b916006af4710a54365b (MD5) Previous issue date: 2016-12-15
Em fevereiro de 2001, o Manifesto ?gil foi proposto tendo como princ?pio equipes pequenas e co-localizadas. No entanto, ao longo destes 16 anos, a agilidade tamb?m foi posta em pr?tica em outros contextos, como por exemplo: equipes distribu?das e sistemas complexos, utilizando-se o termo "Desenvolvimento ?gil em Larga Escala". N?o h? uma defini??o clara e compreensiva de como a agilidade est? presente neste contexto. Assim, nosso trabalho preenche essa lacuna com o objetivo de caracterizar a agilidade no Desenvolvimento ?gil em Larga Escala. Neste trabalho, realizou-se um estudo organizado em duas fases. Na Fase 1, denominada Base Te?rica, realizamos um estudo do estado-da-arte da ?rea. Na Fase 2, denominado Estudo Emp?rico, n?s realizamos duas investiga??es: um estudo de campo em uma empresa ?gil em larga escala, para identificar o desenvolvimento durante o processo de transforma??o da empresa para esta nova abordagem e, um grupo focal, para identificar como as equipes ?geis em larga escala que v?m utilizando os m?todos ?geis o quanto se percebem em termos de aspectos de maturidade ?gil. Estes resultados contribuem para os pesquisadores e profissionais entenderem melhor como a agilidade e definida e percebida nestes grandes ambientes. O conhecimento e ?til para aqueles que querem entender como o desenvolvimento ?gil se adapta a tais ambientes e para pesquisadores com o objetivo de se aprofundar sobre o tema.
The Agile Manifesto was proposed in February 2001 having in mind small and collocated teams. However, agile has also been put in practice in other settings (e.g. large teams, distributed teams, complex systems) under the term ?Large-Scale Agile Development' (LSAD). There is no clear definition for and understanding of how agility is present in this setting. Thus, our work fills in this gap aiming to characterize agility in LSAD. We conducted a study organized in two phases. In Phase 1, named Theoretical Base, we conducted the state-of-the-art of the area. In Phase 2, named Empirical Study, we conducted two investigations: a field study in a large-scale agile company to identify how agility was developed during the transformation process of the company to this new approach, and a focus group to identify how large-scale agile teams that have been using agile for a certain while perceive themselves in terms of maturity in agile aspects. Findings contribute to researchers and professionals better understand how agility is defined and perceived in large settings. This knowledge is useful for those who want to enter the agile journey in such similar environments and for researchers aiming to further explore the topic.

APA, Harvard, Vancouver, ISO, and other styles

4

Salvador, David Musat. "Hindrances for Agility : Detection and Recommendations." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3202.

Full text

Abstract:

Context. Global Software Development is software work undertaken at geographically separated locations across national boundaries in a coordinated fashion involving real time or asynchronous interaction. Distributed Agile Development aims at the benefits of both Agile Software Development and Global Software Development aiding the distributed teams to overcome the challenges brought by the distribution. Objectives. In this study the author investigates whether a globally distributed company is prepared to be agile, determining hindrances for agile and providing recommendations to mitigate or overcome the detected hindrances. Methods. In this case study, surveys and interviews were used to study the hindrances for agile and literature was used to provide the recommendations towards the detected hindrances. Results. 4 hindrances were detected. Only 1 was justified as necessary for the good performance of the distributed company. Several recommendations to overcome the hindrances were proposed. Both hindrances and proposed solutions were validated by the company representative. Conclusions. We conclude that the studied individuals are willing to be agile. As agile is built bottom-up, the company is prepared to be agile. However, they will not be able to be agile until they overcome or mitigate the detected challenges. In the study, several solutions for it are proposed.

APA, Harvard, Vancouver, ISO, and other styles

5

Srinivasan, Jayakanth. "Exploring the Sources of Enterprise Agility in Software Organizations." Doctoral thesis, Västerås : Akademin för innovation, design och teknik, Mälardalens högskola [School of Innovation, Design and Engineering], Mälardalen University, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-6853.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Winter, Jeff. "Measuring usability - balancing agility and formality : for stakeholders' needs in software development /." Licentiate thesis, Karlskrona : Department of Interaction and System Design, School of Engineering, Blekinge Institute of Technology, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00438.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Lee, Harris IV Edward. "Assessing and Improving "Agile Performance" : Using Comparative Agility to Improve Software Development Management." Thesis, KTH, Tillämpad maskinteknik (KTH Södertälje), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-148413.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Buslovic, Maksim, and Samson Deribe. "A Multiple Case Study on Contradictions and Pre-conditions for Outsourcing Agile Software Development Projects." Thesis, Linköpings universitet, Företagsekonomi, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-81884.

Full text

Abstract:

Title: A Multiple Case Study on Contradictions and Pre-conditions for Outsourcing Agile Software Development ProjectsAuthor: Maksim Buslovič & Samson DeribeSupervisor: Jonas SöderlundDate: May 30th, 2012Background: In today’s turbulent business environment organizational success depends on its ability to embrace change and adapt quickly. The ability to satisfy customer is core to profitability; thus being agile is a prominent factor, because customer expectations are never static. One of the project management methods which is quite popular in the software development are is Agile Method. Agile methods depart from the classical project approach as it emphasizes more on interaction among participant, short iteration and continuous feedback to embrace the continuously evolving customer requirements. However, implementing Agile methods in a distributed project work seems to be challenging, thus limiting projects to optimize form their distributed resource as well as external parties.Aim: The purpose of this thesis is to understand how Agile methods contradict with the Outsourcing practice, which ultimately lead to identifying the possibilities to successfully outsource project work based on Agile methods. In addition, the study aims in providing a good ground for future study in ‘Outsourcing within Agile Methods’ to fill the big theoretical gap identified in the area.Methodology: The thesis used a qualitative approach that intends to build theory through iteration by waving back and forth between data and literatures in an inductive manner. The research design was based on multiple case study that used five interviews and one direct observation as an instrument to collect primary data along with secondary data; all three together ensure proper triangulation resulting in higher research validity. Open coding system was used to analyze data; and findings were presented by tables, figures, models and direct quotations.Results: The study shows that values and principles of agile software development which gives much emphasis on proximity in order to have a daily stand-up meetings, visualizations, constant contact with customers and other team members, knowledge sharing and fun disappear when the project is involved in outsourcing partly the development process; because the need use more plans & documentation, clear contracts and less interaction implying a contradiction in both ‘Agile methods’ and ‘Outsourcing’ practices. However, the study identified preconditions that must be considered while involving in outsourcing part of Agile software development: Outsource only if the part to be outsourced is not related to core product; Put a complete team in a co-located manner; Minimize interdependence among distributed teams; and there should be enough time before delivering product to customers.

APA, Harvard, Vancouver, ISO, and other styles

9

Mulder, Susan. "An action research study on the use of Scrum to provide agility in data warehouse development." Diss., University of Pretoria, 2010. http://hdl.handle.net/2263/24561.

Full text

Abstract:

Data warehousing is a new and emerging field. Projects tend to be complex and time consuming. Because of this complexity, teams tend to commit to more than they can deliver. This causes delayed delivery. Applying Agile development styles to data warehousing is one of the alternative methodologies that are being investigated to help teams to accelerate the delivery of business value. Scrum is one of the frameworks that falls within the Agile stream. Scrum focuses on project management and makes use of iterative and incremental development. It tries to deliver the smallest piece of business value the fastest. The paper evaluates the implementation of Scrum in a data warehouse team of a financial investment company. The researcher did an action research study on the team to see if Scrum can be used as a viable alternative framework to bring agility to Data Warehouse development. She examined the changes that the team experienced during and after the implementation of Scrum, focusing on team structure and roles within the teams. The researcher defined a framework to evaluate how well the team implemented Scrum. The researcher also evaluated the quality of work delivered, and the predictability and productivity of the team as metrics to see if Scrum made a difference within the team. The research paper examined why the implementation failed and what issues Scrum highlighted within the team as well as within the way that the company implemented it.
Dissertation (MCom)--University of Pretoria, 2010.
Informatics
unrestricted

APA, Harvard, Vancouver, ISO, and other styles

10

Chidyiwa, Octavia. "An investigation of the best-practices for implementing an Ecommerce software engineering project comparing two common methodologies, viz. Agile and Traditional." University of the Western Cape, 2020. http://hdl.handle.net/11394/7925.

Full text

Abstract:

Masters of Science
In a world where technology is advancing at a very rapid pace, global competition has significantly increased, and this is putting pressure on software companies to produce quality software. It has therefore become critically important to manage well the implementation of software engineering projects by employing effective methods that ensure the best product is produced. The most popular software project implementation methodologies are the Traditional methods and Agile methods. This research explored these two methodologies by comparing the strength and weakness of both approaches. The research was conducted using a constructionist epistemology with a critical inquiry using the grounded theory methodology, applying both quantitative and qualitative methods to the case studies. Findings were collected through participant observation using a designed questionnaire targeting a selected sample of the study population. This sample of the population consisted of Ecommerce organizations in the Western Cape province of South Africa to establish which of the Traditional or Agile methods would best lead to the successful implementation of Ecommerce software engineering projects. The research results showed that the Agile methodology was the preferred and recommended approach. Very few participants of the research supported the Traditional approach to still be considered and used for projects with well-known end goals. An Ecommerce website prototype for a local Cape Town business was constructed as following the Agile approach to measure and validate the findings of the research. The prototype was built successfully from conception to the final delivery product and on time confirming the Agile approach as best for Ecommerce software development. In conclusion, the Agile methodology is the choice approach based on reviewed literature, the research results, and the prototype construction. These results will help in critical decision making regarding an appropriate development methodology to follow for the Ecommerce industry in the Western Cape.

APA, Harvard, Vancouver, ISO, and other styles

11

Reigado, Carolina Rodrigues. "Strategies and habits for adapting the plan in agile teams: a grounded theory and improvisation perspective." Universidade de São Paulo, 2018. http://www.teses.usp.br/teses/disponiveis/18/18156/tde-17122018-090903/.

Full text

Abstract:

The ability of agile teams to adapt the project plan to unexpected problems is still a less-researched area. They must change the project plans as facing unexpected challenges and, even though existing studies relate some aspects to this ability, such as participatory decision-making, openness to discuss problems in an immediate sense and focus on actions to be taken in near future, these studies do not yet offer a complete theory, or set of practices, about how adaptation takes place. What actions and decisions of the team allow for adaptation? Improvisation is an approach that could potentially fill this gap and consists of someone executing an action without previously planning it, or doing it differently from the original plan, when facing a problem. This study presents an investigation of how agile teams adapt when facing unexpected changes or problems during the projects. The concept of improvisation is used and the study involved two agile software development teams and using Grounded Theory (GT). The results indicate that the teams apply different improvisation strategies, such as breaking standard work rules, as well as maintain habits that contribute positively to improvisation. Clients also play an important role in helping teams solve unexpected problems and should be invited to collaborate. These results can be used to assist professionals in search of more effectiveness in agile teams in terms of adapting the plan during the project.
A habilidade de os times ágeis adaptarem o plano do projeto de acordo com problemas inesperados ainda é uma área de pesquisa pouco explorada. Essas equipes precisam ser capazes de adaptar o plano do projeto quando se deparam com desafios inesperados e, ainda que os estudos relacionem alguns aspectos a essa habilidade, como tomada de decisão participativa, abertura para discutir problemas de imediato e foco em ações de curto prazo, os estudos ainda não oferecem uma teoria completa ou conjunto de práticas que descrevam como, de fato, a adaptação acontece. Quais ações e decisões do time lhe garantem a capacidade de adaptação? A improvisação é uma abordagem interessante para compreender esse gap, e consiste em executar uma ação sem previamente planejá-la, ou de uma maneira diferente do que a planejada, quando da ocorrência de um problema ou mudança inesperada. Esse estudo apresenta uma investigação da adaptação em projetos ágeis quando as equipes se deparam com mudanças ou problemas inesperados. O conceito da improvisação é usado e o estudo envolveu dois times ágeis que desenvolvem software, e utilizando o método Grounded theory (GT). Os resultados indicam que os times utilizam diferentes estratégias de improvisação, como quebrar regras de trabalho, assim como mantem hábitos que contribuem positivamente para a improvisação. O cliente também desempenha um papel importante ao ajudar os times a resolverem problemas inesperados, e portanto devem ser convidados a colaborar. Esses resultados podem ser usados para auxiliar profissionais no sentido de obter-se times ágeis mais efetivos na adaptação do plano durante o projeto.

APA, Harvard, Vancouver, ISO, and other styles

12

Wallström, Andreas. "Guidance on Implementing Agile Software Development Methods within a Traditional Environment." Thesis, KTH, Industriell ekonomi och organisation (Inst.), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-296990.

Full text

Abstract:

Agile software development methods keep increasing in popularity. Many organizations who are using traditional software development methods, such as water-fall and stagegate based methods are switching to agile software development methods. This transition can be challenging, especially for organizations using project governance models that hinder the adoption of agile practices. This study aims to provide guidance to managers on how to introduce agile software development methods in such traditional organizations. The study is a single-case study on a large governmental agency in Sweden. Eight interviews with developers, team-leads and managers were conducted. The study identifies practical tools and ideas that managers can use to introduce a shared definition of agile, adopting an agile mindset, dedicated teams, and CI&CD. Together, this guidance supports managers with the introduction of agile software development methods in organizations utilizing traditional project governance structures and traditional software development methods.
Agila systemutvecklingsmetoder fortsätter öka i popularitet. Många organisationer som använder sig av traditionella systemutvecklingsmetoder så som vattenfallsmodellen byter till agila systemutvecklingsmetoder. Denna övergång kan vara utmanande, speciellt för organisationer som använder sig av projektbaserade förvaltningsmodeller som hindrar implementeringen av agila metoder. Den här studien syftar till att ge vägledningen till chefer kring hur de kan introducera agila systemutvecklingsmetoder iden nyss nämnda typen av traditionella organisationer. Studien är en fallstudie gjort på en stor myndighet i Sverige. Åtta intervjuer med systemutvecklare, lag-ledare och chefer har utförts. Studien identifierar verktyg och idéer som chefer kan använda sig avför att introducera en delad gemensam definition av agilt, anamma ett agilt tankesätt, introducera dedikerade teams och CI&CD. Tillsammans hjälper de här verktygen med introduktionen av agila systemutvecklingsmetoder i organisationer som använder sig av traditionella systemutvecklingsmetoder och förvaltningsmodeller.

APA, Harvard, Vancouver, ISO, and other styles

13

ALMEIDA, NETO Humberto Rocha de. "Um modelo de maturidade para governança ágil em tecnologia da informação e comunicação." Universidade Federal de Pernambuco, 2015. https://repositorio.ufpe.br/handle/123456789/17340.

Full text

Abstract:

Submitted by Irene Nascimento (irene.kessia@ufpe.br) on 2016-07-12T19:02:01Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Tese Humberto Rocha - M3 - CORRIGIDA - 27.01.22016 - FINAL - SEM ASSINATURAS.pdf: 7669370 bytes, checksum: b59a4824a693e49ccfb1316ab17c75ba (MD5)
Made available in DSpace on 2016-07-12T19:02:02Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Tese Humberto Rocha - M3 - CORRIGIDA - 27.01.22016 - FINAL - SEM ASSINATURAS.pdf: 7669370 bytes, checksum: b59a4824a693e49ccfb1316ab17c75ba (MD5) Previous issue date: 2015-07-15
A Governança Ágil em Tecnologia da Informação e Comunicação (TIC) é uma área em ascensão que vem sendo sugerida como uma proposta inovadora pautada nos princípios e valores do Manifesto para Desenvolvimento Ágil de Software. O uso de tais princípios e valores tem como principal objetivo a minimização da burocracia na Governança convencional. Alguns autores têm apontado que a maioria das iniciativas para Governança são burocráticas e que a adoção de abordagens mais ágeis ainda é considerada uma tarefa desafiadora. Isto se dá principalmente devido a multidisciplinaridade e relativa incipiência da área. Se por um lado há um conjunto bem estabelecido de princípios e valores ágeis em domínios subjacentes à Governança Ágil em TIC (a exemplo de Desenvolvimento de Software), por outro lado, alguns de seus domínios ainda requerem evolução (a exemplo de Gerenciamento de Serviços, Operações, Infraestrutura, entre outras). Diante deste contexto, esta tese de doutorado propõe um modelo de maturidade denominado MAnGve Maturity Model (M3). O M3 apoia a evolução sistemática e gradual de maturidade em Governança Ágil em TIC. Para tal, o modelo de maturidade proposto estrutura seu conhecimento por meio de cinco níveis de maturidade. Estes níveis foram construídos a partir de um amplo estudo de base teórica (uma revisão ad hoc e uma revisão sistemática da literatura) envolvendo principalmente as áreas de: Agilidade no desenvolvimento de software; Governança em TIC; e modelos de maturidade e capacidade. Por fim, o M3 foi submetido a avaliações por meio de métodos científicos (dois surveys e um focus group) que nortearam melhorias ao modelo proposto. Os resultados destas avaliações apontam o M3 como uma iniciativa relevante e inovadora para este recente campo de pesquisa
Agile Governance in Information and Communication Technology (ICT) is an area on the rise that has been suggested as an innovative proposal based on the principles and values of the Manifesto for Agile Software Development. The use of these principles and values aims to minimize bureaucracy in conventional Governance. Some authors have pointed out that most initiatives for Governance are bureaucratic and that adopting more agile approaches is still considered a challenging task. This is mainly due to multidisciplinary and relative incipiency of the area. On the one hand there is a well-established set of agile principles and values in domains behind the Agile Governance in ICT (for example, Software Development), on the other hand, some of its domains still require evolution (like Service Management, Operations Infrastructure, etc.). Given this context, this doctoral thesis proposes a maturity model called MAnGve Maturity Model (M3). The M3 supports the systematic and gradual evolution of maturity in Agile Governance in ICT. To this end, the proposed maturity model structure their knowledge through five maturity levels. These levels were constructed from a large study of theoretical basis (ad hoc review and systematic literature review) mainly involving areas: Agile software development; Governance in ICT; and capability maturity models. Finally, M3 was subjected to evaluations by scientific methods (surveys and focus groups) that guided the improvements in proposed model. Their results indicate the M3 as an important and innovative initiative for this recent field of research.

APA, Harvard, Vancouver, ISO, and other styles

14

Quast, Marc. "Systèmes d'information sociaux." Phd thesis, Université de Grenoble, 2012. http://tel.archives-ouvertes.fr/tel-00876866.

Full text

Abstract:

Les systèmes d'information d'entreprise actuels s'articulent autour d'applications centrales lourdes, qui ne fournissent pas l'agilité nécessaire pour survivre dans un environnement économique hautement concurrentiel. De nombreux acteurs (unités commerciales, individus, équipes et communautés) doivent introduire leurs propres applications pour pallier à ces limitations, avec pour résultat un système d'information fragmenté, incohérent et impossible à gouverner. Cette étude propose un paradigme d'architecture d'entreprise alternatif, qui s'appuie sur une décomposition plus fine du système d'information et une distribution différente des responsabilités. Il permet à tout acteur de contribuer au système d'information en introduisant des fragments, privés ou partagés avec d'autres acteurs, qui peuvent ensuite être composés pour former des applications dédiées à un profil. Les récents mécanismes de l'informatique sociale sont proposés pour gérer les volumes potentiels importants de fragments émergeant de la communauté d'employés. L'objectif des systèmes d'informations sociaux est à la fois d'améliorer la cohérence et la gouvernabilité du système d'information de l'entreprise et d'exploiter l'intelligence et l'énergie collective de l'entreprise à des fins d'agilité métier maximale.

APA, Harvard, Vancouver, ISO, and other styles

15

Andrei, Arratia-Falcon. "Prioritering av icke-funktionella krav i praktiken : Ur ett agilt perspektiv." Thesis, Uppsala universitet, Institutionen för informatik och media, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-210354.

Full text

Abstract:

Requirements management is an important part of the software development process. The success of a project may depend on how this is handled. Even though several research studies indicates that more attention should be paid on non-functional requirements, the primary focus in practical projects still regards identifying functional requirements. Especially the prioritization of the non-functional requirements has been proven to be of great importance for the success of a project. This report investigates basics in agile requirements management involving opinions from experts from a software development company. This is done with help of existing literature and interviews with key actors involved in prioritization at the company. I investigate prioritization of non-functional requirements and possibilities for agile project development. The results contribute to developing an overall understanding of the agile way of working. The methodology of this report follows a qualitative approach. It is based on secondary data from literature and documents, but also on data collected via interviews. The results are acknowledging earlier findings from the literature and illustrate with examples actual prioritization of non-functional requirements, and how and why prioritization is a complex activity at a company. However, according to one of the most important findings of this study, the strict use of prioritization techniques is not the most urgent necessity for the success of a project.
Kravhanteringen är en viktig del av systemutvecklingsprocessen. Ett projekts framgång kan kopplas till hur detta genomförs. Även om flera studier pekar på att mer uppmärksamhet bör läggas på icke-funktionella krav är den primära fokusen i flera projekt fortfarande att identifiera funktionella krav. Speciellt prioriteringen av de icke-funktionella kraven har visat sig vara av stor betydelse för ett lyckat projekt. Den här rapporten undersöker grunderna i den agila kravhanteringen som involverar åsikter från experter i ett företag inom mjukvaruutveckling. Detta görs med hjälp av befintlig litteratur samt intervjuer med nyckelaktörer involverade i prioriteringen hos företaget. Jag undersöker prioriteringen av icke-funktionella krav och möjligheter för agil projektutveckling hos företaget. Följaktligen kommer resultatet bidra till att ge läsaren en allmän förståelse om det agila arbetssättet. Metodologin för den här rapporten följer ett kvalitativt tillvägagångssätt. Den baseras på sekundär data från litteratur och dokument, men även data insamlat via intervjuer. Resultaten medger tidigare upptäckter från litteraturen och visar med exempel verklig prioritering av icke-funktionella krav samt hur och varför prioriteringen är en komplex aktivitet hos ett företag. Dock är, enligt en av de viktigaste upptäckterna i den här rapporten, ett strikt användande av prioriteringstekniker inte den viktigaste nödvändigheten för ett lyckat projekt.

APA, Harvard, Vancouver, ISO, and other styles

16

Wendler, Roy. "Towards a Maturity Model to Measure Organizational Agility in the Software and IT Services Industry." Doctoral thesis, Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2016. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-209623.

Full text

Abstract:

Agile software development methods reduce project costs and development time by simultaneously enhancing quality. But despite these advantages, agile principles are rarely adopted by the whole organization. In fact, it seems difficult to describe what distinguishes an agile organization from another. Therefore, the objective of this thesis is to gain an understanding what factors constitute agility at an enterprise level and to develop a maturity model as measurement tool. To fulfill this aim, the thesis as based on a multi-paradigmatic approach combining behavioral and design science and utilizes a pluralistic set of research methods belonging to both paradigms. A comprehensive analysis of agility-related frameworks showed that despite partial similarity there is no consensus about what constitutes an “agile organization”. Hence, the thesis identified the structure to be found behind the concept of organizational agility using an exploratory research approach. A survey among organizations in the software and IT services industry was conducted and showed that organizational agility can be described using six interrelated factors that can be further aggregated into the three basic dimensions of “Agility Prerequisites,” “Agility of People,” and “Structures Enhancing Agility.” Based on these results, the Organizational Agility Maturity Model has been developed providing a theoretically and empirically grounded structure of organizational agility supporting the efforts of developing a common understanding of the concept. The application of the maturity model furthermore creates useful benefits for organizations and underscores the strategic character of organizational agility. It generates an awareness about the complexity of organizational agility. Furthermore, it may serve as a reference frame to implement a systematic and well-directed approach for improvements and continuous assessment of actions taken.

APA, Harvard, Vancouver, ISO, and other styles

17

Lagré, Mårten. "Varför arbetar vissa utvecklingsteam agilt med kravhantering och vissa inte? : En fallstudie på Lantmäteriet." Thesis, Högskolan Dalarna, Informatik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:du-25514.

Full text

Abstract:

Kravhantering inom systemutveckling utgör basen för vad som ska utvecklas. Agila systemutvecklingsmetoder blir vanligare för varje dag som går. Det har dock ofta visat sig finnas utmaningar med hur man anpassar just kravhanteringen till de agila metoderna. Verksamheter har olika förutsättningar för att arbeta agilt. Lantmäteriet i Gävle uttryckte ett behov att undersöka varför den agila praxis man hade inte följdes av alla utvecklingsteam i samband med kravhanteringen. Syftet med denna uppsats var därför att undersöka varför vissa utvecklingteam i en verksamhet arbetade agilt med sin kravhantering medan vissa inte gjorde det. För att undersöka detta utförde jag en fallstudie där jag med hjälp av enkäter och intervjuer samlade in data från både utvecklare och personer på verksamhetssidan som var inblandade i kravhanteringen. Resultaten visade att orsakerna till att en agil kravhantering fungerade så olika var flera. Genom att använda en tematisk analys kunde jag urskilja några framträdande orsaker. Kommunikation och flexibilitet samt kunskap och förståelse för olika perspektiv var teman som utgjorde positiva faktorer. De teman som istället utgjorde negativa faktorer var bland andra otydliga roller, brist på direktiv, en övertro till metoder och processer, osynk mellan verksamhet och IT, prioriteringsproblem, förvaltningsplaner, attityder och IT-arkitektur.
Requirements engineering within software development is the foundation of what needs to be developed. Agile methods in software development become more common every day. It has however often been shown that there are certain challenges with how to adopt the requirements engineering to the agile methodology. Businesses have different preconditions for agile methods. Lantmäteriet in Gävle had a need to examine why not all the developing teams followed agile methods within the requirements engineering process. The purpose with this thesis was thus to examine why some developing teams in an organization worked in an agile manner with the requirements engineering, and some did not. To do this I performed a case study where I collected data through questionnaires and interviews from both developers and people from the business side. The results showed that the reasons for these differences were multiple. Communication and flexibility, and knowledge and understanding for different perspectives were the positive factors. The themes that hindered an agile way of working were, among others, unclear roles, lack of direction, too much reliance on methods and processes, discrepancy between business and IT, prioritizing issues, management plans, attitudes and IT architecture.

APA, Harvard, Vancouver, ISO, and other styles

18

Ghahestani, Shervin, and Pauline Korssell. "Agil transformation för produktutveckling i mjukvarubranschen : Ett arbete om upplevda utmaningar och fördelar med agilt arbetssätt." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-290047.

Full text

Abstract:

Allt fler aktörer uppkommer på den redan konkurrenskraftiga marknaden vilket ställer höga krav på utveckling av nya innovativa produkter för företag inom mjukvarubranschen. Detta leder till att företag måste förändra sin struktur och sitt arbetssätt för att kunna anpassa sin produktutveckling efter kunderna och marknaden. Ett sätt för företag att kunna fortsätta vara konkurrenskraftiga och bemöta marknadens behov är att implementera agila arbetssätt. Syftet med detta arbete är att bidra till ökad kunskap kring hur produktutvecklingsprocessen för en agil transformation från beslut till implementation kan ske i mjukvarubranschen. Arbetet har undersökt tre frågeställningar relaterade till agil transformation i mjukvarubranschen. Inledningsvis genomfördes en litteraturstudie för att erhålla en ökad förståelse för produktutveckling i mjukvarubranschen och för det agila arbetssättet. Vidare utfördes en kvalitativ semistrukturerad intervjuundersökning med fyra respondenter från tre företag där samtliga arbetar med agila arbetssätt och produktutveckling inom mjukvarubranschen. Den kvalitativa studien undersökte vilka utmaningar och potentiella fördelar en agil transformation kan generera samt vad som kännetecknar en lyckad agil transformation. Utifrån resultatet av denna studie utformades ett antal kategorier som kan användas som riktlinjer för hur en organisation kan gå tillväga vid en agil transformation i mjukvarubranschen. Studien visar att en agil transformation är en komplex och tidskrävande process. Utmaningar med agil transformation innefattar att ett agilt arbetssätt ofta blir beroende av en nyckelperson, det kräver en hög samverkan och ökad förståelse för varandras arbetsuppgifter samt ett anpassningsbart tankesätt som är mottagligt för förändring. Däremot genererar den agila transformationen fördelar så som en ökad produktivitet och användarnöjdhet, minskat antal defekter och en kortare ledtid hos samtliga företag. För att lyckas med en agil transformation visar studien på att ett företags medarbetare bör vara mottagliga för förändring och att motivet till transformationen borde komma inifrån organisationen. Sammanfattningsvis resulterade den agila transformationen i en förbättrad mjukvaruutveckling.
A large number of businesses are emerging on the already competitive market which places high demands on the development of new innovative products for companies in the software industry. As a result, companies must change the structure of the organization and their methods. Due to this, they have to customize their product development in order to meet the requirements of the customers and the markets demand and maintain their competitiveness. One way for companies to stay competitive is by implementing agile working methodologies. This study aims to contribute with knowledge and investigate the processes of an agile transformation from decision-making to implementation in the software industry. The study has examined three problem statements related to the agile transformation in the software industry. Initially a literature review was performed to gain an insight into product development in the software industry and the agile working methodologies. Furthermore, a semi structured qualitative interview was conducted which involved four respondents from three companies that work with agile working methodologies and product development in the software industry. This qualitative study examined the challenges and possible opportunities that an agile transformation generates as well as the characteristics of a successful transformation. Based on the result of this study, several categories were chosen and treated as guidelines for how an organization in the software industry can approach the agile transformation and proceed with it successfully. The results of the study demonstrate that an agile transformation is a complex and time-consuming process. The many challenges involving the agile transformation includes that the agile working methodology often becomes dependent of a single key person, it also requires collaboration, an increased understanding of each other’s work as well as an adaptable mindset that is receptive towards change. However, the agile transformation enables advantages amongst all the companies such as an increased productivity and user satisfaction, decreased number of defects as well as a reduced leadtime. To succeed with an agile transformation, it is of importance that a company’s employees are receptive towards change and that the motive behind the transformation comes internally within the organization. In conclusion, the agile transformation improved and strengthened the companies’ software development.

APA, Harvard, Vancouver, ISO, and other styles

19

Agorelius, Malin, and Emma Ekström. "Inter-teamsamordning i skagila projekt : En fallstudie på Avanza Bank för att möta beroenden i projektprocessen." Thesis, Linköpings universitet, Projekt, innovationer och entreprenörskap, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-178058.

Full text

Abstract:

Användandet av agila metodiker har ökat under de senaste decennierna. Detta har lett till en uppskalning av agila metodiker då även stora organisationer vill uppnå fördelarna som kommer med det agila arbetssättet. Att skala upp agila metodiker, och använda dessa i storskaligt agila miljöer (författarnas koncept skagila miljöer, som återfinns i sektionen ’Begreppet ’skagil’'), kommer dock med flera nya organisatoriska utmaningar. En utmaning, som omnämns i både litteratur och i arbetets empiriska undersökning på företaget Avanza, är inter-teamsamordning i skagila miljöer. Avanza har identifierat problemen med beroenden mellan team i skagila mjukvaruutvecklingsprojekt. För att möta problemet med beroenden initierades det här arbetet med syftet att, utifrån Avanzas nuvarande projekt design, undersöka hur teamöverskridande arbete kan samordnas för att möta beroenden i projektprocessen. För att uppnå syftet genomfördes en fallstudie på Avanza innehållande intervjuer med tolv respondenter och observation av interna dokument. Den empiriska undersökningen bekräftade ursprungsproblematiken gällande inter-teamsamordning och bidrog även med information om företagets nuvarande projektdesign. Resultatet visade att projektorganisationen verkar som en hybrid organisation med starka, agila inslag. Dock visade sig Avanza uppleva sin projektdesignen som helt agil. Vidare ansågs projektets beroenden bidra till agilt slöseri, vilket påverkar både produktivitet och effektivitet negativt i mjukvaruutvecklingsprocessen. Fyra huvudområden av agilt slöseri identifierades vilka var väntan, rörelse, defekter och tilläggsprocesser. Genom att klustra ihop liknande slöseri framtogs tre problemområden kopplade till Avanzas projektprocess, nämligen ’viss frånvaro av proaktivt angreppssätt och planering’, ’viss frånvaro av forum för hantering av inter-teamberoenden’ och ’skillnader i implementering av agila metodiker och projektprioritering bland teamen’. För att möta problemen fastställdes sex åtgärder, nämligen implementering av en mer proaktiv projektledarroll, anammning av hybridkulturen, skapande av rollspecifika team, implementering av arrangerade forum för teamsynkronisering, kodifiering och utveckling av befintliga mekanismer och samordning samt skapande av ett gemensamt förhållningssätt till agila principer i projekt. Arbetets slutsatser är till viss del generaliserbara och skulle kunna adopteras av andra företag eller projektorganisationer som har liknande problem och projektdesign som Avanza. Dock krävs en viss ansträngning för att först identifiera vilken projektdesign intressentföretag har samt att identifiera projektrelaterat slöseri. Avanza är även verksamma inom tech-branschen där projektorganisationen verkar kring mjukvaruutveckling. Därför kan det antas att slutsatserna mer sannolikt, passar andra organisationer som jobbar med mjukvaruutveckling.
The usage of agile methodologies has rapidly increased over the last decades. This has led to an upscaling of agile methods since larger organizations want to gain the benefits of the agile way of working. However, this has not come without issues, and using agile at scale (authors’ concept scagile, in upcoming section ’Begreppet ’skagil”) has introduced new organizational challenges. One challenge that is mentioned both in literature and in the empirical findings at the case company, Avanza, is inter-team coordination in scagile environments. Today Avanza is struggling with dependencies between teams in scaled agile software projects. To address this issue this study was initiated with the purpose to, based on Avanza’s current project design, investigate how cross-team collaboration could be coordinated to face and overcome dependencies in the project process. To accomplish this a case study, containing interviews with twelve respondents and observation of internal documents, was made. The empirical findings confirmed the original issues related to inter-team coordination and also provided valuable information about the company’s project design. Regarding the project design the findings showed that the project organization is a hybrid organization with strong agile influences. However, the alleged perception of the project design was a fully agile organization. Further, the dependencies in the projects seem to cause agile waste, which has a negative influence on productivity and efficiancy in software projects. Four main areas of agile waste were detected, namely waiting, motion, defects and extra processes. By clustering similar waste, three main problem areas were detected, viz ’a certain absence of a proactive approach and planning’, ‘a certain absence of forums for handling inter-team dependencies’, and ‘differences between teams regarding the implementation and usage of agile principles, and project prioritization’. To face these issues, six measures were determined, namely implementation of a more proactive project management approach, embracing the hybrid culture, creating role specific teams, arranging forums for team synchronization, codifying and developing the current coordination mechanisms and deciding on a shared approach for project methodologies. The findings of this study is to some extent generalizable and could be adopted by other companies, or project organizations, that are struggling with the same problem areas and have the same project design as Avanza. However, some effort is required to first determine current project design and to identify project related waste. Further, the client company is operative in the fin-tech industry where the project organization orbits around software development. Therefore it can be assumed that the findings are more likely to fit another software organization.

APA, Harvard, Vancouver, ISO, and other styles

20

Swafford, Patricia M. "Theoretical development and empirical investigation of supply chain agility." Diss., Georgia Institute of Technology, 2003. http://hdl.handle.net/1853/29590.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Redding, Guy Matthew. "A preliminary formalism for variable coupling in agile systems." Queensland University of Technology, 2006. http://eprints.qut.edu.au/16243/.

Full text

Abstract:

It is generally the case that corporate information systems consist of heterogeneous software subsystems that interact using many various processes and protocols. Applications that execute within such subsystems tend to be designed in isolation with little or no thought given to the requirements for future interaction. To provide bridges between these heterogeneous subsystems, one-off "hacked" solutions are usually introduced which rely upon maintenance of the status quo for all aspects of the execution environment and are thus inherently "brittle". Such a situation is inappropriate for large-scale and highly decentralised system deployments. In order to make such systems more robust and exhibit scalable performance characteristics, it is preferable to construct them with the ability to react to changes in the environment that they operate within. This research seeks to provide a method of how to engender "agility" into system components to improve their ability to deal with unpredictable environments. Our approach is to view systems and components from an interactive perspective and provide a middleware mechanism that enables a "variable" degree of coupling between system components. To achieve this we introduce three high-level "dimensions" of coupling, namely mediation, adaptation and crystallisation. Each dimension is characterised by the location of behaviour required for interaction and patterns of behaviour movement. The coordination characteristics of these dimensions of coupling are specified to establish a separation of coordination and application functionalities in endogenous distributed systems. The outcomes of this research project are: a definition for the dimensions of coupling that have been identified, a protocol to perform transitions between dimensions and a preliminary framework for the development of more agile applications.

APA, Harvard, Vancouver, ISO, and other styles

22

Lotfi, M. "Disentangling resilience, agility and leanness : conceptual development and empirical analysis." Thesis, City University London, 2015. http://openaccess.city.ac.uk/8342/.

Full text

Abstract:

This PhD thesis extends the existing knowledge on resilience in the context of supply chain, specifically by: (1) disentangling resilience, leanness and agility and (2) investigating how resilience along with leanness and agility affects operational performance outcomes. At the first phase, a literature review of practices underlying Lean, Agile and Resilient (LAR) was done, classifying them to the areas of overlap and non-overlap between LAR as regards the practices. Of the many practices identified for each of LAR, there are some that underlie just one of these three while others underlie two of them and even all three. To establish the practitioner need for this research, a survey combined with a focus group of various companies was conducted in the Forum of 2011 at Procter & Gamble, Brussels’ office. The results confirm lack of clear distinction between practices that are part of lean, agile and resilience. Clarifying these concepts is crucial both from theoretical and practical aspects. Theoretically, when it comes to those practices which go under lean and agile, agile and resilience or even the three of LAR, when it comes to have them in statistical models researchers don’t know where exactly these practices should be categorized. Practically, unclear boundaries between these concepts can make implementation of respective practices potentially problematic or confusing for managers. At the second phase, the thesis aims at “disentangle resilience, leanness and agility”. The survey carried out was done online in Germany due to the country’s strong base in manufacturing. Through factor analysis, this part of the research approves the idea of literature that resilience has some practices that purely helps it, while it also has some practices that affect agility and resilience and agility, leanness and resilience. There are some differences in the boundaries of these categorizations between what literature mentions and what industrial managers believe in. At the third phase, the thesis aims to investigate “how resilience along with leanness and agility affects performance outcomes”. The aim is to empirically assess a set of hypotheses that follow not only from the literature, but also from the perceptions of practitioners about LAR resulted from phase two. The model is tested on a sample of Automotive Parts Suppliers (APS) in Iran as the largest automotive industry in the Middle East and 12th in the world, and specifically as an appropriate choice for a resilient-needed environment due to sanctions and volatility of the currency. A survey was used to obtain information and a structural equation model to analyse the data. The model quantitatively explains that while leanness is independent form resilience, agility brings about resilience. On the other hand, the model tests the relations of leanness and resilience on flexibility, delivery, cost and time to recovery performance outcomes. The results show that higher level of resilience will lead to better delivery performance, better cost performance (i.e. helps cost reduction) and better time to recovery performance (i.e. helps time to recovery reduction). The results also show that its effect on flexibility performance is not significant. Regarding leanness, the results confirm that lean positively affect delivery and flexibility performance. In addition, higher level of leanness will lead to better cost performance (i.e. helps cost reduction). The results also reject the hypothesis stating that higher level of leanness will lead to worse recovery performance, inferring that higher level of leanness leads to better time to recovery performance (i.e. helps time to recovery reduction). Finally, there are different theoretical and managerial implications. Theoretically, this research disentangles resilience, agility and leanness. Then, it presents a model that resilience; leanness and agility are modelled not separately but besides each other and quantitatively it investigates how resilience along with leanness and agility affects performance outcomes. From managerial point of view, a need to understand what measures of the three concepts of LAR are related to each area between the three concepts has been answered so managers can prioritize their efforts and seek to balance their efforts across LAR. Overall, the conceptual model that stems from the SEM model gives a useful starting point for supply chain researchers regarding the three approaches in the supply chains.

APA, Harvard, Vancouver, ISO, and other styles

23

Åslin, Erik. "“The development of a new reactive agility test for soccer”." Thesis, Mittuniversitetet, Avdelningen för hälsovetenskap, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-35705.

Full text

Abstract:

Fotboll är en intermittent sport med både offensiva och defensiva aktioner som kräver ett flertal höghastighetsrörelser (sprint, vändningar) som respons till yttre stimuli vilket betonar betydelsen av att träna och testa agility (kvickhet). Syfte med denna studie var att a) konstruera ett nytt fotbollspecifikt reaktivt agility-test, b) utvärdera reliabiliteten och validiteten av de nya testerna och c) undersöka eventuellt samband mellan fysiska egenskaper (snabbhet, effektutveckling/explosivitet, styrka) och snabbhetstest med riktningsförändringar (CODS) och förmåga till reaktiv agility (RA). Tjugo unga manliga fotbollsspelare (ålder: 17,0 ± 0,9 år; kroppslängd: 1,81 ± 0,03 m; kroppsvikt: 70,0 ± 7,4 kg; kroppsfett 11,3 ± 2,0 %) delades upp i två grupper (10 spelare per grupp) baserat på ålder och fotbollsprestation (U17 & U19). Reliabilitetsdata visade hög tillförlitlighet för de båda CODS och RA-testerna (ICC-koefficienter 0,92 och 0,70-0,88). Within-subject variabiliteten hade en variationsvidd emellan 3,6–5,8 %. Ett moderat samband mellan CODS och RA-protokollen indikerar på en låg samhörighet. Regressionsanalyserna visade att de testade fysiska kvaliteterna inte kunde användas för att förutsäga resultaten i CODS och/eller de andra RA-testerna. Oberoende t-test visade att den högre rankade gruppen var bättre i både CODS och två andra RA-tester. Sammanfattningsvis, påvisade de nykonstruerande testerna god reliabilitet och validitet för test av unga fotbollsspelare. I tillägg, visade sig CODS och RA vara två oberoende kvaliteter och bör tränas och testat separat.

Godkännande datum: 2017-11-07

APA, Harvard, Vancouver, ISO, and other styles

24

Kerley, Warren Peter. "Agility in structured information systems development projects : a knowledge perspective." Thesis, University of Cambridge, 2009. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.611639.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Virchez, Azuara Alejandro. "A human resource perspective on the development of workforce agility." Thesis, Pepperdine University, 2016. http://pqdtopen.proquest.com/#viewpdf?dispub=10133132.

Full text

Abstract:

This study explored workforce agility from a human resource perspective. This included its main determinants, such as adaptability, proactivity, resiliency, business orientation, and self-awareness; the interventions through which it is developed, such as performance management processes, training, and coaching; and finally the main challenges that organizations face when developing it, such as cultural context and the lack of strategic clarity. The empirical analysis provided several insights on the development of workforce agility. Although limited to a small sample, the study provided evidence supporting the need for future research on the definition of the characteristics of an agile workforce, the definition of a competency model to support its development, the need to deepen the understanding of the mechanisms related to its development, and the main challenges faced by leaders in the implementation of an agile workforce.

APA, Harvard, Vancouver, ISO, and other styles

26

Jonsson, Carl, and Olle Bogren. "Ett nytt agilt värdegrundskoncept för system- och mjukvaruutveckling? : - En kvalitativ nulägesanalys hos ett IT-konsultbolag." Thesis, Linnéuniversitetet, Institutionen för informatik (IK), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-78168.

Full text

Abstract:

Den här kandidatuppsatsen har utförts genom en nulägesanalys på ett IT-inriktat konsultbolag. Studien identifierar det upplevda nuläget inom organisationen för att se om medarbetarnas upplevelser matchar de förhoppningar organisationen har med ett nytt infört värdegrundskoncept. Ett värdegrundskoncept med syfte att identifiera medarbetarnas inre motivation och främja den personliga utvecklingen samt hur det nya värdegrundskonceptet ämnar lösa de problem som finns inom system- och mjukvaruutveckling. Organisationen vill i sin tur att det ska leda till ett internt och externt värdeskapande och engagemang för alla parter, vilket kopplas till samhällsnytta, hållbarhet samt arbetsmiljö. Studien har genomförts med en induktiv ansats, där den kvalitativa undersökningen har samlat in data utifrån sex intervjuer, för att få en djupare förståelse av medarbetarnas egna tankar och åsikter. Den insamlade empirin har sedan jämförts, analyserat och diskuteras i förhållande till teori och tidigare forskning. Utifrån likheter och skillnader kunde vi sedan dra en slutsats till hur nuläget i organisationen är i förhållande till vad teorin säger. Resultatet av studien påvisar att respondenterna har en gemensam syn på att organisationen är innovativa och placerar medarbetarna i fokus. Inom organisationen finns det en samhörighet, lyhördhet och delaktighet, vilket skapar engagemang, motivation och personlig utveckling bland medarbetarna. Respondenterna ser det nya värdegrundskonceptet som ett bra komplement den agila metodiken som råder inom organisationen samt ett bra agilt verktyg. Organisationskulturen speglas av bra stämning, fräsch och inbjudande kontorsmiljö samt ärlighet mot kunden. Det framkom även en del meningsskiljaktigheter under undersökningen, exempelvis rörande osäkerhet över hur informationen tillhandahålls och hanteras.
This candidate assignment has been conducted through a zero-position analysis at an IT- based consulting company. The study identifies the current situation within the organization to see if the employees' experiences match the hopes the organization has with a new introduced values concepts. A values concepts aimed at identifying employees' internal motivation and promoting personal development as well as how the new values concepts aims to solve the problems in system and software development. The organization, in turn, wants it to lead to internal and external value creation and commitment for all parties, linked to community benefits, sustainability and work environment. The study has been conducted with an inductive approach, where the qualitative survey has collected data based on six interviews, to gain a deeper understanding of the employees' own thoughts and opinions. The collected empire has since been compared, analyzed and discussed in relation to theory and previous research. Based on similarities and differences, we could then draw a conclusion about how the present situation in the organization is in relation to what the theory says. The result of the study shows that respondents have a common view that the organization is innovative and places employees in focus. Within the organization there is a sense of togetherness, responsiveness and participation, which creates commitment, motivation and personal development among the employees. Respondents see the new values concepts as a good complement to the agile methodology within the organization as well as a good agile tool. The organizational culture is reflected by good atmosphere, fresh and inviting office environment and honesty towards the customer. There were also some differences of opinion during the investigation, such as uncertainty about how the information is provided and managed.

APA, Harvard, Vancouver, ISO, and other styles

27

Kurdi, Suparna. "Software development process and strategies used to expedite software development." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk2/ftp04/mq22136.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Kurdi, Suparna Carleton University Dissertation Management Studies. "Software development process and strategies used to expedite software development." Ottawa, 1997.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

29

Johansson, Katrin. "Agile Software Development." Thesis, Linköpings universitet, Institutionen för teknik och naturvetenskap, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-97920.

Full text

Abstract:

Systemutvecklingsföretag är på väg in i en turbulent period. Globaliseringen ger en total konkurrens som kräver snabba anpassningar. Detta ställer krav på reaktionssnabbhet. En framtid där vi slipper ogenomträngliga lösningar ligger nu inom räckhåll. Ett nytt synsätt har börjat ta form och konkurrerar nu ut den gamla, processorienterade synen på systemutveckling. Testdriven utveckling, refactoring och par-programmering är inslag i denna nya mera lättrörliga utvecklingsmetodiken. Detta synsätt går under namnet Agile Software Development. Den studie jag genomfört och som denna uppsats är resultatet av, syftar till att ta reda på hur systemutveckling enligt synsättet agile fungerar i verkligheten och vad det betyder för aktiva systemutvecklare. Resultatet av studien är baserad på en kvalitativ undersökning, i form av intervjuer, som gjorts med tretton systemutvecklare på olika företag runt om i Sverige. Resultatet visar att genom att utveckla mjukvara med en agilemetod, får man en snabbare utvecklingscykel med fokus på störts affärsnytta först. Det ger mer funktioner med högre kvalitet till lägre kostnad. Resultatet visar också att man har en flexiblare syn på utvecklingen och en attityd som välkomnar förändringar när helst dom dyker upp. Ett arbetssätt där förändringar är en del av planeringen.

APA, Harvard, Vancouver, ISO, and other styles

30

Hellström, Andreas, and Anatoly Chervyakov. "Global Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1687.

Full text

Abstract:

Global Software Development is an area that has been recently highlighted. Translation is usually an issue that people associate with adapting software for a specific country but it is much more than that. Through text representation and data formatting you can go deep into cultural aspects that affect the user interface and even the core functionality. In this thesis we will discuss just how these matters can affect development of global software. To carry out the investigation we analyzed current approaches and references and build up an extended methodology with suggestions to develop global software applications.
Utveckling av globala programvara är ett område som den senaste tiden har uppmärksammats. Översättning är vanligtvis en fråga som människor associerar med att anpassa programvaror för ett specifikt land men det är mycket mer än det. Man kan gå djupare in i kulturella aspekter som kan påverka användargränssnitt och även mjukvarans kärna. I den här uppsatsen diskuterar vi hur dessa aspekter kan påverka utveckling av global programvara. För att genomföra vårt arbete analyserades vi först befintliga metodologier och byggde upp en utökad metodologi med förslag på hur man kan utveckla global programvara.
0737 305407 0708 230374

APA, Harvard, Vancouver, ISO, and other styles

31

Leinonen, J. (Juho). "Evaluating software development effort estimation process in agile software development context." Master's thesis, University of Oulu, 2016. http://urn.fi/URN:NBN:fi:oulu-201605221862.

Full text

Abstract:

This thesis studied effort estimation in software development, focusing on task level estimation that is done in Scrum teams. The thesis was done at Nokia Networks and the motivation for this topic came from the poor estimation accuracy that has been found to be present in software development. The aim of this thesis was to provide an overview of what is the current state of the art in effort estimation, survey the current practices present in Scrum teams working on LTE L2 software component at Nokia Networks Oulu, and then present suggestions for improvement based on the findings. On the basis of the literature review, three main categories of effort estimation methods were found: expert estimation, algorithmic models and machine learning. Universally there did not seem to be a single best method, but instead the differences come from the context of use. Algorithmic models and machine learning require data sets, whereas expert estimation methods rely on previous experiences and intuition of the experts. While model based methods have received a lot of research attention, the industry has largely relied on expert estimation. The current state of effort estimation at Nokia Networks was studied by conducting a survey. This survey was built based on previous survey studies that were found by conducting a systematic literature review. The questions found in the previous studies were formulated into a questionnaire, which was then used to survey the current effort estimation practices present in the participating teams. 41 people out of 100 in the participating teams participated in the survey. Survey results showed that like much of the software industry, the teams in LTE L2 relied on expert estimation methods. Most respondents had encountered overruns in the last sprint and the most often provided reason was that testing related effort estimation was hard. Forgotten subtasks were encountered frequently and requirements were found to be both unclear and to change often. Very few had had any training on effort estimation. There were no common practices for effort data collection and as such, it was mostly not done. By analyzing the survey results and reflecting them on the previous research, five suggestions for improvements were found. These were training in effort estimation, improving the information that is used during effort estimation by collaborating with specification personnel, improving testing related effort estimation by splitting acceptance testing into their own tasks, collecting and using effort data, and using Planning Poker as an effort estimation method, as it fit the context of estimation present in the teams. The study shed light on how effort estimation is done in software industry. Another contribution was the improvement suggestions, which could potentially improve the situation in the teams that participated in the survey. A third contribution was the questionnaire built during this study, as it could potentially be used to survey the current state of effort estimation in also other contexts.

APA, Harvard, Vancouver, ISO, and other styles

32

Berglund, Sara. "Agility in Military Processes : Development of an Assessment Tool for Agile Command Teams." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-81548.

Full text

Abstract:

Agility is developing to a more and more central concept in the military domain and new war fare methods etc. is creating a greater demand on the Swedish Defence Agency to be more agile. The concept is very complex but could be described as the ability a command team has to discover threats and opportunities, and act with a response towards these to gain advantage in the situation. This report aims to develop an assessment tool for evaluating whether or not, or to which extent, a command team is agile. Discussions have been made in sessions with informants that somehow are connected to (working with or research about) agility in the Swedish Defence Agency to discuss the development of an assessment tool like this. Five sessions have been executed and after the first two respectively the last three, upgrades of the tool were made. The result of the study shows that it is not impossible to develop an assessment tool, but for a complex concept like agility, it is very hard. The conclusions drawn is that it might be possible to create a basic frame for a tool that further on can be shaped to fit the command team being evaluated.

APA, Harvard, Vancouver, ISO, and other styles

33

Kraska, Jenna M., Ann M. Kinser, Corey B. Whitted, Jon Keller, Michael W. Ramsey, G. Gregory Haff, William A. Sands, Margaret E. Stone, and Michael H. Stone. "Relationship of Isometric Peak Force and Rate of Force Development to Coaches Rank, Agility, and Agility Endurance Charactristics Among Female American Collegiate Football (Soccer) Players." Digital Commons @ East Tennessee State University, 2007. https://dc.etsu.edu/etsu-works/4097.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

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 text

Abstract:

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.

APA, Harvard, Vancouver, ISO, and other styles

35

Ke, Yuqing S. M. Massachusetts Institute of Technology. "Assessing various software development methodologies and matching software development methodologies with projects." Thesis, Massachusetts Institute of Technology, 2019. https://hdl.handle.net/1721.1/122438.

Full text

Abstract:

Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2019
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 157-158).
As the software industry evolves, various software development methodologies have become widely used in the industry. Most commonly used methodologies are Waterfall and Agile, along with less known alternatives, such as spiral and hybrid methodologies. When deciding on the methodologies, program managers tend to choose one based on the team preference or historical pattern. However, each software project is unique in its own way and has characteristics that are distinct from the previous projects the team has worked on. For each project, it is crucial to adopt a suitable methodology that help teams to produce the software that meets customer needs within schedule and budget constraints. Therefore, a practical question for every program manager is "How to find a suitable methodology for a specific project?" This thesis is aimed to help program managers answer this question.
We first explore how to evaluate each software development methodology based on the two-level decomposition of software development methodology, then analyze the project characteristics based on the situational inputs in three categories: scope, schedule and budget. Thereafter, the thesis proposes a framework to match software development methodology with a specific project. This thesis extends West's work in [1] by introducing a systems approach to assess a software project and a framework to determine the degree of compatibility between a methodology and a software project. The benefits of leveraging the systems approach are: ** The decomposition of methodologies highlights which elements in a methodology play key roles of providing the advantageous ilities over other methodologies. ** The decomposition of a project enables a program manager to evaluate the input elements of a project and gain a systems view on the project characteristics.
The framework allows program managers to compare several candidate methodologies and choose the most compatible one using the mismatch scores, weighted summations that indicate the incompatibilities between the candidate methodologies and the project based on the ilities ranking decided by the program managers. To demonstrate how to use this framework for a real world project, an example project is given. The detailed steps of calculating the mismatch scores between three methodologies and the project are shown. The proposed framework can be used as a guideline for program managers to find methodologies for different projects with the information gathered from project stakeholders. This framework has some limitations. A major one is that, since the framework is quantitative based, induvial experience is used to evaluate the elements of methodologies and factors of projects.
Further work can be done to improve the objectivity of the evaluation through the surveys of industrial experts and members of teams adopting this framework.
by Yuqing Ke.
S.M. in Engineering and Management
S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program

APA, Harvard, Vancouver, ISO, and other styles

36

Sheikh, Bilal Tahir. "Interdisciplinary Requirement Engineering for Hardware and Software Development - A Software Development Perspective." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-147886.

Full text

Abstract:

The software and hardware industries are growing day by day, which makes their development environments more complex. This situation has a huge impact on the companies which have interdisciplinary development environments. To handle this situation, a common platform is required which can be acted as a bridge between hardware and software development to ease their tasks in an organized way. The research questions of the thesis aim to get information about differences and similarities in requirements handling, and their integration in current and future prospectives. The future prospect of integration is considered as a focused area. Interviews were conducted to get feedback from four different companies having complex development environments.

APA, Harvard, Vancouver, ISO, and other styles

37

Konuralp, Zeynep. "Software Process Improvement In A Software Development Environment." Master's thesis, METU, 2007. http://etd.lib.metu.edu.tr/upload/12609059/index.pdf.

Full text

Abstract:

A software process improvement study is presented. The literature on software development processes and their improvement is reviewed. The current peer review process at Software Engineering Directorate of the X Company, Ankara, Tü
rkiye (XCOM) is studied and the static software development metrics based on a recent proposal have been evaluated. The static software metrics based improvement suggestions and the author&rsquo
s improvement suggestions discussed with the senior staff are compared. An improved peer review process is proposed. The static software development metrics have been evaluated on the improved process to see the impacts of the improvements. The improved process has been already implemented at XCOM and preliminary results have been obtained.

APA, Harvard, Vancouver, ISO, and other styles

38

Abbas, Noura. "Software quality and governance in agile software development." Thesis, University of Southampton, 2009. https://eprints.soton.ac.uk/158357/.

Full text

Abstract:

Looking at software engineering from a historical perspective, we can see how software development methodologies have evolved over the past 50 years. Using the right software development methodology with the right settings has always been a challenge. Therefore, there has always been a need for empirical evidence about what worked well and what did not, and what factors affect the different variables of the development process. Probably the most noticeable change to software development methodology in the last 15 years has been the introduction of the word “agile”. As any area matures, there is a need to understand its components and relations, as well as the need of empirical evidence about how well agile methods work in real life settings. In this thesis, we empirically investigate the impact of agile methods on different aspects of quality including product quality, process quality and stakeholders’ satisfaction as well as the different factors that affect these aspects. Quantitative and qualitative research methods were used for this research, including semi-structured interviews and surveys. Quality was studied in two projects that used agile software development. The empirical study showed that both projects were successful with multiple releases, and with improved product quality and stakeholders’ satisfaction. The data analysis produced a list of 13 refined grounded hypotheses out of which 5 were supported throughout the research. One project was studied in-depth by collecting quantitative data about the process used via a newly designed iteration monitor. The iteration monitor was used by the team over three iterations and it helped identify issues and trends within the team in order to improve the process in the following iterations. Data about other organisations collected via surveys was used to generalise the obtained results. A variety of statistical analysis techniques were applied and these suggested that when agile methods have a good impact on quality they also has a good impact on productivity and satisfaction, also when agile methods had good impact on the previous aspects they reduced cost. More importantly, the analysis clustered 58 agile practices into 15 factors including incremental and iterative development, agile quality assurance, and communication. These factors can be used as a guide for agile process improvement. The previous results raised questions about agile project governance, and to answer these questions the agile projects governance survey was conducted. This survey collected 129 responses, and its statistically significant results suggested that: retrospectives are more effective when applied properly as they had more impact when the whole team participated and comments were recorded, that organisation size has a negative relationship with success, and that good practices are related together as when a team does one aspect well, they do all aspects well. Finally, the research results supported the hypotheses: agile software development can produce good quality software, achieve stakeholders’ satisfaction, motivate teams, assures quick and effective response to stakeholder’s requests, and it goes in stages, matures, and improves over time.

APA, Harvard, Vancouver, ISO, and other styles

39

Sherwood, Patricia Ann. "Inspections : software development process for building defect free software applied in a small-scale software development environment /." Online version of thesis, 1990. http://hdl.handle.net/1850/10598.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Abdullahi, Abdille. "Component-based Software development." Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2335.

Full text

Abstract:

Component-based Software development is a promising way to improve quality, time to market and handle the increasing complexity of software management. However, The component-based development is still a process with many problems, it is not well de_ned either from theoretical or practical point of view. This thesis gives a brief overview of Component-Based Software development and starts with brief historical evolution followed by a general explanation of the method. A detailed discussion of the underlying principles like components, component framework and compent system architecture are then presented. Some real world component stadards such as .net framework, CORBA CCM and EJB are given in detail. Finally, simple fille-sharing-program based on Apache's Avalon framework and another one based on .net framework are developed as a case study.

APA, Harvard, Vancouver, ISO, and other styles

41

Nilsson, Jacob. "Development of organizer software." Thesis, University West, Department of Informatics and Mathematics, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-503.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Algan, Fatih Tuğlular Tuğkan. "Test driven software development/." [s.l.]: [s.n.], 2005. http://library.iyte.edu.tr/tezler/master/bilgisayaryazilimi/T000412.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Kortetjärvi, Fredrik, and Rohullah Khorami. "Software development of visualizationsystem." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-44789.

Full text

Abstract:

Today wireless technologies are increasing in the automation systems used in homes and buildings. More electrical devices are used in a house to save time, money, and energy because they are relatively inexpensive and easy to install; these devices even allow smart components such as mobile tablets and computer connectivity. To connect all these devices for data transmission purposes and easy access, the KNX is the best choice. The KNX standard is an open standard for home and building automation. KNX standard supports different communication media such as Twisted pairs, Power line, Radio Frequency, and tunnelling IP. KNX system is a bus system for building control, making all electrical and smart devices in a KNX system use the same transmission method and exchange telegrams via a shared bus network. To check and control all the electrical devices in a home or an apartment takes time; that is why there is a massive need for applications to make every room’s controlling process much easier and take a much shorter time. This project is about designing and implementing a visualization application for windows and .NET for managing and comparing input data with the actual data. This application is equipped with a KNX bus driver to communicate with hardware in a building. The practical part of the application is to take some raw data and then sort them in a specific way to minimize the time of controlling the process of the KNX devices in a building.

APA, Harvard, Vancouver, ISO, and other styles

44

Marques, João Miguel Resende. ""GWB" simulation software development." Master's thesis, Universidade de Aveiro, 2009. http://hdl.handle.net/10773/1768.

Full text

Abstract:

Mestrado em Engenharia e Gestão Industrial
Nas últimas décadas, a evolução da indústria alcançou uma extrema importância na nossa vida pessoal e também no comportamento empresarial. O conjunto de ferramentas existentes nos computadores representam um papel fundamental na comunicação, nas estratégias, nas decisões, nos sistemas de análise de processos das nossas empresas, entre outras. Os software são normalmente concebidos para permitir aos os seres humanos realizar tarefas para as quais o cérebro humano não é capaz, tais como: manipulação de grandes quantidades de informação, realização de cálculos complexos, e controlar simultâneamente muitos processos. Este projecto final foi desenvolvido exactamente sobre a disciplina de software. O presente documento mostra como uma empresa multinacional desenvolve internamente um novo software modular. Algumas técnicas serão investigadas e aplicadas a um problema real existente na empresa Robert Bosch-Bélgica, pertencente ao sector automóvel e principal responsável mundial pela produção de limpa pará-vidros. Aqui se encontrará uma sugestão para uma metodologia do ciclo de vida de um software e será explicado passo a passo todos os aspectos deste processo, desde a criação até ao desenvolvimento desta nova ferramenta de cálculo de apoio à decisão para o design. Esta metodologia foi aplicada à empresa permitindo assim a criação de um manual para o software de simulação chamado “GWB”. Mais precisamente, este projecto descreve a fase de testes, definido como a validação. Esta fase inclui um planeamento e execução de testes do software. Estes resultados foram analisados e comparados com as medições reais. Com base em conhecimentos anteriores, foi conseguido melhorar a precisão do software quer em parâmetros de produção quer em parâmetros de comportamento real dos limpa pará-brisas. Com a criação do manual e do melhoramento do software foram alcançados os dois objectivos principais envolvidos neste estágio. Este trabalho contribuiu significativamente para o desenvolvimento do software de simulação da Robert Bosch, no entanto, é sugerido um conjunto de acções futuras. Estas têm como objectivo ajudar no desenvolvimento do “GWB” para uma implementação adequada no processo de produção de limpa pará-brisas. ABSTRACT: In the last decades the evolution of software industry has reached an extreme importance in our personal daily life and also in the companies behavior. The existing sets of tools represent a vital role in our company’s communications, strategies, decisions supports, systems and process analysis, among others. Software is typically designed to enable humans to perform tasks which the human brain is not well capable, such as: handling large amounts of information, performing complex calculations, and controlling many simultaneous processes. This final project was developed based under the subject software. The present document shows how a multinational enterprise develops internally a new modulate software. Some techniques will be investigated and applied to a real life problem existing in the successful Robert Bosch-Belgium company at the automobile industry world responsible for the production of wiper blades. Here you will find a suggestion of a software life cycle methodology and an explanation step by step of all the aspects of this process from the creation to the development of a new calculation tool for design decision support. This methodology was applied to the company thus enabling to create a handbook for the simulation software called “GWB”. More precisely this project describes the testing phase, defined as validation. This phase contains the planning and execution of software tests. These results were analyzed and compared with real measurements. Based on previous knowledge, was able to improve the accuracy of the software either in production parameters or on parameters of actual behavior. With the creation of the manual and the software improvement two main objectives involved in this internship were accomplished. This work contributed significantly to the development of the Robert Bosch simulation software. However, it is suggested several future actions. To assist in the development of the “GWB” tool for a proper implementation in the wiper blade production process.

APA, Harvard, Vancouver, ISO, and other styles

45

Rais, Aziz. "Interface-Based Software Development." Doctoral thesis, Vysoká škola ekonomická v Praze, 2017. http://www.nusl.cz/ntk/nusl-264730.

Full text

Abstract:

Even though there are many software development and project management methodologies available, research and practice both show that IT software development projects still fail, and that the quality of software products does not always meet customers' expectations. There might be multiple causes for such failures, but some of these reasons can be seen to influence or create others. Therefore, the larger the project is, the higher its risk of failure, especially if the teams involved work remotely (distributed and outsourced). This increase in project complexity is considered the motivation for this paper. Similarly, there are other factors that can result in a project's failure and customers' dissatisfaction regarding software quality. All such factors identified by research conducted by organizations specializing in this area are analyzed in order to identify a common root of IT project failures. Once the root causes of these failures have been identified and analyzed, the goal of the Interface based software development methodology is to solve them. The solution offered by an Interface based software development methodology is to improve understanding of software requirements and to describe these requirements with interfaces in an object-oriented way. Interface based software development will support and drive development towards service-oriented architecture (SOA) and component-based development (CBD). The goal of interface based software development is to increase software testability and maintainability and to make it more easily feasible to execute various software development processes in parallel.

APA, Harvard, Vancouver, ISO, and other styles

46

Östlund, Joel, and Filip Eriksson. "Evaluation of Software License Management Frameworks for Grid Environments : The Four Ts for Agile Systems." Thesis, Linköpings universitet, Ekonomiska informationssystem, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-104419.

Full text

Abstract:

Business Agility could be the means to survive in a competitive environment of continuous andunanticipated change and to respond quickly to rapidly changing, fragmenting global markets that are catered by competitors. To leverage the potential benefits of Business Agility, many companies use Information Technology as a major force for augmenting their agility. The topic of increasing Business Agility through Information Technology has been pervasively studied in research papers. And in the context of this thesis, we will investigate research papers in order to develop an evaluation model for facilitating making informed decisions regarding agile Information Systems in computational Grid environments. The Information Systems in this thesis will focus on license management systems, which is an intricate but coherently integrated blend of many different modules compiled as a technical solution that enables software license management. We will use our evaluation model to compare license management frameworks, easily grasped as a draft for a license management system, for Grid environments and also underpin it with a case study on an in-use license management system in order to strengthen its business applicability. The research was conducted as a qualitative comparison and a case study, combining both research papers and a real business context in order to fulfill the goals and purposes of this thesis. The results of the analysis implies that most of the license management frameworks for Grid environments lacks various details needed for making a feasible implementation in a certain business context, whilst those that have been trialed in a real business situation fulfilled almost every aspect of our evaluation model. The conclusion drawn is that our evaluation model is a seemingly good start for making informed decisions when choosing or designing an agile license management system for Grid environments

APA, Harvard, Vancouver, ISO, and other styles

47

Burrell, Iris Shendell. "Examining the Effect of DevOps Adoption capability on organizational agility." Diss., Temple University Libraries, 2018. http://cdm16002.contentdm.oclc.org/cdm/ref/collection/p245801coll10/id/506178.

Full text

Abstract:

Business Administration/Management Information Systems
D.B.A.
The purpose of this research is to investigate the effect of DevOps adoption on organizational agility. The first chapter establishes through literature review and a pilot study, a theoretical definition of DevOps and identifies through survey data, the key DevOps adoption capabilities. The definition and key capabilities identified during the pilot study establishes the foundation through which a subsequent study is performed. The second chapter details an examination of the effects of DevOps adoption capability on organizational agility. Through capability theory, we propose that DevOps adoption capability positively affects organizational agility. We also propose that the capabilities of collaboration/communication, continuous monitoring, measurement and automation positively affect DevOps adoption capability and likewise; the capabilities of responsiveness, competency, flexibility, and quickness affect organizational agility capability. We test our model with survey data collected from 333 respondents and find that our hypotheses are supported and that DevOps adoption capability has a positive effect on organizational agility capability.
Temple University--Theses

APA, Harvard, Vancouver, ISO, and other styles

48

Vietsch, Rik, and Mol Jessica de. "New Product Development in the Mobile Device Industry : Agility as the 10th Success Factor." Thesis, Jönköping University, JIBS, Business Administration, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-12361.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Gallagher, Michael James. "Development of telemetry for the agility flight test of a radio controlled fighter model." Thesis, Monterey, California. Naval Postgraduate School, 1992. http://hdl.handle.net/10945/23639.

Full text

Abstract:

Approved for public release; distribution is unlimited
Advanced design tools, control devices, and supermaneuverability concepts provide innovative solutions to traditional aircraft design trade-offs. Emerging technologies enable improved agility throughout the performance envelope. Unmanned Air Vehicles provide an excellent platform for dynamic measurements and agility research. A 1/8-scaled F-16A ducted-fan radio-controlled aircraft was instrumented with a telemetry system to acquire angle of attack, sideslip angle, control surface deflection, throttle position, and airspeed data. A portable ground station was built to record and visually present real-time telemetry data. Flight tests will be conducted to acquire baseline high angle-of-attack performance measurements, and follow-on research will evaluate agility improvements with varied control configurations.

APA, Harvard, Vancouver, ISO, and other styles

50

Alajrami, Sami. "Software development in the post-PC era : towards software development as a service." Thesis, University of Newcastle upon Tyne, 2017. http://hdl.handle.net/10443/3756.

Full text

Abstract:

Engineering software systems is a complex task which involves various stakeholders and requires planning and management to succeed. As the role of software in our daily life is increasing, the complexity of software systems is increasing. Throughout the short history of software engineering as a discipline, the development practises and methods have rapidly evolved to seize opportunities enabled by new technologies (e.g., the Internet) and to overcome economical challenges (e.g., the need for cheaper and faster development). Today, we are witnessing the Post-PC era. An era which is characterised by mobility and services. An era which removes organisational and geographical boundaries. An era which changes the functionality of software systems and requires alternative methods for conceiving them. In this thesis, we envision to execute software development processes in the cloud. Software processes have a software production aspect and a management aspect. To the best of our knowledge, there are no academic nor industrial solutions supporting the entire software development process life-cycle(from both production and management aspects and its tool-chain execution in the cloud. Our vision is to use the cloud economies of scale and leverage Model-Driven Engineering (MDE) to integrate production and management aspects into the development process. Since software processes are seen as workflows, we investigate using existing Workflow Management Systems to execute software processes and we find that these systems are not suitable. Therefore, we propose a reference architecture for Software Development as a Service (SDaaS). The SDaaS reference architecture is the first proposal which fully supports development of complex software systems in the cloud. In addition to the reference architecture, we investigate three specific related challenges and propose novel solutions addressing them. These challenges are: Modelling & enacting cloud-based executable software processes. Executing software processes in the cloud can bring several benefits to software develop ment. In this thesis, we discuss the benefits and considerations of cloud-based software processes and introduce a modelling language for modelling such processes. We refer to this language as EXE-SPEM. It extends the Software and Systems Process Engineering (SPEM2.0) OMG standard to support creating cloudbased executable software process models. Since EXE-SPEM is a visual modelling language, we introduce an XML notation to represent EXE-SPEM models in a machine-readable format and provide mapping rules from EXE-SPEM to this notation. We demonstrate this approach by modelling an example software process using EXE-SPEM and mapping it to the XML notation. Software process models expressed in this XML format can then be enacted in the proposed SDaaS architecture. Cost-e cient scheduling of software processes execution in the cloud. Software process models are enacted in the SDaaS architecture as workflows. We refer to them sometimes as Software Workflows. Once we have executable software process models, we need to schedule them for execution. In a setting where multiple software workflows (and their activities) compete for shared computational resources (workflow engines), scheduling workflow execution becomes important. Workflow scheduling is an NP-hard problem which refers to the allocation of su cient resources (human or computational) to workflow activities. The schedule impacts the workflow makespan (execution time) and cost as well as the computational resources utilisation. The target of the scheduling is to reduce the process execution cost in the cloud without significantly a ecting the process makespan while satisfying the special requirements of each process activity (e.g., executing on a private cloud). We adapt three workflow scheduling algorithms to fit for SDaaS and propose a fourth one; the Proportional Adaptive Task Schedule. The algorithms are then evaluated through simulation. The simulation results show that the our proposed algorithm saves between 19.74% and 45.78% of the execution cost, provides best resource (VM) utilisation and provides the second best makespan compared to the other presented algorithms. Evaluating the SDaaS architecture using a case study from the safety-critical systems domain. To evaluate the proposed SDaaS reference architecture, we instantiate a proof-of-concept implementation of the architecture. This imple mentation is then used to enact safety-critical processes as a case study. Engineering safety-critical systems is a complex task which involves multiple stakeholders. It requires shared and scalable computation to systematically involve geographically distributed teams. In this case study, we use EXE-SPEM to model a portion of a process (namely; the Preliminary System Safety Assessment - PSSA) adapted from the ARP4761 [2] aerospace standard. Then, we enact this process model in the proof-of-concept SDaaS implementation. By using the SDaaS architecture, we demonstrate the feasibility of our approach and its applicability to di erent domains and to customised processes. We also demonstrate the capability of EXE-SPEM to model cloud-based executable processes. Furthermore, we demonstrate the added value of the process models and the process execution provenance data recorded by the SDaaS architecture. This data is used to automate the generation of safety cases argument fragments. Thus, reducing the development cost and time. Finally, the case study shows that we can integrate some existing tools and create new ones as activities used in process models. The proposed SDaaS reference architecture (combined with its modelling, scheduling and enactment capabilities) brings the benefits of the cloud to software development. It can potentially save software production cost and provide an accessible platform that supports collaborating teams (potentially across di erent locations). The executable process models support unified interpretation and execution of processes across team(s) members. In addition, the use of models provide managers with global awareness and can be utilised for quality assurance and process metrics analysis and improvement. We see the contributions provided in this thesis as a first step towards an alternative development method that uses the benefits of cloud and Model-Driven Engineering to overcome existing challenges and open new opportunities. However, there are several challenges that are outside the scope of this study which need to be addressed to allow full support of the SDaaS vision (e.g., supporting interactive workflows). The solutions provided in this thesis address only part of a bigger vision. There is also a need for empirical and usability studies to study the impact of the SDaaS architecture on both the produced products (in terms of quality, cost, time, etc.) and the participating stakeholders.

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic 'Agility in Software Development'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles