Zugl.: Bamberg, Universiẗat, Diss., 2007.

Thesis--Auburn University, 2009. / Abstract. Vita. Includes bibliographical references (p. 73-75).

Thesis (MSc(Computer Science))--University of Pretoria, 2003. / Summary in English and Afrikaans. Includes bibliographical references.

Konstanz, Univ., Diss., 2009.

Les nouvelles technologies de l’information deviennent un moyen incontournable pour réaliser des transactions instantanées dont tirent profit certaines chaînes logistiques. De ce fait, de nouveaux moyens liés aux opérations d’approvisionnement se développent. Leur émergence est directement liée à l’environnement volatile où évoluent désormais de plus en plus de chaînes logistiques. Les opérations d’approvisionnement du type «e-Procurement» sont des exemples de ces nouvelles pratiques où les chaînes logistiques sont qualifiées d’agiles. L’objectif de cette thèse est d’aborder des problématiques d’approvisionnement où un décideur est confronté au problème de choix de fournisseurs ainsi que la quantité de produits commandée durant le temps. Ces systèmes évoluent dans un environnement changeant caractérisé par des variations asynchrones et répétitives des prix d’achat et de commande ainsi que des capacités des fournisseurs et où l’évolution de ces données est inconnue. L’exemple des systèmes d’achat sur Internet ainsi que les systèmes d’enchères inversées en ligne s’inscrivent parfaitement dans la problématique traitée ici. Dans ce cadre, les approches classiques d’optimisation peuvent s’avérer inadaptées pour ce problème. Les travaux récents sur l’optimisation dynamique peuvent répondre à ce type de questionnement mais n’ont pour l’instant pas été étudiées dans le contexte des chaînes logistiques. Nous proposons, dans cette thèse, une approche basée sur des algorithmes génétiques dynamiques que nous avons illustrée avec trois cas d’application dans le cadre de l’approvisionnement en ligne. / In a context of increased competition between enterprises, supply chains are struggling to respond to an increasingly volatile and complex environment. With technological advances, current practices to build efficient supply chains have changed. Indeed, the enthusiasms of companies with the use of internet have lead researchers to find adequate methods to cope with the dynamic nature of logistics networks. The purpose of this thesis is to address a dynamic procurement issue under asynchronous and repetitive variations over time. The supply chain considered is composed of two levels (buyer-suppliers) operating in highly agile environment. The questions facing the buyer is how many units of product should be purchased and from which supplier in response to variation in term of price and capacity. Because of this highly changing environment characterized by frequents changes in a short time, most of the classical optimization approaches seems inadequate to address these problems. Recently, dynamic optimization has been used successfully to deal with such problems. However, we have no knowledge of its application in a supply chain context. We propose a dynamic genetic approach which is applied to an e-procurement context in aim to optimize the procurement process during time.

