Arpáš JozefAbstract. The essay deals with the different ways of communication within and between teams during software development. It focuses in particular on the case of software development, where teams collaborate with offices in the same building, but where the level of communication is similar with teams thousands of miles distant. I identified the reasons why the communication between the teams is needed. This fact is mainly due to the interdependence of the individual teams. I can say that the lack of communication is due to mainly ways to apply team members to communicate outside of the team. Main problem can be described as increase in email communication, precisely at the expense of verbal communication. Then I put my experience into practice, showing that the team members have either personal obstacles, why not sufficiently communicate with members of other teams, or cannot identify the person with whom them need to communicate, or other personal or behavioral barriers that prevent them from communication. At the end of the essay, I proposed a solution to prevent a lack of communication between the teams, which is based on the correct management team members, project managers resulting in improving their communication skills and greater independence.Balko KarolAbstract. There are various indicators and methods which help us significantly in monitoring and further dealing with problems during the software development, however, not all of them are applicable in monitoring of projects developed in small teams. This thesis focuses particularly on those, which are helpful for us especially in projects developed within small teams.Dorner MichalAbstract. Version control and issue tracking system are now both fundamental support tools for software development. Along with documentation, they are part of any larger project. This essay focus on their integration, ergonomics and proper use. Lists the current situation and the functionality which can improve it for better orientation in the entire project.Konôpka MartinAbstract. Important part of project planning is the creation of plan and its monitoring. However, activities planned for the completion of the project often take longer than was expected. There are several approaches for development of software projects and each uses different way of planning. Customer requirements for the software projects frequently change and so does the project plan even during its formation. Planning Manager must be able to respond to emerging changes in customer requirements or problems in implementation of the plan. The key thing is to visualize the plan but each approach for development offers different techniques. Since we do not know a way how to create perfect plan, there can be no perfect technique either. But we can combine the advantages of several techniques together. In the essay, we discuss combination of existing techniques for plan visualization in a traditional and agile approach.Košický MartinAbstract. CMMI is a more and more used reference model, that helps improve quality assurance in a company. Process improving is based on maturity models and capability models. Even though CMMI helps to improve quality it does not guarantee so. This essay is considering the impact of increasing maturity levels on the organization and how it looks, if a company is on the bottom level. If failure is inevitable with low maturity levels or no levels, and why a company with high CMMI level fails to delivery high quality products. Essay points out that motives that encourage the company to take over CMMI are also key elements for making quality software.Krajčovič JozefAbstract. Software development is an increasingly complex matter that involves a large number of diverse processes and requirements. This prompted the company to reorganize management of consistent stimulus to more efficient use of available resources. One of these sources are supportive tools that are used in the software development process. Way how to anhancement of effectivity at support tools used of software development is to automate routine operations that are mostly performed manually. This essay I will try to convince you of the benefits of using automation. In an essay are alse answer on this questions. What and when to automate? Application of automation is also beneficial in small teams and small projects?Láni MarekAbstract. The problems associated with insufficient documentation have to be faced probably by 99% of programmers if not by all. The creation of documentation is not a difficult process of software development, but this process is generally not met with much likes. Even modern approaches to software development pay limited attention to it. Such an approach is also an agile development. Its motto says: "Working software over documentation" and its answer to the question of how much documentation is necessary is: "Just enough." However, examples from practice show that documentation is a very important part of a software project and there are instances where a working software can not exist without it. We also try to define how much documentation is "just enough" and we discuss the patterns of documentation related to agile development. These patterns are Fake documentation, Timestamps, Project dictionary, Electronic backup and Distinct activity. For each of these models there are provided examples under what circumstances is creating of a specific type of documentation favorable, and what problems will it help us to avoid. We also discuss the possible ways in which it could be improved and outline the pros and cons of each solution.Lipták MartinAbstract. Software quality consists of functional aspects, that are visible to the customer, and structural aspects, that are visible only in cases of their insufficiency. Quality must be built into product in each development phase including specification. Incorrectly specified product is a bad-quality product, since it is of no value for the customer. On the other hand, product built with quility in mind in each one of its development phases, leads to customer satisfaction. Quality must be constantly improved in the development process. Essay compares aspects of quality of web, mobile and desktop applications.Lóderer MarekAbstract. Information and knowledge is an important part of every team. Large number of specialized software tools is used to transmit, process and store information. Teams try to choose tools that best cover their needs. This essay highlights the different groups of software tools that allow the transmission and storage of information in teams. It describes some of their common and different features. The essay describes a group of support tools that are used to share source codes and solve problems and errors discovered in software development process. Data from these support tools can produce new information and hidden dependencies. They can help managers to manage their team and enable timely response to emerging issues. The essay also describes several ways to streamline the processing of data from those systems, in order to produce more accurate and reliable information.Rais JaroslavAbstract. Total quality management has absorbed static methods of quality management and has integrated not only the focus on the software process and product, but also the focus on the external and internal customers. In other words, success is built on three pillars, namely the customer, the software process and people. [Phil Crosby] Total Quality Management is not controlled by any rules or standards (ISO), but it applies everything that can encourage good quality of the development of a software product. The introduction of Total Quality Management helps to build a good and flexible way to achieve the desired quality of a software product, with a focus on an employee and a customer from different cultural, religious and economic backgrounds.Roško MichalAbstract. Planning of any project is a complex operation and planning of a project, which is based on costumer´s concept even more. Is therefore SCRUM using ideal in every case? However SCRUM is actively used and offers the possibility to create a product that is based on customer´s concept, but what factor do the experiences of team members play in the planning in SCRUM? What level of experience must the planning manager have? Many other questions come to mind, when you think about the title, if the planning in SCRUM is so good for the planning manager. Planning of each stage in SCRUM has its pitfalls and especially the planning can be affected by several factors. SCRUM is based on a team, but what happens if the team is not experienced enough? One of the major factors that affect several stages, not only the planning, is an experience, whether it is an experience of the team, team members or the planning manager.Ružička PavolAbstract. In this essay we are going to deal with the management of risks in the development of software, but in terms of supporting tools. These tools would help us in the management of risks or in the best case they should make the decision instead of us. The important question is whether it is suitable to use the concrete tool for the existing risk. Before we start to use any tool we have to consider what information it needs for the input and what can be provided for us. It is needed to consider whether the thing that will be provided for us is worthwhile and the money that we have to have for using this tool are also important. If we use the production device inappropriately it can give us wrong output information. This can influence our decisions and make a mistake. The mistake in the management of risks can influence the project in the way we will not be able to finish it successfully.Šteňová AndreaAbstract. Healthy communication inside team is crucial prerequisite for project to be successful. In distributed team environment it is even more complicated and even more important to manage communication properly. Team members have to communicate and cooperate with someone, whom they have never met before. The most preferred type of communication, face to face, is not possible within distributed team. Growth of the new communication supportive technologies opens up new possibilities of more efficient communication in local teams. Proper use of these technologies allows us to solve problems associated with distributed teams creation. I have identified variety of communication forms and their efficient usage in the essay. Can distributed team be efficient? Efficiency does not depend solely on its communication, however, the communication can be efficient.Sudor VladimírAbstract. This work seeks to clarify the different metrics monitoring project. It also offers important features for the metrics that need to be taken into account when choosing a particular metric. I tried to identify general properties that they can be applied to all metrics. Further in the work is already specifically mentioned metrics described by these properties. For each metric are provided by its advantages and disadvantages. The aim of this work is to determine what we allow and metrics to help the reader make better choices the selection of the metrics. Because of the large number of metrics and we can all use. The combination of appropriate metrics can avoid most of the problems in software development.Tomlein MatúšAbstract. Software projects tend to have a poor implementation of risk management processes, which is a common reason why many projects are not ready to enter the market or face numerous problems during development. However, there is also room for an opposing problem, which is excessive and inefficient risk management. Although it is rare, excessive risk management can cause losses and threaten the project. How can such situation manifest in real projects? And what are the best practices to avoid it? This essay aims to provide answers to these questions and discusses various factors that might cause excessive risk management.
|