Who is responsible for the greatest risks of software project?

Blšták Miroslav

Abstract. Underestimation of risk management can lead to complete haltdown and failure of the software project. Risks aspects are present since first step of realization our project. Risks can involve minor or major scope of incidence, but their influence can cause big difficulties for realization or even completion of project. Risks implications can be present during liftetime. Risk management is very often omission, because it is difficult to identify amount of different situations, especially when the committal time of project comes. But, it is risk management, which can reveal potential problems and save lots of time and energy of all interested people related with project. In my essay, I will try to identify risks and problems which very often cause failure and unsuccessful ending of software projects and interested people, who are responsible for these problems.

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.

Will we prevent failures in software projects by educating risk management?

Gondár Jakub

Abstract. Risk management is important element in software development management. It seems that risk management is underestimated or is missing completely in many software projects. I wonder if this could be because there is lack of risk management in education. In my essay I deal with question, if educating risk management will help prevent disasters in software projects. Essay starts with introduction to risk management then I will deal with need of risk management education for software engineering students. I introduce some of educating methods from abroad, case study based education and interesting innovative method based on interactive game. At the end I summarize results of mentioned methods.

How on risks

Grega Jaroslav

Abstract. In today's world full of uncertainty, it is necessary to count with many dangers in each area. Such area is the development of software and information systems. In this essay I would like to acquaint the reader with the issue of risk management. The introduction will describe basic terms of risk management. Then moving on to the actual problem which I will apply knowledge of risk management in the subject team project. After a brief introduction to explain why risk management is important and why it is important to deal with it. Since not everybody knows how to deal with managing risk, I decided to bring this essay as I see it based on their own experience.

Teaching risk management

Kasala Štefan

Abstract. This essay is about risk management. It is very important, but also very often underestimated part in the process of software development. In this work we think over the reasons, why the risk management is neglected and the possible solutions using innovative ways of teaching and education of students. Theoretic preparation is often too much abstract. Possible solution is to practice teaching based on case studies and analyzing failed project. This ways of teaching provide space to think, discussion and show real reasons to students, why to take this part of management seriously.

Risk without a gain

Mančík Gabriel

Abstract. Development and coordination of the software project is a challenging and often risky process. Aim of risk management is to study potential risks associated with development, predict them and minimize the likelihood of their appearance. This work is centred on risk management associated with outsourcing project to offshore companies, where a whole new risk factors arise. I address the fundamental issues and challenges related to the specific nature of the relationship between client and offshore supplier. My work analyzes the issue of the proper choice of supplier, risks arising from communication between different cultures and the problems associated with the physical distance of both parties. For all the discussed problems solutions are proposed.

Are there any risks of risk management?

Pakan Filip

Abstract. Despite advanced technologies and support tools for software development still a lot of software projects fail nowadays. In recent years attention is turning towards risk management. Research in this field has shown that identifying and efficient controlling of risks may significantly decrease the probability of project failure. Practice confirms the findings of research and proves that risk management has already saved numbers of projects and large amount of resources. Although there are many undoubtable benefits of managing risks in software projects I will try to propose some drawbacks of risk management from my point of view in this essay. Furthermore I will try to identify and discuss what risks are closely related to risk management. Moreover I will offer some of my own ideas to eliminate risks of risk management in context of new and inexperienced team developing software system. The goal of this essay is not to discourage the readers from integrating risk management into their projects. The goal is to notify the readers about potential weaknesses of risk management and to propose them several useful hints how to manage risks even more precisely.

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.