• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 22
  • 15
  • 15
  • 14
  • 2
  • 1
  • Tagged with
  • 71
  • 71
  • 30
  • 30
  • 24
  • 23
  • 21
  • 21
  • 16
  • 16
  • 16
  • 15
  • 13
  • 11
  • 9
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
1

Tool support for social risk mitigation in agile projects

Licorish, Sherlock Anthony Unknown Date (has links)
Software engineering techniques have been employed for many years to guide software product creation. In the last decade the appropriateness of many techniques has been questioned, given unacceptably high rates of software project failure. In light of this, there have emerged a new set of agile software development methodologies aimed at reducing software projects risks, on the basis that this will improve the likelihood of achieving software project success. Recent studies show that agile methods have been gaining increasing industry attention. However, while the practices recommended by agile methodologies are said to reduce risks, there exists little evidence to verify this position. In addition, it is posited that the very processes recommended by agile methodologies may themselves introduce other risks. Consequently, this study addresses the risks inherent in the human collaboration practices that are central to agile methods. An analysis of the risk management literature reveals that personality conflicts and customer-developer disagreements are social risks that occur through human collaboration. These risks negatively affect team cohesion and software project success. Personality conflicts are said to be mostly influenced through poor team formation, whereas customer-developer disagreements are induced through excessive customer direct interaction. However, these risks are not adequately addressed by standard risk management theories. Furthermore, an evaluation reveals that these risks are also not considered by existing software tools.This study therefore designs and implements a web-based solution to lessen the social risks that may arise in agile projects. The Agile Social-Risk Mitigation Tool (ASRMT) offers support for personnel capability assessment and management and for remote customer feature management, extending the customer's access through an interface. Using software engineering experts to evaluate ASRMT, the tool is shown to effectively address social risk management theories, and is considered likely to assist agile developers in their handling of social risks. In addition, above and beyond its intended purpose, ASRMT is also likely to assist agile teams with general project management. The findings of the ASRMT user evaluations demonstrate sufficient proof of concept to suggest that such a tool could have value in live software projects.
2

Tool support for social risk mitigation in agile projects

Licorish, Sherlock Anthony Unknown Date (has links)
Software engineering techniques have been employed for many years to guide software product creation. In the last decade the appropriateness of many techniques has been questioned, given unacceptably high rates of software project failure. In light of this, there have emerged a new set of agile software development methodologies aimed at reducing software projects risks, on the basis that this will improve the likelihood of achieving software project success. Recent studies show that agile methods have been gaining increasing industry attention. However, while the practices recommended by agile methodologies are said to reduce risks, there exists little evidence to verify this position. In addition, it is posited that the very processes recommended by agile methodologies may themselves introduce other risks. Consequently, this study addresses the risks inherent in the human collaboration practices that are central to agile methods. An analysis of the risk management literature reveals that personality conflicts and customer-developer disagreements are social risks that occur through human collaboration. These risks negatively affect team cohesion and software project success. Personality conflicts are said to be mostly influenced through poor team formation, whereas customer-developer disagreements are induced through excessive customer direct interaction. However, these risks are not adequately addressed by standard risk management theories. Furthermore, an evaluation reveals that these risks are also not considered by existing software tools.This study therefore designs and implements a web-based solution to lessen the social risks that may arise in agile projects. The Agile Social-Risk Mitigation Tool (ASRMT) offers support for personnel capability assessment and management and for remote customer feature management, extending the customer's access through an interface. Using software engineering experts to evaluate ASRMT, the tool is shown to effectively address social risk management theories, and is considered likely to assist agile developers in their handling of social risks. In addition, above and beyond its intended purpose, ASRMT is also likely to assist agile teams with general project management. The findings of the ASRMT user evaluations demonstrate sufficient proof of concept to suggest that such a tool could have value in live software projects.
3

Vybrané agilní metodiky v praktických aplikacích / The chosen agile methodologies in practical use

Růt, Václav January 2015 (has links)
The thesis focuses on concrete application of the selected agile methodologies on the designed new software development methodology in the company Firma 2.0. The theoretical section briefly characterizes agile methodologies in general and then focuses on their representative sample, and thus Scrum, Kanban, SAFe and LeSS and the DevOps movement, which build a framework for the practical section. The selected components, which are used in the second part, are emphasized. Importantly, all of the methodologies are based on the agile manifesto and thanks to that are mutually combinable. The practical section introduces the company Firmy 2.0 together with its existing software development methodology, which is currently insufficient. The shortages are described as bottlenecks of the methodology itself as well as issues of process management of the company. The newly designed software methodology eliminates those drawbacks and integrates new elements and terminology in order to better correspond with the current processes in the company. The main contribution of the thesis is seen in the new design of software development methodology for a small company, which can also be potentially used outside of the company Firma 2.0, associated with a sound theoretical background.
4

Aplikace agilní metodiky Scrum a využití podpůrných softwarových nástrojů / Utilization of Agile Scrum and Usage of Support Software Tools

