Adda MichalAbstract. There are many reasons, why software projects fail. Poor communication between developers is one of them. Poor communication is the reason of problem, when developer doesn’t have overall overview of project. Without the overview, he makes wrong and meaningless choices. This essay proposes the remedy for this problem in form of organizing stand-up meetings. But to gain positive results from stand-up meetings, we have to organize them correctly. In this essay, I am contemplating and giving answers for basic questions, which every manager should ask himself, before he starts organizing this kind of meetings. Although stand-up meetings are pretty easy to understand, if we don’t avoid some pitfalls, we can lose all of its benefits. They can actually become burden for us.Bado DávidAbstract. 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.Blšták MiroslavAbstract. 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.Bystrický MichalAbstract. 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.Kasala ŠtefanAbstract. 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šš MarekAbstract. 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.Kostolanský JurajAbstract. Technical documentation, user's guide, source code comments. These documents are considered an essential part of a software product. However, writers often spent much less energy to create them than they deserve. Although good documentation implies more satisfied customers, saved significant time and money, it is still considered as a necessary evil more than as a way to simplify own work and to improve the quality of the final product. In this essay I focus on the need for documenting software from multiple perspectives, I think about the concept of quality in the context of documenting and I describe the basic mistakes made by the documentation writers.Kucsera ViktorAbstract. The essay deals with the effect of team members’ quality on the final software product. The choice of one’s role in the team is being connected to person’s technical skills, while the social skills are believed to affect the whole team performance in general. The main idea is revolved around finding the ideal characteristics of a person to fulfill individual software project metrics. In the end, a quality teamwork is described as an element, that changes a group of individuals into a cohesive team.Mydla ĽudovítAbstract. Usually there are many people working on software projects. The whole team of employees. Each and every person has unique abilities, talents, experience, motivation and can contribute those, that project is finished on time, in desired scope and quality. On the other hand our human nature makes us volatile, with restricted knowledge and prone to various diseases, which makes us different from machines. Despite these facts I would like to explain, why I hold the opinion, that the core of risk management is care about people in our team. Taking measures to select right people, being supportive and motivate them during the whole project life cycle. And why this role should be mostly inspired by human resource management.Plank MartinAbstract. In the domain of project planning, there are various methods, which help us to get the most precise estimates of task complexity or create the best iteration plans. Likewise, we can exploit many software tools, which help us plan correctly. Nevertheless, in this essay, I want to discuss about people, hence just they are those, who create successful or failed project. And I suppose that the success often depends on a good project plan. But the plan is created by people, too. I want to state that planning is not issue only for managers. Every project stakeholder should be included in the planning. I mean not only the customer, but every developer that works on the customers’ requirements satisfaction.Škoda MatejAbstract. 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.Tomčo MarekAbstract. Software development was since the beginning dynamic process full of changes, adjustments and compromises. Development of complex software system in a team consisting of dozens, sometimes hundreds of workers would not be possible in such an environment without good development support. The increasing pressure from competitors in the industry makes companies find better possibilities of bussines. Transfer of development parts to foreign subsidiaries brings big benefits, such as increased speed of development or improvement of quality by correct distribution of tasks. However, this solution brings many new challenges due to the impossibility of direct communication, diversity of cultures and time zones. This essay talks about importance of development support in such environment in both, general thoughts and practical examples from experience of professional software company.Uhrin MartinAbstract. Planning software project is a key aspect in the field of managing development of a project. In the beginning everybody wants to know a release date. This can not be said with certainty and good estimate is just a matter of experience, coincidence. That’s why it is important to know how to effectively use the time. Agile methods give us good pieces of advice how to accomplish this and that’s why people start using them. People keep searching for better ways to develop a software, therefore new methods arise. We are going to have a look at Scrum and Kanban, think about their advantages and disadvantages and try to find a way to make the most of both when it comes to developing a software.Zboja TomášAbstract. Pair programming, known from extreme programming, was researched in various fields. This essay aims to look at pair programming how it relates to the quality of developed product. It identifies fields of quality of software, and later focuses on them. These are primarily standards during software development, the consequent quality from them, which should be part of requirements. A large part is dedicated to product errors – errors created during the implementation phase. Some sources of investigation indicate that pair programming has a negative impact on software's quality. The majority thinks the opposite, though. The essay contains a reflection, whether the measurment that indicates the negative impact is correct. Althought, generally, the acceptable result is, that this kind of programming is appropriate in terms of quality, there's a reflection on which kinds of software are the most suitable to be created with pair programming. It also states the conditions that would help to achieve the measured result - improved quality.
|