A utilização de uma gestão de portfólio de projetos permite que as empresas possam se adaptar rapidamente frente as turbulências advindas do ambiente interno e externo e com isso, possam rearranjar os projetos para que estes estejam alinhados com estratégia da organização. Entretanto, o modelo tradicional de gerenciamento de portfólio possui procedimentos que não seguem necessariamente essa característica de agilidade e adaptação. Na maioria das vezes os procedimentos são pouco visíveis, extensos e poucas vezes são interativos ou divulgados por todos os níveis hierárquicos das organizações. Dessa maneira o propósito deste trabalho é a aplicação de práticas, métodos e ferramentas ágeis na gestão de portfólio de projetos. Para isto, foi realizada uma revisão sistemática da literatura, a análise crítica do modelo tradicional por 7 especialistas da área e desenvolvimento de um modelo com base na análise das respostas das entrevistas por três especialistas sendo 2 da área acadêmica e 1 profissional da área. Os principais resultados revelam, que a existe uma escassez de trabalhos referentes a utilização de ferramentas ágeis em gestão de portfólio de projetos e na percepção dos entrevistados, a aplicação de práticas, métodos e ferramentas ágeis atende o quesito de gestão visual, melhor interação entre as equipes de trabalho, democratização da informação relativa à tomada de decisão e ferramentas alinhadas com a proposição ágil. / The use of project portfolio management allows companies to adapt quickly to the turbulence arising from the internal and external environment and with that, can rearrange the projects so that they are aligned with the organization's strategy. However, the traditional portfolio management model has procedures that do not necessarily follow this characteristic of agility and adaptation. Most of the time the procedures are barely visible, extensive and are rarely interactive or disseminated by all hierarchical levels of organizations. In this way, the purpose of this work is the incorporation of agile practices, methods and tools in project portfolio management. For this, a systematic review of the literature, the critical analysis of the traditional model by 7 specialists of the area and the development of a model based on the analysis of the answers of the interviews by three specialists were carried out, being 2 of the academic area and 1 professional of the area. The main results show that there is a shortage of work related to the use of agile tools in project portfolio management and the perception of the interviewees, the incorporation of agile practices, methods and tools attends to the question of visual management, better interaction between work teams, democratization of decision-making information and tools aligned with the agile proposition.

A utilização de uma gestão de portfólio de projetos permite que as empresas possam se adaptar rapidamente frente as turbulências advindas do ambiente interno e externo e com isso, possam rearranjar os projetos para que estes estejam alinhados com estratégia da organização. Entretanto, o modelo tradicional de gerenciamento de portfólio possui procedimentos que não seguem necessariamente essa característica de agilidade e adaptação. Na maioria das vezes os procedimentos são pouco visíveis, extensos e poucas vezes são interativos ou divulgados por todos os níveis hierárquicos das organizações. Dessa maneira o propósito deste trabalho é a aplicação de práticas, métodos e ferramentas ágeis na gestão de portfólio de projetos. Para isto, foi realizada uma revisão sistemática da literatura, a análise crítica do modelo tradicional por 7 especialistas da área e desenvolvimento de um modelo com base na análise das respostas das entrevistas por três especialistas sendo 2 da área acadêmica e 1 profissional da área. Os principais resultados revelam, que a existe uma escassez de trabalhos referentes a utilização de ferramentas ágeis em gestão de portfólio de projetos e na percepção dos entrevistados, a aplicação de práticas, métodos e ferramentas ágeis atende o quesito de gestão visual, melhor interação entre as equipes de trabalho, democratização da informação relativa à tomada de decisão e ferramentas alinhadas com a proposição ágil. / The use of project portfolio management allows companies to adapt quickly to the turbulence arising from the internal and external environment and with that, can rearrange the projects so that they are aligned with the organization's strategy. However, the traditional portfolio management model has procedures that do not necessarily follow this characteristic of agility and adaptation. Most of the time the procedures are barely visible, extensive and are rarely interactive or disseminated by all hierarchical levels of organizations. In this way, the purpose of this work is the incorporation of agile practices, methods and tools in project portfolio management. For this, a systematic review of the literature, the critical analysis of the traditional model by 7 specialists of the area and the development of a model based on the analysis of the answers of the interviews by three specialists were carried out, being 2 of the academic area and 1 professional of the area. The main results show that there is a shortage of work related to the use of agile tools in project portfolio management and the perception of the interviewees, the incorporation of agile practices, methods and tools attends to the question of visual management, better interaction between work teams, democratization of decision-making information and tools aligned with the agile proposition.

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

