Spelling suggestions: "subject:"[een] AGILE METHODS"" "subject:"[enn] AGILE METHODS""
1 |
RiPLE-SC: na agile scoping process for software product linesMoraes, Marcela Balbino Santos de 31 January 2010 (has links)
Made available in DSpace on 2014-06-12T15:56:44Z (GMT). No. of bitstreams: 2
arquivo2982_1.pdf: 2135820 bytes, checksum: df75cf5b4604b648bc295b0acd5b0db0 (MD5)
license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5)
Previous issue date: 2010 / Fundação de Amparo à Ciência e Tecnologia do Estado de Pernambuco / As constantes mudanças e a busca por novos benefícios na indústria de software
possibilitam o surgimento de novas áreas de pesquisa. Neste contexto, uma
tendência que tem apresentado importantes benefícios é a área de
desenvolvimento ágil de linhas de produtos de software. Linhas de produtos de
software é uma importante estratégia de reuso para minimizar custos e tempo
de entrega das aplicações, além de maximizar a qualidade e a produtividade do
desenvolvimento de software. Entretanto, desenvolver linhas de produtos
requer esforços e custos iniciais para apresentar resultados significativos, uma
vez que envolve planejamento sistemático, gerenciamento de pontos comuns e
variáveis dos produtos e design flexível e detalhado, aspectos que aumentam
sua complexidade. Por outro lado, a abordagem ágil apresenta como foco o
código e tem seu desenvolvimento realizado de forma iterativa. Além disso, esta
metodologia encoraja práticas e valores como comunicação face a face,
pequenas iterações, planejamento e design simples e incremental. Comparando
linhas de produtos de software e métodos ágeis, diferentes aspectos são
identificados. No entanto, pesquisas recentes mostram similaridades entre elas,
como: aumento de qualidade e produtividade no desenvolvimento de software e
redução de custos e tempo de entrega das aplicações. Portanto, visando
diminuir custos e esforços iniciais necessários para adoção de uma linha de
produtos de software, este trabalho propõe um processo de escopo ágil para
linhas de produtos de software, unindo os benefícios das duas abordagens. O
processo proposto é avaliado através de um estudo de caso industrial
|
2 |
Using Agile Methods for Software Development in R&D ScenarioGuarino de Vasconcelos, Luis Eduardo, Kusumoto, André Yoshimi, Leite, Nelson Paiva Oliveira, Lopes, Cristina Moniz Araújo 10 1900 (has links)
ITC/USA 2015 Conference Proceedings / The Fifty-First Annual International Telemetering Conference and Technical Exhibition / October 26-29, 2015 / Bally's Hotel & Convention Center, Las Vegas, NV / Due to the quick change of business processes in organizations, software needs to adapt quickly to meet new requirements by implementing new business rules. In Research and Development (R&D) scenario, the research is highly non-linear and changes are inevitable. In this context, it is known that traditional methodologies (e.g. waterfall) may lead to the detection of failures late, increase the time and cost of development and maintenance of software. On the other hand, agile methodologies are based on Test- Driven Development (TDD), maintain the technical debt under control, maximize the Return on Investment and reduce the risks for customers and companies. In this paper, we show the use of Scrum and TDD in the development of an experimental tool that aims to make the calibration in real time of the rudder of a fighter aircraft. The preliminary results allowed to increase the coverage testing of the software and hence the quality of the tool.
|
3 |
Agila metoder i stora företag : Hinder och möjligheter under initiativfasenvid implementation av agila metoderVaarala, Robert, Svernell, Johan January 2014 (has links)
Som svar på ökade krav på IT-relaterade produkter har de så kallade agilautvecklingsmetoderna uppfunnits. Förespråkare för agila metoder hävdar att bättreresultat kan uppnås genom minskning av tydliga, strikta kravspecifikationer,dokumentation och planering inom projekt till förmån för ett större fokus på småsjälvorganiserande arbetsgrupper och ett iterativt utvecklingssätt. De värderingar och den praxis som är förknippade med agila metoder ter sig vara meranpassade för små företag , på grund av den tunga betoningen på små självständigagrupper och brist på formell styrning och kontrakt. Syftet med detta examensarbete harsin grund i den oppositionen. Vilka omständigheter uppstår när en avdelning på ett stortföretag vill omvandla sin projektmetodik till en agil? Specifikt utförs en fallstudie på enutvecklingsavdelning ett stort IT-företag med över 69 000 anställda världen över. I det studerade fallet visar resultaten att intresset för agila metoder är korrelerat mednärheten till mjukvaruutvecklingsprocessen . Mjukvaruutvecklarna i studien anser att detfinns stora problem med dagens utvecklingsprocess och fann bristen av flexibilitet ikravhantering samt begränsat kundengagemang oerhört frustrerande. Andragruppmedlemmar var mindre bekymrade. Genom att anamma företagets lednings samtkundens synsätt blev det klart att mer agila utvecklingsprocesser försvårar strategiskplanering av företags totala projektportföljer. Författarna föreslår att en agil transformation inom ett stort företag kräver starkaförespråkare inte bara från utvecklarlaget utan även från företagets affärssida samtkunden. Anammandet av agila metoder ställer stora krav på tillit i relationen mellanutvecklingsteam och ledning samt mellan utvecklingsteam och kund, eftersomsamarbetet till lägre grad bör styras av strikta kravspecifikationer som speglas i fastakontrakt.
|
4 |
Modelo híbrido de gestión de portafolio para pequeñas empresas / Hybrid Portfolio Management Model for Small EnterprisesFeijoo Pérez, Nataly Eliana 04 April 2020 (has links)
El objetivo del presente trabajo de investigación es proponer un modelo híbrido para la gestión de portafolio en pequeñas empresas, siguiendo buenas prácticas de enfoques adaptativos y predictivos. El modelo propuesto se basa en el supuesto de que cada organización ya tiene identificado recursos humanos con el compromiso, habilidades y experiencia necesarios para trabajar bajo una nueva gestión estratégica con métodos agiles.
El modelo adaptativo está basado en el Agile Practice Guide (Project Management Institute, 2017), el estándar para la gestión de portafolio (Project Management Institute, 2017) y la Business Case Essentials: A Guide to Structure and Content (Schmidt, 2003) que es una guía para la elaboración de casos de negocio. De estos, se han tomado conceptos, técnicas y herramientas que han permitido proponer un modelo sencillo de gestión de portafolio que pueda ser adaptado a pequeñas organizaciones.
Por último, es importante indicar que la propuesta del trabajo de investigación se elaboró teniendo como modelo una pequeña empresa de consumo masivo, llamada AFS Consumo EIRL, ubicada en Lima – Perú. Previo a iniciar con el diseño del modelo, se realizaron algunos análisis y diagnósticos, por medio de entrevistas a los miembros de la organización, para finalmente proponer el modelo descrito en el presente trabajo. / The objective of this work is to propose a Hybrid Portfolio Management Model in small enterprises, following adaptive and predictive approaches and applying the Standard for Portfolio Management. This model is based on the assumption that each organization has already identified human resources with the commitment, skills and experience necessary to work under a new strategic agile management.
The adaptive model is based on the Agile Practice Guide (Project Management Institute, 2017), The Standard for Portfolio Management (Project Management Institute, 2017) and the guide Business Case Essentials: A Guide to Structure and Content (Schmidt, 2003). This work takes concepts, techniques and tools from these three documents to propose a simple portfolio management model that can be adapted to any organization.
Finally, it is important to indicate that the research work proposal was prepared using as a model, a small mass consumption company called AFS Consumo EIRL, located in Lima - Peru. Before starting to design this model, some analyzes and diagnoses were carried out through interviews with the members of the organization to finally propose the model described in this work. / Trabajo de investigación
|
5 |
CRITICAL PERSONALITY TRAITS IN SUCCESSFUL PAIR PROGRAMMINGAtli, Gulgunes 28 June 2006 (has links)
No description available.
|
6 |
TOWARDS A REFLECTIVE-AGILE LEARNING MODEL AND METHOD IN THE CASE OF SMALL-SHOP SOFTWARE DEVELOPMENT: EVIDENCE FROM AN ACTION RESEARCH STUDYBabb, Jeffry 13 April 2009 (has links)
The ascension and use of agile and lightweight software development methods have challenged extant software design and development paradigms; this is especially notable in the case of small-team and small-shop software development. In this dissertation, a Reflective-Agile Learning Method and Methodology (RALMM) for small-shop software development, is proposed to enhance communication and learning in the use of agile methods. The purpose of the inquiry in this dissertation pertains to: the nature of the professional practice of small team software development; the implications of the epistemology of Reflective Practice has for the professional practice of small-team software development; and whether the introduction of Reflective Practice to an extant agile methodology improves process, productivity and professional confidence for a small development team. This dissertation uses Dialogical Action Research (Mårtensson and Lee 2004), or Dialogical AR, a qualitative and interpretive research approach, to iteratively develop and refine the Reflective-Agile Learning Model and Method (RALMM). The proposed model and method also considers Hazzan and Tomayko’s (2002, 2004, and 2005) synthesis of Schön’s (1983, 1987) Reflective Practice and Extreme Programming (XP). RALMM is shaped by Argyris and Schön’s theories of practice (1974) and Organizational Learning (1978, 1996) and Schön’s ancillary work on generative metaphor (1979) and frames (Schön et al. 1994). The RALMM artifact was developed in a Dialogical AR Partnership using Lee’s (2007) framework for synthesizing design science and action research. The development and use of RALMM facilitated theorizing on the role of Reflective Practice in the successful use of agile methods. To assist in interpretation and analysis, the data collected during Dialogical AR cycles are analyzed using Strauss and Corbin’s (1998) Grounded Theory as a mode of analysis to guide in the coding and analysis of qualitative evidence from the research. As a result of this research, RALMM improved the practitioners’ processes and productivity. Furthermore, RALMM helped to establish, formalize and reinforce a team learning system for the continued development of the practitioners’ professional repertoire. Additionally, the iterative development of RALMM provides a basis for theorizing on Reflective Practice as an epistemology, paradigm, metaphor and frame of reference for the professional practice of small-shop software development.
|
7 |
The Effects of Digitalization on Managing Project TeamsFeise, Philipp, Graf von Hatzfeldt Trachenberg, Paul Philipp Maria January 2019 (has links)
Background: In various industries, market power is concentrated on a few major companies, which makes competition increasingly challenging for small and medium-sized enterprises. Those SMEs are furthermore impacted by the characteristics of their industry and need to change constantly and adapt to maintain competitive in this challenging market environment. The IT sector is characterized by a high degree of digitalization, quickly changing customer needs, and short lifecycles. Thus, many IT firms apply agile working methods, increase working in teams, and use different digital tools and applications. In many cases, those adjustments also impact the organizational structure of the firm and require a change in management. Purpose: In the context of a medium-sized IT firm, this study aims to evaluate the effects of digitalization on management innovation in project teams. Method: To gain a deep understanding of the researched topic, we chose a qualitative interview-based study. We collected the data for this single-case study in semi-structured interviews and applied purposeful sampling (theory based). For the data analysis, we used content analysis (open code; grouping; categorization). Conclusion: We developed a framework describing the influence of digitalization on management innovation in six dimensions, which emerged in the study. Those dimensions are project teams, virtual teams, communication & collaboration, trust, technology, as well as leadership & management. Digitalization strongly influences management innovations in all six identified fields. Digitalization, management innovation, and the respective field are interdependent. In our case, we found that digitalization acts as an enabler or simplifier for management innovation in all six dimensions.
|
8 |
Qualidade de software no desenvolvimento com métodos ágeis / Software quality on agile developmentOliveira, Bruno Henrique 25 April 2014 (has links)
A Engenharia de Software é uma disciplina que tem entre seus objetivos melhorar a produtividade dos processos de desenvolvimento de software, assim como propiciar qualidade ao produto resultante desses processos. Para mensurar a qualidade dos produtos de software, foram criados modelos de qualidade, que recomendam métricas, processos e atividades que passaram a se tornar parte do dia-a-dia do desenvolvimento de projetos em empresas. Considerando outra perspectiva, a indústria de software tem adotado cada vez mais os métodos ágeis. Esses métodos foram desenvolvidos visando a entrega rápida do software, com ciclos curtos e adaptáveis de desenvolvimento, foco na comunicação direta e baixo volume de documentação. Considerando a importância do tema qualidade de software, e a baixa aderência dos modelos tradicionais de qualidade aos métodos ágeis, o objetivo deste projeto foi investigar o tema qualidade de software no contexto ágil, ou seja, estudar quais métricas de qualidade são empregadas nesse processo de desenvolvimento. Para isso foram realizados dois estudos empíricos, um estudo de caso e um survey, sobre atividades de garantia e controle de qualidade, métricas de qualidade de software, processos e ferramentas utilizadas no desenvolvimento de software. Os resultados obtidos guiaram a construção de uma ferramenta de apoio para avaliação da qualidade durante o desenvolvimento ágil de software. Os resultados dos estudos mostraram que a execução constante de atividades como revisão de código e refatoração, são fatores essenciais para garantia de qualidade nos métodos ágeis. Outro resultado encontrado foi o de que praticantes de métodos ágeis são entusiastas do processo de desenvolvimento utilizado. Eles conhecem o método e praticam com alta fidelidade os passos definidos pelo processo. É possível concluir que os métodos ágeis possuem diversas atividades como foco na garantia de qualidade de seu produto desde os estágios iniciais do desenvolvimento. A cultura ágil cria um ambiente propício para motivação e engajamento das equipes de desenvolvimento, fato que reflete positivamente na qualidade final dos produtos / One of the main objectives of Software Engineering is to improve the productivity of software development processes, as well as providing quality to the product resulting from such processes. Thus, quality models were defined to measure the software quality. Those models recommend metrics, processes and activities that became part of day-to-day on development companies. Considering another perspective, the software industry has increasingly adopted agile methods. These methods were developed considering rapid software delivery, with short and adaptable development cycles, focusing on direct communication and low volume of documentation. Considering the importance of software quality and the low compliance of agile methods to traditional quality models, this project aimed to investigate software quality in agile development environments, in other words, to research wich quality metrics are employed in these development processes. Considering this objective, two empirical studies were designed, a case study and a survey. These studies have explored themes like software quality control, software quality assurance, quality metrics, development process and development tools that are employed on software development. The results guided the construction of a tool to support the quality evaluation during the agile development. The studies results showed that the high frequency of activities such as code review and refactoring, are essential factors for assuring quality on projects using agile methods. Another result was found regarding developers behavior. Agile practitioners are enthusiasts of the development process they use. They have a high level of compliance to development process they use. It is possible to conclude that agile methods have several activities focused on the quality assurance of its own products since the initial stages of development. The agile culture creates a convenient environment that engages and motivates the development teams. This fact has a positive effect on the product quality
|
9 |
Scrum-DR: uma extensão do framework Scrum aderente ao CMMI-DEV utilizando técnicas de Design Rationale. / Scrum-DR: an extension of the scrum framework adherent to the capability maturity model using Design Rationale techniques.Sandra Kawamoto 08 November 2017 (has links)
Os métodos ágeis introduziram uma nova abordagem de desenvolvimento de software, enfatizando os indivíduos, o produto e a comunicação. Prometem alta satisfação do cliente, baixo índice de erros, tempo de desenvolvimento mais rápido e uma solução para a rápida mudança de requisitos. Por outro lado, modelos de qualidade de software, como o CMMI, prometem previsibilidade, estabilidade e segurança, melhorando a qualidade dos produtos e dos processos da empresa. O intuito desta pesquisa é unir estas duas abordagens na tentativa de aproveitar as vantagens de ambas. Como resultado, apresenta-se o framework Scrum-DR, uma extensão do Scrum, aderente às diretrizes do CMMI-DEV na categoria Suporte. O Scrum-DR possui características do desenvolvimento ágil de software e contempla a utilização de técnicas de Design Rationale, apresentando um modelo que soluciona uma importante questão nas metodologias ágeis. / Agile methods introduced a new approach to software development, emphasizing individuals, product, and communication. They promise high customer satisfaction, low error rates, faster development time and a solution for rapidly changing requirements. On the other hand, software quality models, such as CMMI, promise predictability, stability and security, improving the quality of the company\'s products and processes. The purpose of this research is to link these two approaches in an attempt to take advantage of both. As a result, the Scrum-DR framework, a Scrum extension, adhering to the CMMI-DEV guidelines in the Support category is presented. Scrum-DR has characteristics of agile software development and contemplates the use of Design Rationale techniques, presenting a model that solves an important issue in agile methodologies.
|
10 |
Three Studies of Problem Solving In Collaborative Software DevelopmentDomino, Madeline Ann 15 December 2004 (has links)
A potential solution to producing quality software in an acceptable time frame may be found by using the newer, innovative methods, such as collaborative software development. The purpose of this dissertation is to examine the individual developer characteristics, developmental settings, collaborative methods and the processes during development that impact collaborative programming performance and satisfaction outcomes.
Understanding individual differences in performance in the collaborative development setting is important, since it may help us understand how the collaborative setting may raise the lowest level of performance to much higher levels, as well as how to select individuals for collaborative development. Exploring the impact of the virtual setting on collaborative development processes is important as it may help us improve performance outcomes in different work settings. Investigating how adaptations of pair programming impact collaborative processes may assist in implementing changes to the method that enhance quality and individual satisfaction.
A multi-phase methodology is used, consisting of an intensive process study (Study 1) and two laboratory experiments (Studies 2 and 3). Study 1 illustrates that collaborative programming (pair programming) outcomes are moderated by both individual developer differences and the processes used during development. While cognitive ability and years of IT experience are important factors in performance, the impacts of conflict and the faithful appropriation of the method are highlighted. Distributed cognition is used as a theoretical foundation for explaining higher performance.
Study 2 findings suggest that while collaborative programming is possible in a virtual setting, performance is negatively impacted. Face-to-face programmers have significantly higher levels of task performance, as well as satisfaction with the method, when compared to virtual programmers.
Study 3 results suggests that the use of structured problem solving (preparing test cases before writing code) may be a key factor in producing higher quality code, while collaboration may be indusive to higher levels of developer satisfaction.By understanding how, why and when collaborative programming techniques produce better performance outcomes and what factors contribute to that success, we add to the body of knowledge on methodologies in the MIS domain.
|
Page generated in 0.047 seconds