Abstract. Agile methods have being established as an alternative to the classic methods of software development. Reasons of their success are discussed in the first section of this paper. In the same section are discussed basic characteristic of agile methods also. One of the most famous agile methods is Extreme programming, which is discussed in the next section. Second half of this paper is dedicated to scaling of agile methods, using agile methods in large and distributed projects. Published experiences and recommendations are discussed in these section beside experiments in this area.

Abstract. With a demand for increasing complexity during the design of software systems, the distributed system or component design model has become a standard solution. Distributed software teams are confronted not only with the design phase, but also with mutual coordination and communication with the effort of successfully achieving their goal. It turns out, that the aspects like communication, coordination and informational awareness have significant effect on the overall performance of a distributed software team. A wisely chosen communication technology has a strong positive impact on the aspects stated. In terms of team coordination the concept of coordination authority has proven to be essential with a major effect on the coordination process efficiency increase. The actual value of coordination authority is notable especially in problem situations, which the project may encounter during the course of various circumstances. This paper presents the results and conclusions from a study of communication management of distributed software teams with emphasis on communication technologies and essential factors affecting performance of a distributed software team. Attention is also paid to the analysis of the distributed software team concept, particularly its relevance and characteristics.

Abstract. In this „Team era“, problematics of the teams and the mutual relations of their members are currently being the object of a lot of research. The interactions in a group and its dynamics belong to the area of group psychology but a good manager or a team leader should be aware of this topic. One of the most important parts of these relations that we should focus on, is conflict. It is very important to understand what is a conflict, how does it occur, what phases does it have and how solve these situations or how to avoid them. These questions are handled in the first part of this essay. The second part is focused on the means of minimizing of the factors, which cause the conflicts, namely two roles in the team – the programmers and the testers. There are also described some situations, which make pressure between the two mentioned groups and some possible tactics of minimalizing them.

Abstract. Everybody knows that people tend to make mistakes, but no one can predict when and what exactly will it be. During last few decades new techniques are proposed to reduce errors and increase effectiveness of software development. Despite all efforts, many software projects still fail. This article tries to shortly describe and explain few reasons why, and gives a summary of what can we do to cope with it.

Abstract. In order to beat the competitive firms is necessary to produce qualitatively comparable results, but in shorter time and with lower costs. This paper is concerned with improving software team productivity in order to achieve better work effectiveness and qualitatively better results. It is pointing out some basic productivity affecting aspects and discovers some ways how to improve it as well. Therefore we give team coordination due attention and we describe some ways how to solve coordination problems. With coordination hangs together communication in team as well. This paper deals also with team member productivity and with factors that affect it. The team member productivity influences the whole team productivity. It depends on his conscientiousness, skills, working conditions and motivation.

Abstract. Many software projects face difficulties because their monitoring relies too strongly on subjective information from the team members. Deviations from planning are often recognized too late. Automated project monitoring can alert managers on coming problems and allow them to take essential precautions. Therefore the key point during monitoring progress is visualizing real project state automatic and anytime.

Abstract. To survive on the contemporary market, a software company has to master a process of transition towards the use of new technologies and tools. This need is consequence of constant emergence of new technologies, which must be used in the development process, either they are required by the problem we deal with in the project, or are required by customer. Management of this process is not trivial. There are many risks associated with it. To eliminate them, we need to apply specific procedures and tools. This essay deals with causes of need of new technologies and tools and main risks, which are associated with transition towards using them. Later on, it presents particular management tools that project manager can use to deal with risks.

Abstract. In the current software project development trend as one of very important activities project management is getting into spotlight. It contains several pieces trying to ensure the organization, planning of projects and to allocate the main executed parts. Planning and estimating is one of this pieces which is this document dedicated to. The stress is put on clarify the planning process from more points of view. In fact it consists of some series of simple steps which can be repeated several times. Another view of this is dividing the process into main processes and supporting processes. Main processes consist of the creation of schedule and budget estimation. Supporting processes include for example risk analysis and management. Estimating is divided into four steps: estimating the size of project, the effort, the schedule and project cost. Next are the opportunities of project estimating. The best way is to use the know-how from previous projects, if there are any. If not, there can be made use of often used practices, or mathematical formula. At the end possible reasons and effects of underestimating projects are shown. There could be many factors like in haste made weak plans, underestimating the size or effort of the project.

Abstract. Quality definition differs from one quality expert to another. Document discuss the problem: what means quality for customer. Quality measurement metrics and the need of quality measurement are noted here. Then subprocesses of quality management process (Juran’s trilogy) and essential quality tools used for increasing quality are presented. I am trying to answer the question: Why are quality improvements needed and how certificates are influencing end-product quality. At the end are effects on project result analyzed which consists of quality income and quality costs.

Abstract. In present times the most software projects are not finished with success. It is dependant on bad relation between customer and programmer, mostly on communication relations. In this essay are characterized the ways of communication between customer and programmer, which can increase the chance of project success.

Abstract. Risk analysis and management in software projects is still on marginal interests of management. High failure rate of projects proves, that management should revaluate this irresponsible access to risk. This paper presents ProRisk Management framework, that describes risk management method in software projects and covers whole life-cycle of project. Paper goes through individual phases of the framework, from risk identification, through model construction, his calibration, computing risk values, till developing action plans to prevent risk occurrence and monitoring and maintaining process of the framework. Thereafter devotes to valuation of this framework and his benefits and disadvantages for managers and organization.

Abstract. The choice of appropriate people into the project has an large impact to its success. The task of project manager is to analyze all needed information and to make appropriate team structure to be able to manage the project into successful end. In this essay I describe some factors which affect the decision of project manager in case of team organization.

Abstract. Management of software system is an essential part of development of a new software product. It‘s hard to imagine how could we control and coordinate a large project, which includes many teams, without any software system management tool. However, simply buying a tool a putting it in a place doesn‘t mean automatically success in project. In this article are mentioned main goals of software management and I offer some aspects, which should be considered before deciding for some tool.

Abstract. Software team is a group of people, which has common goal, and it is to develop a product, by the customer’s requirements. Team of people, it can be small or large, is not only group of permanent people in the process of project developing, it is a dynamic formation, it makes changes. On team changing, many factors are applying, which causes team changes. People in the team are changing too. Competencies and roles of people in the team has changing in development process. Management of this process is very important in viewpoint of finishing the project successfully and for manager is management of human resources one of the most important activities. Essay is thinking about team process and his effect to management.