Essays collection 2013
Home Home SK
"management"
Bystrický Michal

Abstract. The control version system is helping with backups and managing versions. However, there are many cases where usage of the control version system is a disadvantage. This essay concentrate on these particular cases. I discuss the control version system from the different perspectives and whether it is appropriate to use.


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.


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.


Kišš Marek

Abstract. Monitoring is an important part of a project management. We monitor with the aim to have a control over processes, that need to be adapted to occuring changes. The use of good methods for monitoring improves chances of successful completion of the project in the required time and budget. The term management usually presents a set of actions associated with a leading of a team. But we can also manage yourself for any self-activity. Methods used in this kind of management can be based on the methods of team management. The essay presents some prevalent approaches to monitoring and analyzes the possibility of using them to monitor activity of student of computer science during his semester, in order to improve effectivity of his work and increase his success.


Korec Tomáš

Abstract. Communication is one of the most important human skills. It is the basis of any successful collaboration. This essay addresses the importance of communication in software development projects. It refers to the underestimation of communication, despite the ever increasing level and size of software projects, because many times these development projects spread among several countries. It refers to the possible reasons for failure of software projects and to what degree is it a fault of bad communication. Essay describes effective communication as a basis for the success of each project. Furthermore ,it addresses the problems that often have with communication not only developers, but also managers. These problems are then reflected negatively on the success of the project, of course. Essay addresses communications style and personality of manager as a basis for effective communication, which is necessary for success of software project.


Kujan Jozef

Abstract. Nowadays we use the term usability more and more often in the field of information technologies. This term began to be used in user centered development. It was necessary to create this term according to some historical events. These events were mostly a reaction to demands of that historical era. But today it needs to be done by managers. Despite of great effort spend in development and innovation of web pages in terms of usability, the usability is still far back viewed ass quality attribute. There could be many reasons why it is this way. Essay describes this field and is aimed at motivating competent managers to act and improve software also by adding this quality attribute. There are also write some motivations given by historical events or showing todays success.


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.


Rais Jaroslav

Abstract. Total quality management has absorbed static methods of quality management and has integrated not only the focus on the software process and product, but also the focus on the external and internal customers. In other words, success is built on three pillars, namely the customer, the software process and people. [Phil Crosby] Total Quality Management is not controlled by any rules or standards (ISO), but it applies everything that can encourage good quality of the development of a software product. The introduction of Total Quality Management helps to build a good and flexible way to achieve the desired quality of a software product, with a focus on an employee and a customer from different cultural, religious and economic backgrounds.


Staňo Filip

Abstract. Communication is a base of every human coexistence and cooperation. In software development, correct choice of communication method is critical. This is the reason, why I will try to analyse and describe all common forms of communication used in software engineering. Main subject of this essay is local and distributed communication and their appeal on team performance. I claim that local communication is always an advantage. Subsequently I describe formality as a phenomenon in team cooperation and its appeal on motivation and oppositely on chaos in communication. Last but not least is analysis of synchronnous and asynchronnous communication method following with recommendation how to use them properly and in correct situation. In this essay I will describe all afore mentioned methods of communication in detail and also their final outcome on project results. Later I will identify usability of all this methods in certain situations as well as consequences of their incorrect use. In this essay I compare suitability of all methods based on number of people in team and also based on software development process phase we are currently in.


Škoda Matej

Abstract. With using agile methodologies of software development, quality of software documentation is low, often it has low priority and it is neglected. Developers consider it needless. Result of documentation is often unusable document. This essay speaks is about problems as low quality of documentation, forced creation of documentation or creation of documentation too late. It describes opinion of scrummasters to documentation creation at agile methods of software development and its importance for software projects. It describes process of documentation creation and tries to bring some solutions to those problems by using combination of agile and classic teams to software development. It also express to another concept used to documentation creation and it is automatic generating.


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