Tošner, Jiří January 2015 (has links)
Agile software development methodologies are very popular for their efficiency and flexibility. This thesis focuses on agile software development methodology called Scrum. Basic description and comparison of traditional and agile methodologies is mentioned at first. Attention is paid to methodology Scrum which is shown on an example of usage by a specific company. It is convenient to use some software tool for organization of Scrum methodology. Therefore, an overview of the most common tools and basic comparison of software tools for organizing this methodology is presented. Conclusion of this thesis is recommendation for improvements for the investigated team, based on issues which were identified.
5

Modelo de Producción para la Reducción de Tiempos de Entrega de Pedido en una empresa metalmecánica de Lima Metropolitana basado en Six Sigma / Production Model for the Reduction of Order Delivery Time in a Peruvian Metalworking Company Based on the Six Sigma DMAIC Methodology

Espinoza Cuadros, Anelit Nelva, Criollo Marcavillaca , Miriam Rosalinda 04 April 2020 (has links)
El principal problema que enfrenta un fabricante de tableros eléctricos es la alta tasa de demora en entrega de pedidos. El factor predominante que han dado lugar al retraso de la entrega de pedidos es el cuello de botella que se genera en el proceso productivo. Para resolver este problema, se desarrolló una propuesta innovadora utilizando la metodología DMAIC (Definir, Medir, Analizar, Mejorar y Controlar), la cual esta orientada a la mejora de procesos utilizada por Six Sigma [1] [2]. Para respaldar este análisis, se realizará una simulación, buscando una reducción considerable del cuello de botella y, por consecuencia, el aumento de productividad, mejorando el tiempo de entrega de pedidos. Al implementar la metodología DMAIC Six Sigma, se mejorará el tiempo de entrega de pedidos a 96%, mejorando así la calidad del proceso de producción y generando beneficios económicos. / The main problem faced by a manufacturer of electrical panels is the high rate of late delivery of orders. The predominant factor that has led to the delay in order delivery is the bottleneck generated in the production process. To solve this problem, an innovative proposal was developed using the DMAIC (Define, Measure, Analyze, Improve and Control) methodology, which is oriented to the process improvement used by Six Sigma [1] [2]. To support this analysis, a simulation will be carried out, looking for a considerable reduction of the bottleneck and, consequently, the increase of productivity, improving the time of delivery of orders. By implementing the DMAIC Six Sigma methodology, the order delivery time will be improved to 96%, thus improving the quality of the production process and generating economic benefits. / Trabajo de investigación
6

Analýza projektu implementace penzijní reformy / Analysis of the Pension Reform Project Implementation

Kupka, Jaromír January 2012 (has links)
This thesis is devoted to the theme of a new information system of the pension company. The first part is the input into the subject. It defines the scope of the thesis and defines the objectives that the author wants to achieve in the thesis. The second part is focused on the analysis of project methodologies and selection of an appropriate methodology for this type of project. The third part of the thesis is focused on the analysis of agile methodologies and selection of the appropriate methodology for a particular project. The fourth part is devoted to the analysis of Scrum methodology. Conclusions of this part are the arguments for deploying agile approach for a specific project. In the fifth part of the thesis the author returns to mistakes at the level of project management, which negatively affected the time plan and financial plan of the project. The final part summarizes the results of analyzes, summarizes the objectives and identifies the expected benefits of the thesis.
7

Estrategia híbrida basada en código y modelos para el desarrollo ágil de aplicaciones web

Jimbo Pinos, Karina 29 May 2015 (has links)
La metodología Mockup-Driven Development (MockupDD) propone utilizar prototipos de interfaz de usuario (usualmente conocidos como Mockups) como artefactos principales de elicitación de requerimientos y modelado en el contexto de un proceso Model-Driven Web Engineering (MDWE). Su proceso se basa en construir estos prototipos de manera obligatoria, temprana y de su posterior anotación al utilizar un microlenguaje de tags. MockupDD propone un enfoque ágil para MDWE, sin embargo, tratar conceptos del lenguaje para implementar requerimientos específicos sigue presentado las mismas dificultades que en los procesos MDWE convencionales: es necesario agregar nuevos elementos al metamodelo y modificar generadores de código. En esta tesis se presenta una estrategia (extensión de MockupDD) que propone agregar características al paradigma MDWE ortodoxo, en donde, cada concepto del lenguaje en lugar de ser inmutable será ejecutable por sí mismo, convirtiéndose en prototipos de implementaciones por defecto, que pueden modificarse según se requiera al utilizar codificación manual – a costas de sacrificar parte o la totalidad de su abstracción. Esto provocará cambios importantes en comparación con la versión de MockupDD original, al plantear una nueva arquitectura de semántica de tags y un alejamiento del paradigma MDWE puro en pos de mejorar la agilidad y la adaptabilidad. / The Mockup - Driven Development (MockupDD) methodology proposes using user interface prototypes (usually known as Mockups) as key artifacts of requirements elicitation and modeling in the context of Model-Driven Web Engineering (MDWE ) process. Its process is based on building these prototypes early and their subsequent annotation using a microlanguage of tags. MockupDD proposes an agile approach for MDWE. However, in this methodology extending language concepts presents the same difficulties as in conventional MDWE processes: you need to add new elements to the metamodel and modify code generators. In this thesis proposes a strategy (an extension to MockupDD) that adds features to the orthodox MDWE paradigm. In this work, each concept of the language it is executable by itself instead of being immutable, thus becoming a prototype of a default implementation that can be modified as required using manual coding - at the expense of sacrificing some or all of its abstraction. This will cause major changes compared to the original version MockupDD, proposing a new architecture to specify tags semantics and a departure from the pure MDWE paradigm, towards improving agility and adaptability.
8

