Publicación a texto completo no autorizada por el autor / Implementa un sistema de información que permite gestionar el registro de empresas que brindan el servicio de transporte de mercancías, gestionar el registro de los vehículos que están asociados a una empresa, controlar las autorizaciones de las empresas para ello se muestra todo el análisis y diseño de sistemas que se realiza para implementar el sistema de información. / Trabajo de suficiencia profesional

Epiroc Drilling Tools is a manufacturing company that produces tools for rock mining and excavation. The company adopted the principles and framework of Lean Product Development in their R&D department with few practices of an agile framework called Scrum. These agile practices are used in the pre-study phase or the knowledge value stream of their lean product development. Hence, this research is limited to the knowledge value stream within the R&D department. The use of agile project management in manufacturing industry is unique and majority of the agile frameworks are specifically designed to suit the needs of software development companies. Several theories like Scrum, Lean, Kanban and DSDM were studied by the researchers to scrutinize the current framework of the department. The challenges and the similarities of the currently used framework with several other agile frameworks and the companies are discussed. Several qualitative research methods were adopted to know the viewpoints of the working employees in the department which are compared with other companies like Volvo Cars, ABB, LShift, EnergySoftware and from another division of Epiroc called Rocktec Automation who faced some similar challenges while practicing agile project management. After further research on the theories and comparison of the process, roles of the working employees and documentations within the knowledge value stream, DSDM had more similarities with the currently used framework than Scrum. This allowed to recommend ways that can fill the missing gaps using practices of DSDM without altering the existing working procedure in the knowledge value stream. This ensures that the improvement in the knowledge value stream remains continuous. On the contrary, a brief discussion is included on whether there is a need to be agile for manufacturing industries or is it just a changing trend in the field of project management.

Submitted by Lucelia Lucena (lucelia.lucena@ufpe.br) on 2015-03-06T18:19:42Z No. of bitstreams: 2 DISSERTAÇÃO Carlos Diego Cavalcanti Pereira.pdf: 4207386 bytes, checksum: 1b429f9663fd012cb9da480f02ee5391 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) / Made available in DSpace on 2015-03-06T18:19:42Z (GMT). No. of bitstreams: 2 DISSERTAÇÃO Carlos Diego Cavalcanti Pereira.pdf: 4207386 bytes, checksum: 1b429f9663fd012cb9da480f02ee5391 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2014-03-18 / As metodologias ágeis de desenvolvimento de software emergiram como alternativa para processos prescritivos, os quais são classificados como excessivamente formais. Com objetivo de viabilizar entregas frequentes, processos adaptáveis, flexíveis e focados no cliente, as metodologias ágeis se tornaram referência sobre como produzir software de forma produtiva. Contudo, com objetivo de tornar o processo mais simples, essas abordagens invariavelmente incorrem em problemas como: modelos pouco generalistas para cobrir todo o ciclo de vida da Engenharia de Software; foco em disciplinas específicas do processo de software; subestimação de aspectos relevantes em iniciativas de desenvolvimento, como esforços de arquitetura, design e documentação; e indicação para equipes e projetos de pequena escala. A proposta desta dissertação de mestrado é propor um framework de processo eficiente de desenvolvimento de software, o qual se baseia nos ideários das metodologias ágeis, porém cobre todo o ciclo de vida de projeto desde a concepção, gestão, implementação e entrega. O framework inclui ferramentas como princípios, valores, atividades, artefatos e práticas específicas, incluindo esforços como arquitetura, design e documentação, concebendo um processo ágil, eficiente e extremamente produtivo para projetos de concepção e manutenção software, independentemente da sua escala.

