Essays collection 2012
Home Home SK
"risk"
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.


Mihalik Adam

Abstract. The essay points out, that despite the advanced development of information technologies we are not able to meet all project risks. At the same time it provides insight into the risks to the customer as one of the most dangerous risks of the project. We determine the percentage of most frequently used methods of the risk elimination and we upgrade them for a finding the specific issues related to customer requirements. We analyze the success of the most common methods of identifying risks and compared with the success of applying decomposition method to the same problem. Using the decomposition method we determine the riskiness of specific project areas, thus we can predict the formation and changes in customer requirements.


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