Belanji Juraj

Abstract. When a man stands in front of a problem, the first instinctive thing that occurs to him is to create a plan to solve that problem. Although that plan is not formally written, each person creates a plan in his mind. For creating a software product, a plan is also needed. The plan is the cornerstone of creating a good software product. As each person is a unique individual, so must any new plan be unique. But is this really true? Is it possible to create a plan, which would be a blueprint for creating new plans? This essay identifies errors that occur while creating a plan. The essay offers a different view on universal planning, and shows that sometimes a universally created plan yields better results than a newly created one.

Software support of project planning in small teams

Beliansky Michal

Abstract. Every one of us is unique man with goals and desires after entire life. We usually lead up all our materially, mentally and human resources to achievement all of these goals. We are consciously or unconsciously managing a planning our life under the influence. From the point of view this plans can be compared to project planning. We plan more extensive operations to achievement our goals in advance and mostly alone, or with your family, our loved ones, team mates. Effective using of visualization tools which are full of functions isn´t any speciality. Current support planning tools offer to beginner many functions with which we can´t meet in ordinary planning.

Software metrics - good helper but a bad master

Brath Marek

Abstract. Creating a software project is extremely complex process in which it is necessary to introduce some measurement methods that allow determine the properties of such a product. Using software metrics managers can monitor more effectively software projects and thus they can better manage resources and reduce overall project time. The main concern for companies is not only to create a quality final product that would satisfy a customer, but especially the most profit in the shortest possible time. Precisely for this reason are trying to implement the most effective ways to measure, but software metrics are not necessarily authoritative, and therefore it is important to use them wisely. Excessive rate of monitoring can be also counterproductive and therefore in the essay I will focus on best-known software metrics and methods for their efficient use.

Planning of small software projects

Feješ Adrián

Abstract. When someone encounters a difficult problem to be solved, first he does is to start thinking about possible solutions. If he founds a suitable solution then he starts focusing on its implementation. A software project can also be seen as a problem and we can define steps and resources that are needed to realize the project, which is a process of creating the project plan. Of course the larger the scope of the project and the more people involved is on its solution, the project plan will be more complex and increases its importance. How does the size of the project influence its planning? Is the approach to planning small project and large project the same? Searching for answers to questions like these is the subject of this essay. To find answers it is necessary to explain the significance of term small software project.

Communication by methods group solutions of the problem

Grznár Filip

Abstract. As a result of poor communication between teams and managers may be failure of the project. I think that communication in the team would improve if the team members better understand the thinking manager and the manager should understand the thinking of the team. Team members should have a sense of personal involvement. I think the solution is to use creative methods of group problem solving. These methods include brainstorming, brainwriting and Delphi method. I think these methods are relatively easy to use in terms of small teams for example in teams on the subject Team project taught at the Faculty of Informatics and Information Slovak university of technoloy in Bratislava. In this essay is to think about the specific benefits of these methods.

Plans successful software projects

Jašš František

Abstract. Currently the software is used increasingly. It affects almost all the human activities. This is reason why, demands its development is growing. Is required not only high quality, but also the shortest time of delivery of the finished solution. In order to fulfill this could be a lot of effort, often hundreds of people. Cooperation as large, but also smaller groups of people requires a high degree of coordination. Every single team member must know what to do and when it needs to be done, because of timeliness. That's why planning is important. It seems that for large projects with large numbers of people involved in the solutions, is planning necessary, but is also needed in small teams, where coordination is not nearly so difficult? How to plan projects that people are not overwhelmed, but to prosecute dates yet? How to plan to not lose too much time for planning? Answers to these and other important issues I will discuss in this essay. In addition, I will discuss some important causes of failure of projects from the standpoint of planning, and from a different perspective. These factors are also an integral part of software projects and should take them into account in the planning process.

Software quality assurance and refactoring

Jendrej Maroš

Abstract. In an essay dealing with the quality software of systems. I point to resource by which software can ensure software quality. The main resource for quality assurance is testing. I show here to the importance of phases before the start of testing. Quality assurance is not merely testing the software project, but also to prepare the criteria and requirements to be met by specified levels. One of the other resources for the better the quality of the software project is refactoring. Refactoring is changing architecture of the software without having to change his behavior, while increasing its quality. Applying refactoring in the project, but does not improve quality. There are various indicators by which detects whether the refactoring is appropriate and as possible is applicable.

Automation or no automation, this is the question?

Krajčovič Jozef