Made available in DSpace on 2015-04-22T22:00:52Z (GMT). No. of bitstreams: 1 Dissertacao_antonio_ver_12.pdf: 602549 bytes, checksum: f4b20bf4513c0983ee97d39a99a89a2d (MD5) Previous issue date: 2010-08-23 / FAPEAM - Fundação de Amparo à Pesquisa do Estado do Amazonas / The industry, to reach more consumers, has adopted the mass customization concept to develop several and different products sharing the same components, in other words, launch similar products attending specific requirements from several market segments. The methodology used to develop software for mass customization is the software product line engineering (SPLE) that uses component reuse concepts in an efficient and systematic way, resulting on several software products sharing a common platform, which are part of a software product line (SPL). Scrum is an agile process that can be used to manage and control complex product and software development by using iterative and incremental practices. It was invented to rapidly drive new products to market, and was designed for hyper productive teams where productivity increases by 5-10 times over industry averages and many collocated teams have achieved this effect. Both, SPLE and Scrum, are designed to develop software products in a productive way, but SPLE has adopted the systematic reuse as its main principle, and Scrum has adopted the self-management teams and agile manifesto. This M.Sc. thesis shows the ScrumPL, a method combining both SPLE and Scrum methodologies based on their input and output needs and the Scrum lifecycle. This process was applied to develop a TV navigation system SPL, with one of the digital TV standards (ISDB-TB, DVB or ATSC), one language, for low-end, mid-end or high-end set-top-box market segment. / A indústria, para alcançar um número maior de consumidores, tem adotado o conceito de customização em massa, ou seja, lançar produtos similares, mas que atendam a requisitos específicos de vários nichos de clientes. A metodologia que trata de desenvolvimento de software voltado à customização em massa é a engenharia de linha de produto de software (SPLE), a qual busca reutilizar componentes de software de forma sistemática e eficiente resultando nas linhas de produto de software (SPL). Scrum é um método ágil usado para gerenciar e controlar o desenvolvimento de produtos e softwares complexos através de um processo iterativo e incremental, que foi criado para introduzir novos produtos no mercado de forma rápida. Esse método tem apresentado ganhos de produtividade de 5 a 10 vezes maior que a média da indústria convencional de desenvolvimento de software. Ambas as metodologias são projetadas para desenvolver produtos de software de forma produtiva, onde a SPLE adota o reuso sistemático de componentes como seu principal princípio, ao passo que o método Scrum lança mão de times auto-gerenciados e do manifesto ágil como os seus. Este trabalho apresenta e discute um processo, denominado ScrumPL, que combina ambas as metodologias para o desenvolvimento de SPLs, baseando-se nas entradas e saídas de cada etapa do Scrum e da SPLE. Por fim é discutida a aplicação deste novo processo no desenvolvimento de uma linha de produto de software de um sistema de navegação de TV digital interativa voltada para três seguimentos de mercado, três padrões de TV digital (ISDB, DVB e ATSC) e vários idiomas.

The use of agile methods continues to increase within software development but the agile processes do not contain the necessary steps to account for the user and realize the usability of the system. It seems it is therefore necessary to integrate the UCD methodology and agile methodology. What this integration should look like is not always apparent as the integration needs to be adapted to the specific context in each organization. Accompanied by a pre-study which identified difficulties with the integration, the current study examines how UCD specialists experience the communication through boundary objects in distributed agile teams. Furthermore the study examines how the understanding of the user is communicated to the developers in the agile teams and the potential of doing so with a design rationale. A case study was therefore performed with interviews of six UCD specialists to try to answers these questions. A content analysis was performed in relation to each research question and identified a number of themes relating to the experiences concerning; (1) communication through boundary objects, (2) how an understanding of the user is communicated, and (3) opinions of using design rationale for this purpose. Some of the conclusions drawn are that boundary objects only aim at communicating the interaction with the system, that they should be viewed as communication aids as they are not stand-alone and making them comprehensive would be even more time consuming. Furthermore, personas are not deemed fitting for communicating the understanding of the user to developers. This should instead be done by allowing developers to participate in user research.

