The primary influence on project results is human effort, therefore the most essential tool for effort management and focus is communication. Communication in Project Management is characterized by its complexity however it may be analysed from two perspectives; communication tools and human factor. The main objective of this work is to identify problematic areas of internal communication in Project Management and the design of corrective measures that will mitigate or eliminate these problems. This work is based on research in a dynamic environment and comprehensive project program, which is an excellent example and material for definition of such areas. The theoretical section lists the topics of project management and communication; each topic affects specific features that are part of the program or directly related (SOA, agile management, conflict parties business, ICT, etc.). The practical part acquaints readers with the concept of sociological research and defines a hypotheses and set of methods that were used in this research. Further, it contains a description of the program in which research was undertaken and the results of such analysis with recommendations on what measurements should be implemented to improve communication and its effectiveness.

The thesis focuses on analysis and the selection of an appropriate project management tool for web based projects. The theoretical part characterizes project management, level of project management in IT environment and web based projects with their specifics. Within the web based projects, it characterizes the possibilities of development and delivery of the Web applications and the methodology used in the development -- rigorous and agile methodologies. The work focuses on the description of agile methodologies in managing software development and their usage in the management of web based projects. Procedures and ways of managing agile methodologies are reflected in the definition of requirements for functionality analyzed among the project management tools in the practical part. The practical part focuses on the description and characteristics of a sample of project management tools used in web based projects and analyzes the selection of the most appropriate one. Evaluation of project management tools is based on the level of compliance with the pre-defined functionalities and comparison of the cost of acquisition and operation for a 3 years period. The functionality of the selected project management tools is evaluated on the basis of meeting the level 8 defined areas. The cost for the project tools are evaluated in the methods of acquisition, which offers their suppliers - On-Premise, On-Demand with proprietary tools and Open Source Software tools under the GNU General Public License.

Diploma thesis deals with creating a Methodology for small software projects focused on automated testing of using Selenium WebDriver tool (abbreviated MMSP - Selenium). The created methodology is based on customized methodology MMSP, which aims to transform part for automated testing of using Selenium WebDriver tool through the best principles and practices of already completed studies. Firstly, there will be summarized the most important terms related to the diploma thesis. Then will follow implementation of the methodology MMSP - Selenium, which is complemented by its new roles, tasks, and work products. Personal benefit of the diploma thesis is also created guidelines for Selenium WebDriver testing tool. For great benefit is also considered the publication of the methodology using the Eclipse Process Framework Composer tool. In conclusion of the created methodology verifies the business use cases, aimed at testing the functionality of web application Manuscriptorium.

The main goal of this diploma thesis is the proposal to use agile development procedures of Scrum framework with UML modeling language applicable for creating websites of small scale. The emphasis is especially put on creating a practically usable type model of the websites. The theoretical part of the thesis has two main chapters. In the "Agile methodology" chapter are listed principles of agile approach to creating software. The next part of this chapter is focus on agile methodologies (Scrum, XP, ASD, FDD, DSDM, LD and Crystal). In the "UML" chapter is introduced modeling language UML and its principles. The next part of this chapter is focus on UML diagrams used in practical part of this thesis (use case diagram, class diagram, sequence diagram, activity diagram and deployment diagram). The practical part of this thesis focuses on the design type model for creating websites of small scale. The type model is based both on the theoretical part of this work and practical experience of the author. In the first part is introduced scheme of model, where is shown the mutual relationship of individual phases. In the next part of this chapter are discussed the individual phases where is used the principle of agile development framework Scrum and examples of use of the UML diagrams.

A crescente demanda por sistemas e a alta velocidade com que seus requisitos evoluem têm evidenciado que desenvolvimento de software exige flexibilidade, pois muitas decisões precisam ser tomadas durante o projeto. Além disso, as dificuldades para a produção de sistemas vão muito além das questões técnicas. Fatores estratégicos, comerciais e humanos são responsáveis por algumas das variáveis que contribuem para tornar o desenvolvimento de sistemas de software uma atividade altamente complexa. Modelos tradicionais de desenvolvimento de software propõem processos prescritivos que não consideram toda essa complexidade. Por outro lado, Métodos Ágeis de desenvolvimento de software sugerem uma abordagem mais humanística com foco na entrega rápida e constante de software com valor de negócios. Porém, para conseguir isto, é preciso escolher um conjunto de práticas de desenvolvimento adequado às características do projeto e da equipe. Desta forma, a natureza única de cada projeto e a necessidade de alta qualidade e produtividade tornam importante a busca por práticas de desenvolvimento. A partir de projetos que conduzimos usando métodos ágeis na academia e na indústria, identificamos e descrevemos 22 práticas para desenvolvimento de software que podem ser adotadas por equipes para aumentar o seu desempenho e/ou a qualidade do software. / The growing demand for systems and the high speed with which their requirements evolve has shown that software development requires flexibility because many decisions need to be taken during the project. Also, the difficulties for the production of software systems go far beyond the technical issues. Strategic, commercial and human factors are responsible for some variables that contribute to make the software development a highly complex activity. Traditional models of software development propose prescritive processes that do not consider all this complexity. On the other hand, Agile Methods of software development suggest an humanistic approach focused on fast and often business valuable software deliveries. But, in order to get it, one needs to choose an appropriated group of development practices accordingly to the project and team features. In this way, the individuality of each project and the need for better quality and productivity motivate the search for software development practices. Based on projects that we conducted by using agile methods in academic and industry environments we identified and described 22 software development practices that can be used by teams to increase their performance and/or the software quality.

