Essays collection 2013
Home Home SK
"risks"
Bado Dávid

Abstract. Nowadays a large percentage of IT projects fail. Because of that, many people are trying to find and examine causes of these fails. Research shows that one of the main causes of fail of software project is insufficient participation of customer on project. Essay talks about why it is important to monitor software project by customer. It points out that traditional software development does not support this trend and even creates obstacles for customer during monitoring. On the other side agile methods encourage customer monitor project and participate on it. Essay appeals to customer to realize, that he can minimalize risk of project failing by choosing development method and by his partcipation in project.


Danada Ondrej

Abstract. Organizations of the tertiary sector often have limited budget and that is why they have to develop their software projects at their own. This kind of projects has its’s own specifics and because of that there are different risks than in commercial projects of professionals. The purpose of this essay is to identify and briefly describe these specifics and compare these risks to the risks of ordinal software projects. The worst risk could be clearly considered the lack of staff, which threads more than in other kinds of projects and its’ consequences are bigger, too. Possibilities of avoiding these risks are also limited and it is necessary to look for special solutions. But some risks are because of some specifics, such as good domain knowledge insignificant and the thread is minimal.


Lihocký Michal

Abstract. Risk management is generally considered as an important part of software development, yet it happens very often that teams don’t support it. But how come that people are not willing to spend any resources to support risk management although they realize its importance? What prevents them to do so? What are main barriers in introducing risk management? Even after we successfully introduce risk management within a project, there are still many problems that we will face. What are the other problems we may face regarding risk management? Are there any recommended best practices in this field? Is there any concrete approach or model that would seem to be applicable in our project we develop within Team Project course? These are the main problems discussed in this essay.


Left Separator
plan schedule communication software project team monitoring agile development customer risks risk Scrum planning risk management version management management disadvantages quality software extreme programming pair programming motivation success support tools version control quality management documentation agile methods software development tasks software metrics team project documentation management project metrics waterfall model manual guide development support small teams usability testing software quality support tools development support management software configuration quality control version control system efficiency agile methods of software development