Baloga Jakub

Abstract. Most diverse personalities with various skills and experience meet when a group of people have to form a team and cooperate on a project. Many manager emphasize skills and experience when they pick members of their team. Not always do they place emphasis on the dynamic of relationships between team members. According to Belbin team inventory, there are 9 team roles and these team roles can show us, how will the team members cooperate, type of communication between team members, if the synergy between the team members will move the team forward, or conflict between team members will arise and it will hamper the whole team. In this essay I want to explore the interactions between the team roles, managers options for effective communication, his options to improve the assignment of functions in existing teams and to prevent possible problems between team members.

Why some teams of people can work together in a project to infinity

Demovič Ľuboš

Abstract. The success of the team project depends on many things - from the least significant to the essential aspects. Every success must overcome enormous variety of risks that should be detected the sooner the better by experienced risk managers. At the same time they should effectively and reliably evaluate how the imminent danger could be removed, or at least mitigated. The greatest competitive advantage in the project implementation is teamwork, which has extremely high strength. But in each team once occur social risks that could cause disintegration of the team. In this essay I would like to outline the main causes of team failure and concurrently I will describe how these reasons detect and remove. The team of people that can pull together can be very quickly the most successful in any sectors.

How agile development replaced the old dinosaur

Fritscher Eduard

Abstract. In software projects and also like in projects from other fields, planning playes a huge role. Correct estimates contribute to the succes of projects. In my esseay I have focused on the comparision of the traditional methods of estimating processes in planning which are usually used in the waterfall modell and the methods which are used in agile development. I have analyzed the state in planning management with the focus of estimation techniques in the waterfall modell and agile methodologies. I have compared methods and techniques in estimation and planning. I have tried to point out how the situation have changed after agile methods came to the scene. Also in this essay I am trying to highlight the benefits and the need that development team should be involved in the estimating and the planning process.

Measuring to better software or what are the ideal measures of software?

Granec Michal

Abstract. Every software product should try to meet the demands that are required from it and it should be as close to these requirements as it can. Software quality manager has to face several problems to reach such level of quality of product that is required. One of the ways which quality manager uses for controlling quality is use of software metrics. They can help us to measure important dimensions of the software and get more tangible idea of it, despite its internal complexity. Using software metrics is not absolute solution and we must be careful with this technique due to variety of pitfalls which can surprise us. In this paper, I discuss the general application of software metrics, but also the most common problems encountered during their use. I further discuss these issues and try to figure out a solution to these problems.

Monitoring software and so we just human beings

Jendek Tomáš

Abstract. Software projects nowadays can be too extensive considering workers and tasks. We need to manage monitoring of project, in order to deliver good product on time with profit. Monitoring technical aspects and factors of project is not sufficient and so we need to take care about monitoring human factors in software development. Programmer´s efficiency and satisfaction can considerably influence overall development result. Monitoring factors as task overload, email overload and work distraction can be used for early identification of problems and we can try to solve problems afterwards. Monitoring degree of human factors must stay in reasonable borders, because pushing too hard on privacy at work can lead to loss of motivation and productivity.

Healing of Bad Documentation

Kandráč Ján

Abstract. Especially in the early days of IT departments of smaller companies happens, that their documentation is underestimated. Documentation management is failing and time is showing that the situation is critical. The problem is in slow and low quality output, or other problems that poor management may arise. There can be found several solutions for such problems, but these solutions are often not based on reversing the bad situation, but on its prevention. Usually it is a description of the prevention against bad documentation or changing management which is necessary because of failure to comply project. How to heal the documentation which is really bad? Or how is it possible to grasp it at any stage and lead it into a success?

How to tell it

Kaššák Ondrej

Abstract. It is a known fact that a group of cooperating people can in appropriate specifications achieve more than individuals working in isolation. But how to ensure the right cooperate specifications and how to synchronize the team to real cooperation and to make the required output by effective way? One of important aspects in this process is to ensure the functioning of communication in the team. Without the sharing of information in the team, it could easily turn into a group of hindering individuals. Nowadays there are available many ways how to share information. But how much are the different ways appropriate for software teams? Is there a difference between communication used in teams working in one place and distributed teams? Which approaches are used by real software teams in everyday usage? And how much can we inspire by them in student team?

Small-time Versioning

Kříž Jakub

