Essays collection 2012
Home Home SK
"risk management"
Bielik Pavol

Abstract. Despite the high awareness of the importance of risk management and theoretical basis in this area, studies show problems in its practical implementation. This fact is reflected by high number of companies and student teams not using any risk management techniques, even though, they are well aware of the appropriateness of their use. What are causes of the current state and how can we change it for better? One possible approach is using games, which brings an innovative approach to software engineering, helping students apply theoretical knowledge to real life situations. But is it effective and if so, where do games fit in the current scheme of education? These are the questions we discuss and answer in this essay.


Bimbo Miroslav

Abstract. Nowadays risk management is common part of software project management. It describes how to identify risks, on which risks to focus and what to do with them. Risk management is needed to be aplied on on every – even very small – project. Our team project is large enought to have risk management formalized. There is avaliable many methodologies for risk management in software projects. Which of them is most appropriate for our team project?


Franta Martin

Abstract. The essay deals with risk management for Web-based projects. Web engineering, as a separate part of software engineering, has its own specific assumptions and resulting risks. Web applications creators faces to decision how to manage these risks, promptly react to user requirements at the same time and not losing market position. In the introduction, essay appoints possible risks involved with Web-based development. It focuses on risks of leading development and compares them to risks resulting from technology specifics in given environment. The essay presents the key questions that product owners and managers should pose before development begins, or before the final product is deployed. Risk management is approached with question how to lead project dynamically while responsibly.


Kubis Viliam

Abstract. Selecting the right method of risk management is a crucial decision that needs to be made at the beginning of a project. Incorrect risk management method choice can lead to complete failure of risk management process, which will significantly endanger the succes of the whole project - it can lead to a complete haltdown and failure of the whole product. Analyzing and thinking about a particular risk management methodology to choose is one of the toughest decisions a project manager has to make. According to what criteria can a project manager choose the right risk management method? Are all presented methods pricipally equal and usable for each and every project? Is team size and geographical structure significant and important in the decision making process? We strive to answer these and many other questions, or at least provide hints which will lead to making the correct decision - and in turn success of the whole project.


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.


Lezo Andrej

Abstract. In the next chapters I analyze broader look on Riskit method and reason, based on case studies and avaible materials if it can help in risk management. Its main properties are structural process and complexity. It contains many same steps, which couldn’t bring us to the desirable result. Of course, it’s important to choose correct and appropriate way of usage for this method. Main reason why its usage is applicable and only large companies benefit of it is that too much effort devoted to every step is required.


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.


Vacula Matúš

Abstract. Software project in its life-cycle encounters numerous risks. One of the considerable risk are human resources. Each team-member has his own individual skills (e.g. programming, organizing or communication) and individual commitment to do his best. It is very difficult for manager of a newly formed team or fresh manager of an already existing team which he is not familiar with to estimate the capabilities of the team when a crisis shows up. This situations can be prevented by performing a stress test on the team. Test would not only evaluate employees' performance but also identify the hidden flaws in the processes of the project. The test results can help to reach more precise planning and quality risk management.


Left Separator
monitoring software project metrics function points plan planning software product risk management test driven development error effective communication sofware metrics software development team problems development software quality development support management extreme programming pair programming Scrum communication relations control progress subversion git critical path method project planning estimation agile development risks motivation requirement collection testing use case points support tools support tools outsourcing team size estimation version management quality cooperation risk documentation project software versioning conflict