Agile software development has gained significant importance the recent years. Software practitioners have recognized the importance of agile development due to the benefits offered. Therefore, agile software development has been identified as the replacement to traditional or plan driven style of development. There are different frameworks or methods, which follow agile principles, known as agile methodologies. SCRUM and XP are the most popular and widely used agile methods or framework. There are different types of agile methodologies, each containing a set of practices, which can be adapted and implemented in an organization. However, there is still a need for empirical studies to understand the factors like requirements/modifications, challenges and mitigation strategies/techniques, which can enable successful implementation of agile practices in software organizations. In this study, the primary objective is to provide a comprehensive model or framework to practitioners, which includes the list of important requirements/modifications, challenges and mitigation strategies/techniques while implementing agile, and also pertaining to adoption/implementation of individual agile practices specific to SCRUM and XP. This model also includes the categorization of the requirements/modifications and challenges into different levels of an organization, to which they mostly apply. This conceptual model or framework can aid the practitioners in understanding and implementing agile practices in a better way in their organizations. In this study, an industrial survey is conducted in order to identify the list of important requirements/modifications that are needed to implement agile, challenges faced during implementation, and mitigation strategies/techniques needed to address the challenges. Also, categorization of the identified lists into different levels of the organization is also performed using survey. A systematic literature review is performed in order to identify the primary lists of requirements/modifications, challenges and mitigation strategies/techniques, which are further validated and classified using survey. Also, systematic literature review is used to identify the list of requirements/modifications, challenges and mitigation strategies/techniques that are needed while implementing individual agile practices specific to SCRUM and XP. Based on the systematic literature review, 53 primary studies were identified which are relevant to the research area. Upon analyzing the primary studies, the list of requirements/modifications, challenges and solutions are identified for generic agile adoption/implementation and also pertaining to individual practices specific to SCRUM and XP. Thereupon, an industrial survey is conducted where, identified list of requirements/modifications, challenges and mitigation strategies/techniques are provided to the respondents. Respondents were asked to classify the obtained aspects based on the level of importance. Also, they were asked to categorize the obtained requirements/modifications and challenges into different levels of an organization. The survey has obtained 48 responses from different parts of the world. From the results of survey, requirements/modifications, challenges and mitigation strategies/techniques are classified based on the level of importance. Also, requirements/modifications and challenges are categorized into different levels of an organization. Using the obtained factors, a conceptual model or framework was constructed for practitioners that can enable them to understand and implement agile practices in their organizations in a better way. To conclude this research, a comprehensive model or framework was constructed using the final list of important requirements/modifications, challenges and mitigation strategies/techniques while implementing/adopting agile and also pertaining to the individual agile practices, and also based on the categorization of the requirements and challenges into levels of an organization, where they are applicable. The final list of identified lists of requirements/modifications; challenges and mitigation strategies/techniques pertaining to individual agile practices can help practitioners to understand the implementation criteria of agile practices in software organizations. It was observed from the results of survey that perception of literature and practitioners are different in terms of usage of agile practices, as some practices, which were given high focus in the literature, were not given equal priority by the respondents. Empirical findings also help to identify change in policies and procedures and change to open workspace as most important requirements/modifications, organizational resistance and lack of motivated programmers as most critical challenges and proper training and inclusion of experts as most used mitigation strategies/techniques. Moreover, it was concluded that there is also a need for further full-scale empirical works on identifying the factors that affect adoption of agile. Practitioners can identify the benefits from this research and researchers can extend this work to remaining agile methodologies. / Agile systemutveckling har fått stor betydelse de senaste åren. Programvaru utövare har insett vikten av agila utvecklings grund av de förmåner som erbjuds. Därför har agile mjukvaruutveckling identifierats som ersättare till traditionella eller planen driven stil av utveckling. Det finns olika ramar eller metoder, som följer agila principer, så kallade agila metoder. SCRUM och XP är de mest populära och mest använda agila metoder eller ramverk. Det finns olika typer av agila metoder, var och en innehåller en uppsättning metoder, som kan anpassas och genomföras i en organisation. Det finns dock fortfarande ett behov av empiriska studier för att förstå de faktorer som krav / modifieringar, utmaningar och begränsningsstrategier / tekniker, som kan göra det möjligt för ett framgångsrikt genomförande av agila metoder i mjukvaruorganisationer.  I denna studie, är det primära målet att ge en heltäckande modell eller ramverk för utövare, vilket inkluderar en lista över viktiga krav / modifieringar, utmaningar och begränsningsstrategier / tekniker samtidigt genomföra vig, och även avseende antagande / genomförande av enskilda agila metoder specifika SCRUM och XP. Denna modell innehåller även kategoriseringen av de krav / modifieringar och utmaningar i olika nivåer i en organisation, till vilken de oftast gäller. Denna konceptuella modell eller ramverk kan hjälpa utövarna att förstå och genomföra agila metoder på ett bättre sätt i sina organisationer. I denna studie är en industriell undersökning för att identifiera listan över viktiga krav / ändringar som behövs för att genomföra vig, utmaningar under genomförandet, och begränsnings strategier / tekniker som behövs för att ta itu med utmaningarna. Också, kategorisering av de identifierade listorna i olika nivåer i organisationen är också utföras med undersökningen. En systematisk litteraturöversikt görs för att identifiera de primära listor krav / modifieringar, utmaningar och begränsningsstrategier / tekniker, som är validerade längre och klassificerade med hjälp enkät. Dessutom är systematisk litteraturöversikt används för att identifiera en lista över krav / modifieringar, utmaningar och begränsningsstrategier / tekniker som behövs samtidigt genomföra enskilda agila metoder som är specifika för SCRUM och XP. / +918500053444