Context: Global software development is the emerging trend in today’s world as it provides the software companies with certain advantages like access to skill and cheap labor, low development cost etc. There are also many challenges and risks involved in globally distributed software project as compare to co-located projects like communication, coordination and control etc. due to geographical separation. There is also a recent interest in applying agile methods in offshore projects in order to minimize certain offshore challenges. Agile methods in collocated environment demands high communication, coordination and collaboration between the team members. However implementing agile methods in distributed environment is beneficial and challenging too, because of inherited GSD challenges. Therefore, it is necessary to carefully understand the benefits and challenges of applying agile methods in distributed project before actually initiating the development. Objectives: This research study aims to look at current empirical evidence regarding benefits and challenges of applying agile methods in offshore projects, in order to understand it properly. Furthermore, we have examined that which of the benefits and challenges reported in literature can be seen in practice. This helped us in finding out the similarities and differences between the benefits and challenges that are reported in literature and in practice. Methods: To fulfill our aims and objectives we have first conducted the detailed systematic review analysis of the empirical studies from year 2000-2010. The systematic review approach helped us to collect and summarize the empirical data available regarding the benefits and challenges of applying agile methods in offshore projects. The research studies were identified from the most authentic databases that are scientifically and technically peer reviewed such as Inspec and Compendex, IEEE Xplore, ACM digital library, Springer Link, Science Direct, Google Scholar, Scopus, ISI Web of Knowledge and Willey Inter Science Journal Finder. Furthermore, industrial survey was conducted in order to identify whether the benefits and challenges enlisted in literature can be confirmed by practitioners. This helped us in determining the similarities and differences between benefits and challenges that are reported in empirical literature and industrial survey. Results: From systematic review results, we have found the list of benefits and challenges of most applied agile practices such as daily scrum meetings, sprint planning meetings, sprint review meetings, retrospective meetings, pair programming, short release and on-site customer. The most common benefits related to above identified agile practices are early problem identification, project visibility, increase communication, coordination and collaboration, trust, clarification of work and requirements, early client feedback and customer satisfaction. Similarly the most common challenges associated with above identified agile practices are lack of linguistic skills, culture differences and temporal differences. From survey result, it was found that the majority of benefits and challenges identified through literature review are prevalent in software industries to some extent. We were able to identify the benefits and challenges of agile practices such as daily scrum, sprint planning meetings, sprint review, retrospective meetings and short release. The most common benefits of above identified agile practices highlighted by survey participants are project visibility, early problem identification, increase coordination, opportunity for knowledge sharing and transferring, immediate feedback from client, and opportunity for understanding the task properly. Similarly the most common challenges identified by survey participants are language problems, temporal difference and difficult to explain and understand problems or issues over communication technologies. However, there are certain challenges like trust and culture issues, which have received most attention in the empirical literature, but are not identified by majority of industry respondents. Conclusions: From the information attained so far regarding the benefits and challenges of agile methods in offshore projects, we observed that there is an emerging trend of using agile methods in offshore projects and practitioners actually found it beneficial. The benefits of agile practices does not achieve straightaway there are certain challenging factors of GSD too, which can restrict the implementation or make the methodology not useful such as communication, coordination and collaboration. These challenges are usually occurred due to geographical separation, lack of trust and linguistic skills, culture difference etc. The presented work add contribution in a sense as to the best of our knowledge no systematic review effort has been done in this area with specifically focuses on highlighting the benefits and challenges. From survey results we found that majority of benefits and challenges highlighted by survey participants are to some extent same with what we have already studied in literature. However there are certain important challenges which have received most attention in empirical literature but were less identified by the survey participants like trust issue and culture difference. The benefits and challenges identified through industrial survey do not add much information into our attention. This does not mean that all possible benefits and challenges of applying agile methods in offshore project have been explored. The responses which were received from industry practitioners were quite few to make any kind of arguments. There is a probability that we missed the important benefits and challenges related to particular agile practices during our industrial survey. Therefore we conclude that a much thorough and inclusive answers should be required to identify the benefits and challenges of applying agile methods in offshore projects.

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