Abstract. With the rapid development of information and communication technology, software development has become increasingly more complex matter, that includes a large number of disparate processes and requirements. This has prompted the company to reorganize management of available resources and efficient use of support tools that are used in the software development process. One with possible ways how to efficient the software development process is to automate routine tasks, which are mede mostly by hand, what influences to quality of the product. In this essay will address the following questions. Can automation build of the software to increase the efficiency of the development team? Use of automation is also good for small teams? Answers on these questions in my subjective opinion and based on my experience with the supporting tools.

Monitoring? Yes, definitely yes!

Kráľovič Anton

Abstract. Monitoring as well as in practice means regular monitoring of progress in any software project. It's activity that has primarily helped by the software project manager for early detection of any shortcomings on his project, whether failure to meet pre-established schedule or not the client's requirements. Such monitoring is of course its advantages and also disadvantages. What are they and what is their proportion? As software projects ever shared and how to measure their "reliability"? In this essay I try to answer these questions.

Main risks in school software projects

Kukučka Jozef

Abstract. As well as any software project even the school one is threatened with various risks. These can affect its outcome. In general, main success factors in software projects are cost, time and quality. In school projects time is determined by fixed deadline and cost is not relevant because usually there is no budget. Therefore I assume that the only criterion for determination whether or not a school project is successful is by measuring its quality. In this essay I discuss which of the known risks are relevant for school software projects. Based on lists of TOP risks I determine which of them I assume to be the most crucial ones. Next I present which methods of risk management I think are suitable for use in this kind of software projects. They should be simple and effective. Students have often lack of needed skills and this should be considered in choosing techniques and practices.

How to effectively improve the quality in student projects?

Lajčin Tomáš

Abstract. The introduction of this essay deals with definition of quality in software projects. It is not easy to define quality in student software projects. In fact, it is a demanding process. The main idea of this essay is to think about ways to improve the quality of student software projects. Improving the quality of student projects is problematic, because the environment is different and traditional large commercial software projects rules for quality are not applicable here. Using standards for ensure the quality in student project is not as easy as it seems. Student projects have smaller range and they are affected by lot of new factors. This essay is also talking about measurable quality in software projects and the standards are appearing here again. The end of the essay deals with the impact of software projects testing on its quality.

Support of software development in international teams

Lazový Michal

Abstract. The management of a team in software development requires extensive effort from project managers. Especially, when the project is spread across multiple geographic regions. The usage of international teams becomes a trend and therefore a great effort is paid to develop tools to alleviate problems which occurs with collaboration and communication in these teams. Generally, these projects are large-scale, where the aforementioned problems are even more significant and their solution is more difficult. The essay deals with the way how to support this kind of development and also the question, how to improve effectiveness of international teams. Software development in international teams causes several complications, which may result in project failure, degradation of product quality, or cost increment of realization.

Nothing over a good documentation

Macošínec Branislav

Abstract. This work shows why it is important to create documentation. Documentation is generally considered a necessary evil in the software development. My goal is to show that this is may not be good documentation and creating even a supports the process of software development hence the successful completion of the project. Consequently addressed the question: What is a document which contains? This work also shows how agile software development to build the documentation. Later in the document briefly outline what you should be good contains. The paper also addresses the question: Why do people need documentation. Additionally, this document contains the principles of documentation and its breakdown. At the end of the work I deal with documentation describing the distribution areas.

Risk Management, why not...

Staráček Ľuboš

Abstract. Altough the project is well planned, and the management tools are used, software development still carries a risk of failure. It's possible to minimize this risk by involving the risk management, but it's necessary to dedicate an appropriate attention and thoroughness to it. But some studies are denoting that, there are still a lot of companies at this time, which doesn't involve a risk management in their projects. Why this happens? Of course, there are also cases where risk management is not appropriate to use. But what deters project managers from the introduction of risk management in such cases where risk management is appropriate? How could this situation be corrected? These are the main problems that this essay will offer its own vision and its possible solution.

More communication channels doesn’t imply better communication

Turský Lukáš

Abstract. Nowadays we experience a quantity of communication channels, by which we are literally surrounded. Character of these channels may indicate an existence of universal communication tool. In context of this essay two extreme approaches for communication are identified and compared. Also an idea of communication plan as a certain basis for communication management is introduced. Based on mentioned approaches it raises a question on how to choose communication approach so it would ideal for small and agile project teams. Essay discusses an example of communication tools and possible usages of social networks as some form of informal and universal tool for communication. Consequently advantages and disadvantages as a result of using social networks in project team are described together with their limitations. At the end the decision to use social network as a communication tool is evaluated and the idea whether project members in general could be able to better communicate thanks to the social network is settled.