This master thesis focuses on the agile methods description and their use in creating of company strategic material. The main part of this thesis consist of the SCRUM and Kanban method. The work contribution is an optimization of the document creation process. The solution proposed is implemented through the MS SharePoint server with mind mapping module and Kanban board module. Thanks to this solution, company project can be managed in a more effective, faster and higher quality way.

Um Data Warehouse (DW) é um banco de dados centralizado, orientado por assunto, integrado, não volátil e histórico, criado com o objetivo de dar apoio ao processo de tomada de decisão e que estrutura os dados em uma arquitetura analítica bastante distinta da arquitetura relacional utilizada nos bancos de dados transacionais. Construir um DW é um projeto de engenharia bastante complexo pois envolve muitas tecnologias e muitas pessoas, de diferentes equipes, em um grande esforço conjunto para construir esta base central de informações corporativas. O processo tradicional de construção de um DW não utiliza conceitos ágeis e, pelo escopo de desenvolvimento ser grande, pode levar muito tempo até que funcionalidades sejam entregues aos clientes. Os métodos ágeis de engenharia de software são muito usados como uma alternativa aos métodos tradicionais de desenvolvimento e têm diferenciais que trazem muito valor a projetos grandes pois, além de buscar desenvolver versões funcionais em prazos curtos, defendem que todos os sistemas têm a constante necessidade de se adaptar a mudanças. Neste trabalho são aplicadas práticas ágeis no processo tradicional de engenharia de DW para que o desenvolvimento seja realizado em ciclos iterativos curtos, tornando possível o desenvolvimento rápido e evolutivo de um DW com entregas constantes de novas funcionalidades. A contínua evolução deste complexo ambiente analítico é apoiada por conceitos de banco de dados evolutivos e também por fundamentos de métodos ágeis. / A data warehouse (DW) is a central database, subject-oriented, integrated, nonvolatile, and time-variant collection of data in support of management\'s decision making process and that summarize the data in an analytic architecture quite different from the relational one, used in transactional databases. Building a DW is a complex engineering project because it involves many technologies and many people, from different teams, in a huge corporative effort to build a central database with corporative data. The traditional engineering process to build a DW does not use agile concepts and, as its scope is quite big, it might takes a long time until the customer can use its features. Agile methods of software engineering are commonly used as an alternative to the traditional methods and they have some differentials that lead a lot of value to big projects, as the continuous attempt to develop short releases in short periods of time, or the belief that every system needs to be continuously adapted to the changes on its environment. This work applies agile practices in the traditional DW engineering method, so that the development can be done in short iterative cycles, making possible a fast and evolutive DW project, with frequent delivering of new functionalities. The continuous evolution of this complex analytical environment is supported by evolutive database concepts and also for agile methods foundations.

A modelagem evolutiva de bancos de dados é necessária devido às frequentes mudanças de requisitos das aplicações. O desafio é ainda maior quando o banco de dados tem de atender simultaneamente a várias aplicações. A solução proposta por Scott Ambler para evolução utiliza refatorações e define um período de transição, durante o qual tanto o esquema antigo quanto o novo coexistem e os dados são replicados por meio de um processo síncrono que apresenta várias dificuldades, como a interferência no funcionamento normal das aplicações. Para minimizar essas dificuldades, esta tese propõe um processo assíncrono para manter atualizados esses esquemas e apresenta um protótipo de uma ferramenta para auxiliar as evoluções dos bancos de dados. A proposta foi validada por meio de um experimento em laboratório que comparou a solução aqui apresentada com a proposta por Ambler. / Evolutionary database modeling is necessary due to the frequent changes in application requirements. The challenge is greater when the database must support multiple applications simultaneously. The solution for evolution proposed by Scott Ambler is refactoring with a transition period, during which both the old and the new database schemas coexist and data is replicated via a synchronous process, what brings several difficulties, such as interference with the normal operation of applications. To minimize these difficulties, this thesis proposes an asynchronous process to keep these schemas updated and presents a prototype tool to evolve databases. The proposal was validated by a laboratory experiment in which the solution presented here was compared with the one proposed by Ambler.

