Project monitoring is like attending to a baby

Baďura Filip

Abstract. Every day thousands of people work on development of thousands of software projects. To insure, that a reasonable cost and adequate time are spent on development of these projects, it is necessary to control this development. And it is part of management of project – monitoring, that serves to us, so that we don't waste a time and costs. Monitoring of project helps us to keep project on schedule and avoid unnecessary problems in its development. However, if we want to monitoring project, we need to determinate how to do it, what to look for and which metrics to use.

Forus Samo

Abstract. Customer participation is one of best practices in Agile software development (a group of software development methodologies based on iterative and incremental development). Many software projects fail because customer participation is insufficient. Both software project managers and customers must understand that customer participation is necessary for a project to success. On the other hand, customer participation must not be overused, because the project may fail either. That is why some parts of project need user participation and some must not use some. Project managers must take into account important factors affecting customer participation, such as his or her participation style, relationship, communication style, availability and location.

Control the future of Scrum projects

Hlaváč Marek

Abstract. The future of software projects is important, but often forgotten and underestimated topic. From the perspective of agile development in the context of Scrum projects it`s a significant and indispensable part which is pointed out in each development phase. A successful future is assured through project monitoring and controlling. The aim of project monitoring and controlling is early identification of risks and their early removal by using appropriate techniques and metrics. This is the reason why there are so many project failures. For Scrum processes this opens up new possibilities in the selection of specific techniques for different situations. The point is to record essential values that allow us to monitor the status and progress of Scrum projects and their dynamic nature. From this point of view we can define the questions with competent answers which are a prerequisite for future control of Scrum projects. What are the ways of monitoring Scrum projects? How to detect potential risks? Why you should be careful in project monitoring? Where lies the power of project controlling?

Which schedule technique is the right one

Horváth Róbert

Abstract. Planning and scheduling are the activities we do in our everyday life and oftentimes we do not even think about them. Those processes take place not just in our life, but in software project development as well. To create a quality schedule, which is a necessity for further stages of software development, we can choose from several methods. It could be hard to choose proper method, which fits our project specifics, just by its definition. In this essay I describe my opinion on which method to use based on project specifics. I focus on their advantages and disadvantages. Problem is that choosing a right method does not guarantee creation of a good schedule. It is easy to make mistakes in the process, which could lead to failure. Therefore I identify the most common mistakes in process of planning to help managers with avoiding them.

Main risks in school software projects

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.

How to effectively improve the quality in student projects?

Lajčin Tomáš

Abstract. The introduction of this essay deals with definition of quality in software projects. It is not easy to define quality in student software projects. In fact, it is a demanding process. The main idea of this essay is to think about ways to improve the quality of student software projects. Improving the quality of student projects is problematic, because the environment is different and traditional large commercial software projects rules for quality are not applicable here. Using standards for ensure the quality in student project is not as easy as it seems. Student projects have smaller range and they are affected by lot of new factors. This essay is also talking about measurable quality in software projects and the standards are appearing here again. The end of the essay deals with the impact of software projects testing on its quality.

Estimation techniques of software projects planning

Pszota Dávid

Abstract. This paper describes some estimation techniques, which are used in software project planning and scheduling. It also provides comparison and information about advantages and lacks of the described techniques. Here are given some recommendations for better estimation, including the historical data analysis. There is defined the need of discussion between planning management and the members of the developer team.