Abstract. Version control systems are in practice widely used to manage the source code in teams with many programmers. Using these systems in small or even one member teams is not so certain, because a single programmer does not need complex source code management. However, using these systems brings a number of advantages which help the programmer to create a better software product. There are many version control systems in use. They are usually divided into two quite different groups – centralized and distributed. Choosing the right system can be a difficult task which differs from one project to the other. In this work I describe my opinion on choosing the right type of system and usage of the system by single programmers and teams with a small number of members.

The Convenience of Prevention

Kuzmík Ondrej

Abstract. Test or not to test? If so, when, what and how? I use this opportunity to write an eassy to describe my opinion on the matter or at least a part of it. I describe my view on the connection between testing and quality. When testing is worthwhile and when it is not. Tests are usually made to reveal bugs in code and testing the requirements and functionality is often neglected. I try to bring my point on this issue, along with how good testing can make software better or oustanding. I also focus on who should be responsible for testing and the importantance of this person for the team.

It is always about people

Proksa Ondrej

Abstract. Currently, there are high demands on software development. For a team to succeed in fierce competition, it is no logner sufficient to be just good enough.The key member of the team is its leader, who is responsible for the realisation of the project, operation of the team, incuding teams comunication. Work and operation of a team allways depends on quality of comunication between its members. It is a challenge for the team leader to guide the communication in the right direction and to be able to keep his team motivated to succeed. In my essay I am reviewing different forms of comunication, their effectivness, and advantages and disadvantages of different comunication tools. In latter part I am focusing on proper comunication from the team leaders point of view, where I conclude with my opinion on intercontection between efective comunication and motivation.

Somewhere respected, elsewhere deprecated

Trebuľa Ján

Abstract. Risk management is an important part of software project management. Why is so difficult to implement theoretical principles of risk management in practice? Empirical study results, which I analyze in this essay could respond. Moreover, in this essay I present and consider modeling framework of development software project that is directed by objectives. Whereas can be this framework effective? For which teams is actually aimed? Reflections about similar issues along with potential future work are situated in final section of this essay.

Is that plan really so good?

Urbančok Maroš

Abstract. By the software development, especially large projects, planning should play a key role in the distribution of tasks. This area is evolving much faster than other sectors and the development brings with it many pitfalls. This progress must adapt the methods used in planning. But already in the plan developing, we can continuously check, if the plan goes to the wrong direction. Even before its execution is necessary to realize serious errors that could arise in planning. These are easily detected in the bud and thus later to eliminate or minimize their impact. There is a number of detectable errors. Some are serious and can threaten the project, others not. But they still can the project largely undermined.

Monitoring, team or individual issue?

Vandlíková Diana

Abstract. Monitoring is a key aspect for a successful project. Without monitoring the real state of the project many mistakes, about which we had no idea, could appear at the end. Each member of the team can hide his mistakes for a long time. It is not necessarily their fault, it is also caused by their lack of experience. We can look at monitoring from different sides, not only as monitoring parts of the project but also as monitoring the direction of the whole project and its state. Both sides are equally important. Monitoring cannot be the responsibility of a single team member -- the monitoring manager or the mentor, everyone has to do their duties. I highlight the personal responsibility of each team member and the need to communicate among team members about errors and the state of each component. This should be done at the team meetings, where the monitoring manager tries to motivate the members to communicate about the progress of their work. The tools for monitoring and an experienced mentor are beneficial, but they do not guarantee a good result.

How to face the risks in smaller projects

Villaris Vojtech

Abstract. Development of software projects is often linked with different outer or inner risks, which might cause various problems. There are several publications providing some guidelines and techniques for mitigating such risks but most of them are designed for large companies and are focused on bigger software projects. For this reason my essay is primary oriented toward smaller teams that are developing small scale projects. Its aim is also to transpose the process of managing risks to academical ground of semestral projects developed in teams. Therefore this essay describes main differences between large and small projects as well as risks that are considered the greatest ones in this area.

A Tale of Two Revision Systems and their Future

Višňovský Juraj

Abstract. Most of the software systems developed today are dependent on the use of version control systems. Version management is considered to decide success of projects, especially the large ones. This is due to increasing complexity of the source code of software systems. Therefore, the choice of a suitable tool for the version management is a crucial task. All tools for version management are characterized by two revision systems - centralized and distributed version control systems. This essay analyzes these systems, describes the selection of suitable version control system and offers an alternative idea to eventually supplement or replace them.