El presente trabajo tiene como objetivo principal proponer un modelo para desarrollo de habilidades blandas y valores de métodos ágiles, para una organización que desee adoptar los métodos ágiles para el desarrollo de proyectos aplicando los Estándares Globales del PMI. Muchas organizaciones pretenden implementar métodos ágiles, como por ejemplo Scrum, presumiendo que todos los miembros de la organización están dispuestos y listos para comprender lo que implica trabajar con métodos ágiles. Esta presunción suele ser un error en la gran mayoría de casos, lo que lleva al fracaso al momento de implementar métodos ágiles como solución a una baja productividad o como un intento de mejora de la organización. Este trabajo de basa, principalmente, en la Guía Práctica de Ágil (Project Management Institute, 2017), la Guía del PMBOK® 6ta Edición (Project Management Institute, 2017) y la Improv Encyclopedia (improvencyclopedia.org, 2018), de donde se han tomado conceptos, técnicas y herramientas para poder proponer un modelo que sea compatible con cualquier organización que los adopte. Cabe destacar que este modelo se ha ido mejorando durante varias ejecuciones prácticas en organizaciones que, por motivo de confidencialidad, tendrán nombres cambiados pero que nos ayudarán a ilustrar mejor los objetivos que se obtienen con la aplicación de este modelo. Todo este modelo se ha trabajado bajo el nombre comercial de XENDA FREERUN, a cuál en adelante denominaremos FREERUN. Este modelo cubre el análisis y diagnóstico por medio de entrevistas realizadas a los miembros de una organización, la programación de un plan de trabajo y, finalmente, la ejecución de este y la evaluación final. / The main objective of this paper is to propose a model for the development of soft skills and values of agile methods for an organization wishing to adopt agile methods for the development of projects applying the Global Standards of the PMI. Many organizations intend to implement agile methods, such as Scrum, if all members of the organization are willing and ready to understand what it means to work with agile methods. This assumption is often a mistake in most cases, leading to failure to implement agile methods as a solution to low productivity or as an attempt to improve the organization. This work is mainly based on the Agile Practice Guide (Project Management Institute, 2017) the PMBOK® 6th Edition Guide (Project Management Institute, 2017) and the Improv Encyclopedia (Improv Encyclopedia, 2018), from which concepts, techniques and tools have been taken to propose a model that is compatible with any organization that adopts them. It should be noted that this model has been improved during several practical executions in organizations that, for reasons of confidentiality, will have changed names but that will help us to better illustrate the objectives obtained with the application of this model. All this model has been worked under the commercial name of XENDA FREERUN, which in future we will call FREERUN. This model covers the analysis and diagnosis by means of interviews made to the members of an organization, the programming of a working plan and, finally, the execution of this and the final evaluation. / Trabajo de investigación

This diploma thesis deals with a type of efficiency improvement of the hiring process in a company, where agile methods are used for the development of its software products. The theoretical part describes specification of traditional and agile methods, and a profound description of the Scrum and Kanban methods and the use of agile methods for hiring activities. In the following part, there is issued an analysis of the current situation in the company oriented to HR department and suggesting possible solutions for discovered problems.

This diploma thesis deals with a type of a project management of marketing activities in a company, where agile methods are used for development of its software product. The theoretical part describes specifications of traditional and agile methods, their comparison, a profound description of the Scrum method and the use of agile methods for marketing activities. In the following part, there is issued an analysis of the current situation in the company oriented to marketing department and possible solutions of discovered problems are suggested there.