This thesis deals with the application of the functional packaging system Nix and its ecosystem (NixOS, NixOps) for CI/CD in agile development. When using these technologies, the problems caused by different environments are virtually eliminated without the need of containerization. The thesis contains a description of the possibilities and the shortcomings of Nix/NixOps and it proposes a general procedure for the use of these technologies in individual phases of agile development and CI/CD. Thanks to Nix/NixOps, the implementation of CI/CD is very simple and the whole process is also reproducible. The output of the work is a set of the examples demonstrating the use of Nix/NixOps in various projects, which is available as open-source. Thanks to this set, the developers can use Nix quickly and easily in any project, without having to study a large amount of materials.

The problem discussed in this thesis is the optimization of the process of planning, tracking and evaluating tasks in the management area of the department Corporate Technology in Siemens, Brno. Having studied theories of CMMI and principles of ISO 9001, the given process is optimized by automating certain manual tasks. As Corporate Technology uses a SharePoint server to manage tasks, the application is developed to improve his functionality. This application has therefore been tested in the environment of the organization with real-life data and complies to all necessary requirements to be able to save at least 50 % of time in the optimized process. The results of this thesis prove the usability of automating manual repetitive tasks being conducted in the processes of the organization and introduce possibility of increasing process level by preventing human errors.

The goal of master thesis "CMMI Certification for Software Development in Agile Environment" is CMMI quality model research with focus on software development in agile environment in the Siemens company. In the beginning CMMI model and Scrum methodics are introduced. The core of this thesis is focused on the current state analysis. Output of the analysis is a list of potential areas that are currently not compatible with quality model requirements. These areas are to be improved for the company to achieve the desired CMMI certification level. Possible improvements are introduced to the consultant. During the implementation part a web application is realized helping to remove most of the identified imperfections. Application benefit is objectively evaluated by an internal audit. The work includes discussion of possible further application development and quality model standard evolution in this company.

In den 80er und 90er Jahren hatten große Anwendungssysteme in Unternehmen einige hundert bis tausend Anwender. Der Software-Entwicklungsprozess für diese Anwendungen war innerhalb der Unternehmen relativ klar geregelt. Fachinformatiker und Fachabteilungen standen einander dabei gegenüber. Oft wurden auch externe Fachleute und Komponentenlieferanten integriert. Entwicklungsmethoden und Werkzeuge waren auf diese Situation ausgelegt. Seit dieser Zeit haben wesentliche Veränderungen stattgefunden. Internettechnologien haben neue Klassen von Applikationen ermöglicht, die wie folgt charakterisiert werden können: - Die Applikationen sind kooperativ (unternehmensübergreifend). Nicht selten sind 20-50 oder mehr Unternehmen z. B. bei Zulieferketten beteiligt. - Eine eigene Klasse bilden mandantenfähige Systeme sowie Business-to-Consumer Systeme (B2C) bei denen sehr große Nutzerzahlen konnektiert werden. - Die Entwicklungszeiten liegen im Bereich von Monaten statt Jahren für eine erste Bereitstellung einer Basislösung. - Die Systeme werden inkrementell unter starker Anwenderbeteiligung bis hin zur Endbenutzerbeteiligung weiterentwickelt. (...)

Most Agile Software Development methodologies are aimed towards large companies and large-scale projects. The purpose of this report was to identify, and potentially modify, Agile Development methodologies and strategies suitable for small-scale projects. Initially a comprehensive study was conducted on a few selected agile methodologies in order to find the most suitable one to be used for a loosely defined small-scale project. The result of the study led to the methodology Kanban being used experimentally on that project. The report goes through how Kanban was utilized and modified to better suit the project as well as bring forward interesting details regarding the outcome of the actual project. The produced methodology, with Kanban at its core, can especially be of use for small IT companies looking for an agile methodology fitting their project(s). It could also be used to further develop alternative variants of the agile methodology Kanban with focus on small-scale projects. / De flesta agila utvecklingsmetodiker riktar sig mot storskaliga projekt och företag. Syftet med denna rapport var att identifiera lämpliga agila utvecklingsmetodiker och strategier för småskaliga projekt. Inledningsvis genomfördes en omfattande studie av ett fåtal agila metodiker med målet att hitta den mest lämpliga för ett löst definierat småskaligt projekt. Resultat av studien ledde till att metodiken Kanban experimenterades med och användes för projektet. Rapporten går igenom hur Kanban nyttjades och modifierades för att bättre passa projektet i fråga. Den framtagna metodiken, med Kanban som grund, kan vara speciellt användbar för mindre IT-företag som letar efter en agil metodik som passar deras projekt. Den skulle även kunna användas för att vidareutveckla alternativa agila Kanban-metodiker för småskaliga projekt.