Um modelo de gerenciamento de projetos baseado nas metodologias ágeis de desenvolvimento de software e nos princípios da produção enxuta. / A project management model based on agile software development methodologies and lean production principles.

Franco, Eduardo Ferreira 22 May 2007 (has links)
Procurando obter ganhos sustentáveis de produtividade e qualidade no desenvolvimento de software, diversos modelos, formas de organização do trabalho e abordagens inovadoras foram desenvolvidos para auxiliar os gerentes de projeto. O presente trabalho propõe um modelo de gerenciamento de projetos, baseado nas metodologias ágeis de desenvolvimento de software (Extreme Programming e o Scrum), e nos princípios e valores do pensamento enxuto, originado na manufatura automobilística japonesa. Após a proposição do modelo, ele é aplicado em um estudo de caso, avaliando os resultados obtidos na combinação entre as metodologias ágeis e nos princípios e valores da produção enxuta. Em seguida, este modelo é analisado qualitativamente com o intuito de determinar suas vantagens de utilização e seu escopo de aplicação. Para tanto, recorreu-se a uma avaliação do modelo proposto e o tradicional modelo cascata, ainda amplamente adotado no setor de software, e mapeando como este modelo contorna os problemas apontados na literatura, advindos da utilização do modelo cascata. / Looking for sustainable gains in productivity and quality in the development of software, several models, forms of work organization and innovative approaches were developed to support software development managers. The present work proposes a model of project management, based on agile software development methodologies (Extreme Programming and Scrum) and on lean principles and values borrowed from the Japanese automobile manufacturing. After describing the proposed model, it is applied in a case study, describing the results of combining the agile software development methodologies with the lean production principles and values. After this, the model is qualitatively analyzed to determine its advantages and its scope of application. For this, the proposed model is evaluated with the traditional waterfall model - until now widely adopted in the software industry - and mapping how it addresses problems, cited in the literature, derived from the use of the waterfall model.
9

Lean Software Development and Agile Methodologies for a small Software development organization

Moratilla Temprado, Enrique, Ruz Bendito, Enrique January 2010 (has links)
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.
10

Um modelo de gerenciamento de projetos baseado nas metodologias ágeis de desenvolvimento de software e nos princípios da produção enxuta. / A project management model based on agile software development methodologies and lean production principles.

Eduardo Ferreira Franco 22 May 2007 (has links)
Procurando obter ganhos sustentáveis de produtividade e qualidade no desenvolvimento de software, diversos modelos, formas de organização do trabalho e abordagens inovadoras foram desenvolvidos para auxiliar os gerentes de projeto. O presente trabalho propõe um modelo de gerenciamento de projetos, baseado nas metodologias ágeis de desenvolvimento de software (Extreme Programming e o Scrum), e nos princípios e valores do pensamento enxuto, originado na manufatura automobilística japonesa. Após a proposição do modelo, ele é aplicado em um estudo de caso, avaliando os resultados obtidos na combinação entre as metodologias ágeis e nos princípios e valores da produção enxuta. Em seguida, este modelo é analisado qualitativamente com o intuito de determinar suas vantagens de utilização e seu escopo de aplicação. Para tanto, recorreu-se a uma avaliação do modelo proposto e o tradicional modelo cascata, ainda amplamente adotado no setor de software, e mapeando como este modelo contorna os problemas apontados na literatura, advindos da utilização do modelo cascata. / Looking for sustainable gains in productivity and quality in the development of software, several models, forms of work organization and innovative approaches were developed to support software development managers. The present work proposes a model of project management, based on agile software development methodologies (Extreme Programming and Scrum) and on lean principles and values borrowed from the Japanese automobile manufacturing. After describing the proposed model, it is applied in a case study, describing the results of combining the agile software development methodologies with the lean production principles and values. After this, the model is qualitatively analyzed to determine its advantages and its scope of application. For this, the proposed model is evaluated with the traditional waterfall model - until now widely adopted in the software industry - and mapping how it addresses problems, cited in the literature, derived from the use of the waterfall model.

Page generated in 0.0571 seconds