Abstract The adoption of agile methods in software projects has been fast. The majority of new software projects utilises agile methods, and they have radically changed the internal dynamics of software development projects. This has created a need for adjustments in the management of software projects. The current literature rarely discusses the early phases of agile projects: contracting and organising agile projects. The literature also lacks investigations on the project management practices of agile projects. This dissertation focuses on flexibility as it occurs in agile software projects. The main objective of this research is to explore the nature of flexibility in agile software projects and study the challenges of project contracting and management in leveraging agile development methods. The research was conducted as a mixed methods research. The research findings contribute to the emerging literature on agile project management. Secondarily, the results contribute to proactive contracting literature. The results indicate that agile methods can be used to increase flexibility and efficiency in software projects, but flexibility needs to be planned by projects parties. This planning activity already starts in the negotiation phase, and it is optimally summarised in the project contract. Thus, it is also important that lawyers contributing to project contracts are aware and informed of the business contexts. The traditional project management approach needs adjustments in adopting agile practices. This research reports several categories of challenges faced in adopting agile practices and increasing flexibility in projects. The results also indicate that projects delegate part of the decision-making authority to implementation teams in order to increase flexibility. By taking some of the decisions closer to project implementation, flexibility can be used to manage uncertainties caused by a complex environment. / Tiivistelmä Ketterien kehitysmenetelmien käyttö ohjelmistoprojekteissa on yleistynyt nopeasti. Suurin osa alkavista ohjelmistoprojekteista käyttää jo ketteriä menetelmiä ja niiden soveltaminen on muuttanut radikaalisti kehitysprojektien sisäistä dynamiikkaa. Tämän vuoksi on syntynyt tarve tarkastella tarkemmin ketterien projektien johtamista. Kirjallisuudessa on harvoin tarkasteltu ketterien projektien alkuvaiheita, sopimuskäytäntöjä ja organisoitumista. Kirjallisuudessa ei myöskään vielä käsitellä ketterien projektien projektinhallinnan käytänteitä. Tämä väitöskirjatutkimus tarkastelee joustavuutta, joka ilmenee ketterissä ohjelmistoprojekteissa. Työn päätavoite on tarkastella joustavuuden luonnetta ketterissä ohjelmistoprojekteissa ja tutkia mitä haasteita ketterien menetelmien käyttö aiheuttaa projektin sopimusprosesseissa ja projektinhallinnassa. Väitöskirjatutkimus on toteutettu monimetelmätutkimuksena. Tutkimustulokset kohdistetaan tuoreeseen tieteelliseen projektitutkimuksen keskusteluun ketteristä projektinhallintamenetelmistä. Toisekseen, väitöskirja osallistuu ennakoivaa sopimista käsittelevään oikeustieteellisen tutkimusalan keskusteluun. Tutkimustulokset osoittavat, että ketteriä menetelmiä voidaan käyttää lisäämään joustavuutta ja tehokkuutta ohjelmistoprojekteissa, mutta joustavuus tulee olla suunniteltua, jotta siitä voidaan hyötyä. Joustavuuden käytön suunnittelu alkaa jo projektin neuvotteluvaiheessa ja kirjaukset joustavuuden hyödyntämisestä on optimaalisesti kirjattu jo projektisopimukseen. Tämän vuoksi on tärkeää, että sopimuksen muotoiluun osallistuvat juristit ovat hyvin perillä liiketoiminta-alasta ja ovat tietoisia, että sopimus tulee sisältämään joustavuusnäkökohtia tarkoituksellisesti. Perinteinen projektinhallinta kaipaa myös muutoksia ketterien projektien johtamiseen. Tutkimus osoittaa seitsemän pääkategoriaa haasteita, joita yritykset kohtaavat siirtyessään käyttämään ketteriä menetelmiä. Tutkimus osoittaa myös, että ketterissä projekteissa päätöksenteko on joustavuuden lisäämiseksi hajautettu itseohjautuville tiimeille. Kun päätöksentekovaltaa siirretään lähemmäs varsinaista kehitystyötä, voidaan joustavuuden avulla hallita epävarmuutta kompleksissa ympäristössä.