Under sent 1990-tal började utvecklare att bli mer och mer missnöjda med rådande arbetsformer i projekt. Utvecklarna upplevde att modeller som vattenfallsmodellen inte längre speglade verkligheten för utvecklingen. Detta missnöje resulterade i att en mängd nya arbetsmodeller uppstod och 2001 samlades de under Agile Manifesto. Agile lägger tyngdpunkten på individfokus, fungerande mjukvara, kundsamarbete och föränderlighet. Scrum är just nu ett av de mest populära ramverken inom agile.Tieto har använt sig av agile och då främst Scrum i sina projekt sedan tidigt 2000-tal och haft lyckat resultat. Projekten som använt Scrum har levererat i tid och haft nöjda kunder. Dock har Tieto inte utrett vilka konsekvenser Scrum får för ett projekt. Denna studies fokus låg på att undersöka konsekvenserna av att använda Scrum i ett projekt. Detta gjordes med hjälp av intervjuer, observationer och en enkät där arbetet för ett antal Scrum-projekt studerades. Resultatet jämfördes sedan med rådande litteratur inom ämnet samt studier från The Standish group, VersionOne och Yahoo!.Rapportens slutsats är att Scrum påverkar mer än bara arbetssättet och att dessa effekter måste betänkas. Många positiva konsekvenser av användandet av Scrum kunde ses men även ett antal risker upptäcktes. För ett lyckat Scrum-projekt behövs en delaktig produktägare, en engagerad ScrumMaster och ett team som tycker om att ta eget ansvar. / During the late 1990s, developers became more and more dissatisfied with the current way of working in the projects. Developers felt that models such as the waterfall model did not reflect the reality of how software development works in practice. This dissatisfaction led to the development of new models and in 2001 they gathered under the same name in the Agile Manifesto. Agile focuses on working software, customer collaboration and variability. Scrum is currently one of the most popular frameworks in agile.Tieto has implemented agile and particularly Scrum in their projects since early 2000 and have had success. The projects that used Scrum delivered on time and had satisfied customers. However Tieto has not investigated the impact Scrum has on projects. This study focus was on examining the consequences of using Scrum in a project. This was done through interviews, observations and a survey in which the work of a number of Scrum projects were studied. The result was then compared with the current literature in the subject, and studies by The Standish Group, VersionOne and Yahoo!.The report concludes that Scrum affects more than just the way of working and that these effects must be taken under consideration. Many positive consequences of the use of Scrum could be seen but also a number of risks were detected. For a successful Scrum project one needs an involved product owner, a committed ScrumMaster and a team that likes to take responsibility.