Software engineering practices have experienced significant changes over the period of past two decades. Keeping in view the competitive market trends, now is the high time for many organizations to shift from traditional waterfall models to more agile technologies like Scrum [22][23]. A change of this magnitude is often not easy to undertake. The reason that both software engineering techniques are different in many respects, organizations require considerable amount of analysis of the whole transitioning process and possible scenarios that may occur along the way. Small and medium organizations are normally very skeptical to the change of this magnitude. The scale of change is not limited to only software processes, in fact, difficult part is to deal with old attitudes and thinking processes and mold them for the new agile based Scrum development. The process of change therefore need to be understood in the first place and then carefully forwarded to the implementation phase.

Everyone is talking about the software development methods but these methods are categorised into the different parts and the most important are two categories, one is agile software development methods and second is using the traditional software development methods. Agile software methods are relatively considered to be quick and for the small teams. Our main mission is to check which method is better from each other, so for that purpose we go out in the software development market to meet the professional to ask about their satisfaction on these software development methods. Our research is based on to see the suitable method for the professionals; see the challenges on the adoptability of methods and which method is quicker. To perform this study we have gone through a survey questionnaire, and results are analysed by using mixed method approach. Results shows that professionals from both types of methods are satisfied but professionals with traditional methods are more satisfy with their methods with respect to development of quality software, whereas agile professionals are more satisfied with their methods with respect of better communication with their customers. With agility point of view, our study says that both methods have characteristics which support agility but not fully support, so in such case we need to customize features from both types of methodologies.

L'objectif général de ce projet était d'analyser l'activité lors de compétitions de niveau international en rugby à XV et d'explorer l'évolution du niveau d'activité au cours du match pour quantifier la fatigue. Dans une première étude il a été démontré que le niveau d'activité ne variait pas de façon significative au cours du match si l'on quantifiait l'activité des joueurs par l'analyse de la vitesse et du rapport entre la durée d'activité et la durée de la récupération. Par contre, on observe une diminution significative de l'accélération moyenne sur la deuxième mi-temps, cette diminution étant plus particulièrement marquée pour le groupe constitué des troisièmes lignes et des talonneurs. Dans une deuxième étude, nous avons proposé d'étudier la fatigue lors de 12 répétitions d'exercice statique simulant la poussée en mêlée. Les résultats démontrent une diminution significative de la force produite de 11,7 % ce qui est relativement faible si l'on considère le protocole qui consistait à répéter 12 fois 5 s de poussée maximale entrecoupées de périodes de récupération de 15 s. Le faible coût métabolique de la contraction isométrique en comparaison de la contraction concentrique pourrait expliquer la diminution relativement faible de la force produite. L'ensemble de ces résultats suggère que l'enchaînement des séquences de jeu statiques et dynamiques et des périodes de récupération lors d'une compétition internationale permet de maintenir le niveau global d'activité / The overall objective of this project was to analyze the activity at international level competitions in rugby union and to explore the evolution of the level of activity during the match to quantify fatigue. In the first study it was demonstrated that the level of activity did not vary significantly during the match if velocity and the ratio between duration of activity and of recovery periods were analyzed. A significant decrease in the average acceleration in the second half was evidenced; this decrease was particularly marked for the group constituted by back rows and hookers. In a second study, we proposed to study fatigue during static exercise simulating the scrum. The results show a significant decrease in the force produced by 11.7 %, which is relatively low considering that the protocol consisted in 12 time 5 s of maximum effort interspersed with recovery periods of 15 s. The low metabolic cost of isometric contraction compared to concentric contraction could explain the relatively small decrease of the force produced. Taken together, these results suggest that the players’ combinations of action, static or dynamic, and recovery times were optimal for preventing large decrease in physical performance