The goal of this work is to analyze the problems of implementation of agile methods and to map it's positive and negative consequences. The first chapter briefly describes the history and sources of the given group of project development methodologies, including comparison of agile, waterfall and lean methods. In the second chapter, there is information about principles of agile methods, their structure and some concrete methods. The last part of the second chapter aims at the significance of agile methods and their use. The third chapter explores the studies of the given topic in Czech environment as well as outside of it. The practical part of thesis is based on the literature review and it presents the qualitative research of three companies as well as the analysis of the results. Information that was acquired during the semi-structured interviews and results of the literature research were used as the base for recommendations suggested in the conclusion of this work. Keywords: agile methods, project management, qualitative research

The agile principles applied to software engineering include iterative and incremental development, frequent releases of software, direct stakeholder involvement, minimal documentation and welcome changing requirements even late in the development cycle. The Agile Requirements Engineering applies the above mentioned principles to the Requirements Engineering process. Agile Requirements Engineering welcomes changing requirements even late in the development cycle. This is achieved by using the agile practice of evolutionary requirements which suggests that requirements should evolve over the course of many iterations rather than being gathered and specified upfront. Hence, changes to requirements even late in the development cycle can be accommodated easily. There is however, no real process to the agile approach to Requirements Engineering. In order to overcome this disadvantage, we propose to adapt the Requirements Generation Model (a plan-driven Requirements Engineering model) to an agile environment in order to structure the Agile Requirements Engineering process. The hybrid model named the Agile Requirements Generation Model is a soft-structured process that supports the intents of the agile approach. This model combines the best features of the Requirements Generation Model and Agile Software Development. / Master of Science

Las organizaciones reconocen la necesidad de cambiar el modelo de negocio tradicional por uno cada vez más digital y ágil. Por ello, han empezado a transformarse digitalmente, buscando ser más competitivos en un entorno cambiante. Sin embargo, este proceso es relativamente nuevo, y en el Perú son pocos los que han logrado implementarlos positivamente. Por ello, cada vez hay más empresas que reconocen la necesidad de transformarse, pero que desconocen cómo hacerlo. Esta investigación comprende la recopilación bibliográfica, realización de entrevistas, procesamiento de encuestas a los 4 principales bancos, y el análisis estadístico de los resultados para desarrollar estimaciones que permitirían conocer los principales factores que pudieron priorizarse para tener un desarrollo eficiente en este proceso. Esta investigación reúne información y analiza las percepciones de sus trabajadores para realizar estimaciones exploratorias acerca de los factores que permiten obtener un desarrollo eficiente de transformación digital. Se realizaron entrevistas a expertos de diversos sectores y a 4 trabajadores del sector bancario. Finalmente, se realizaron 70 encuestas, de los cuales 59 fueron válidas para su procesamiento. Sin embargo, debido a las limitaciones de tiempo y confidencialidad, no se pudo obtener un tamaño mayor, impidiendo hacer un análisis concluyente a nivel estadístico que pudiera extrapolarse el resto de las empresas. Finalmente, se identificaron 2 enfoques que permiten obtener un desarrollo eficiente en el proceso de transformación: centrarnos en el cliente y colaborador, tomando en cuenta las limitaciones externas e internas durante proceso y reconociendo el objetivo o razón que los lleva al cambio. / Organizations recognize the need to change the traditional business model for a more digital and agile one. Therefore, companies have begun to transform digitally, seeking to be more competitive in a changing environment. However, this process is relatively new, and in Peru few have managed to implement it positively. This research includes bibliographic compilation, interviews, processing surveys to workers of the 4 main banks in Peru, and the analysis to develop statistical estimations that could make us recognize the main factors that should be prioritized to have an efficient development in their digital transformation process. By this way, this research collect data from the main banks in Peru and analyze opinions and perceptions of their employees in order to make exploratory and descriptive estimates about the process. Research considered interviews of experts from different sectors, including members of the analyzed banks and finally 70 surveys were carried out, of which 59 were validated for processing. However, due to the time and confidentiality limitations, it was not possible to reach a larger sample size, so it did not allow us to make a conclusive analysis at a statistical level that can be used as a model for the other companies. Finally, two approaches were identified in the investigation in order to obtain an efficient development of the transformation process: putting the client and the collaborator as center, considering limitations in the process and recognizing the objective that leads the change. / Tesis