Annotation. Software project risk management is an important part of overall software project management. It has to be performed throughout the entire project lifecycle. Its main objective is to identify and treat unexpected risky events in the project, so as they a) never happen, b) cause minor losses. Risk management consists of risk identification, risk analysis, risk response development and risk response control. This essay offers a complex view on risk management phases and overview of the most important factors identified by experienced project managers. It also tries to cope with risk management in software projects like team project in study at FIIT STU.

Annotation. Agile methodologies represented mainly by extreme programming are considered as very useful techniques in development of small projects in changing environments. This fact has developed into a misunderstanding that core practices of these methodologies are not appropriate for other projects and are mistakenly considered as sources of project failures. They are being rejected without even knowing their true meaning. Nowadays is being shown that some of these practices are so rational, that they can have some positive effect almost on any project. So it is essential to identify their true meaning and consequences they are causing to be able to use them and not to reject them completely.

Annotation. This essay deals with introduction of term Virtual Software Company and has two parts: in the first part is defined term Virtual Software Company (Virtual Distributed Team) and are described the tools which are VSCs using. While describing these tools, I focus on those which are used to communicate, not those which are used to share the documents. Context of the second part is composed problems with which are VSCs facing and which are based on results of real researches in this area.

Annotation. The quality is with no doubt the most important part of the each product. The basic idea of this essay is to look more deeply into a concept of system quality, in particular, in the context of management of quality. The paper analyses the individual parts of quality characters. It discusses about which of them are important from the customer's view and from the view of the producer of the software. It examines the concept of an error and also contemplates about individual contradictions between the requirements of the customer and that of the software producer. In conclusion it describes the management of the quality as the system of quality control.

Annotation. This essay introduces the basic concepts of Software Configuration Management and describes different types of software tools for SCM. The different types of SCM tools are described from technical and from teamwork point of view. It handles the SCM impact on the project management too.

Annotation. This essay deals with software team productivity, mainly with the aim to increase the productivity. In the first part we analyze the impacts and factors that influence the team productivity. Particular impacts are quantitatively compared and the most significant impact - team capability - is in the next part more deeply reviewed. Within the team capability we pay attention to personality setup of a smaller team, where we take into the consideration suitability of various types of personalities for particular positions in the software team. This characteristic is described by Myers-Briggs Type Indicator (MBTI). Part of the essay is also the introduction into the personality psychology and more detailed description of MBTI typology.

Annotation. In today's ruthless competition the winner is always the one who makes the best estimate of the situation and reacts accordingly. This is also true for software engineering. This paper briefly defines basic phases of estimation process denoting the importance of reusing historical data from similar projects. It also tries to identify serious problems, which the estimators must face and proposes alternative solutions. Finally, it presents valuable tips and suggestions, which contribute to better estimates and eventually, successful project.

Annotation. The fault is inseparable partner of every software project. This state is caused by multiple factors. The most important one is distinctiveness of software development and its characters. We look at authors of faults and their experience. Than describe fault visibility and their consequences. Testing is one of domain, which we often downgrade, so we look at that reason and relationships between tester and programmer. The faults are directly connected with reliability of software product. The Musa is one of the main models of simulation faults in software systems. At the end we compare fault cost and relation between this value and some dependent factors.

Annotation. The latest trends in software development area suggest even more needs of presence of customer-developer relationship. The need to improve the communication between these two subjects is just a logical ending of resident concurrent struggle of corporations, trying to develop the product in the shortest time. This article is dedicated to communication problems between both of the mentioned subjects, communication levels between them, as well as the role of customer in software development by itself. The essay further deals with the agile methodics as a new trend of software development and explores the customer-developer relationship in extreme programming, the main representative of these techniques. In conclusion essay urges on existence of the customer-developer links which can in essential way make the software development in the future more effective.

Annotation. Despite the best planning, the best team participation and expecting all possible pitfalls, it seems that software projects are experienced to cause unexpectable problems. One possible way how to avoid unsuccessful project termination is to monitor progress of the software project. To be able to monitor development and progress of the software project it is important to create a plan. It is also needed to choose feasible metrics to measure the progress. Choosed metrics should not drive people to achieve better results in a measurement, but it should motivate them to effectively attain identified goals of the project. When the plan is ready, it is possible to ask, which planned tasks are already accomplished, estimate amount of tasks remaining and compare scheduled project status to the real project status. In case of difference, it is possible to correct the plan and aim the effort to the right direction.

Annotation. In this paper I took a closer look on process of development of a team from three different perspectives. As first view I used Bruce Tuckman "forming, storming, norming, performing" model, also mentioning the later added fifth stage "adjourning" which has a special meaning in terms of management. As second view I used Hersey and Blanchard's Situational Leadership model which also has four stages and I pointed out the similarities of stages of these two models. Tannenbaum and Schmidt Continuum is the last view. As next I described the managing tasks which are needed in different stages of development of team explained on model similar to Bruce Tuckman "forming, storming, norming, performing" model and I described in detail changes in managing a team using seven stages of freedom delegating in Tannenbaum and Schmidt Continuum.

Annotation. Complexity of management and development in software projects requires new technologies and software tools. These can be very helpful when designing complex models and are able to automatically generate source code and documentation, and other tools can help us to communicate with people participating in the software project. This essay focuses especially on those tools and technologies, whose purpose is to create and maintain software documentation or to make communication more effective. Project managers can and should choose among the available tools - this decision may have impact on the success of the software project. Which tools and technologies should be used? There is no simple answer to this question.

Annotation. The essay discusses conflict management in general - conflicts, their causes, solutions and prevention. Next, the conflict management theory is applied to team software development and explained on two examples - conflict between developers and end user and conflict between programmers and testers.

Annotation. Introduction and conclusion of the publication