Aufricht Igor

Abstract. This paper talks about the causes of software project failures and why agile methods of software development help less than they should. Author argues that a lot of failed agile projects can be traced to incorrect or incomplete implementation of given agile methods and gives his insight into causes of the failures.

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.

Communication support tools in start-up projects

Lačný Jozef

Abstract. Paper discusses benefits of using communication and management support tools in start-up teams and refers to pros and cons of using these tools. It does not bring final solution whether or not to use these systems, but encourages the reader to decide depending on team and project special characteristics.

How to perform more accurate effort estimation in software projects?

Maršalek Maroš

Abstract. Paper brings a look at improving effort estimates in software projects by using multiple effort estimation techniques. Several types of techniques are discussed and paper focuses on choosing the most effective combination as well as solving the problems involved with this combination.

Choosing the right way in the software version management

Michalko Pavel

Abstract. This paper explains the procedure for selecting the most suitable software for version control. For a few selected divisions of software projects is shown the applicability of each approach. It points to possible problems in the selection of inappropriate access of versioning system. In some cases, is expressed the author's own stance on issues and problems arising. The aim is to convince the reader about using software version control and the proper selection depending of the type of software project.

Minimum metrics for achieve success of software project

Obal Tomáš

Abstract. The author of this essay attend to the importance of monitoring software projects. Author proposes to add human-use reporting with metrics which are objective source of information. The introduction shows the possible ways of monitoring and resources for gathering metrics. For creating the plan is to use metrics included in the analysis, which must be measured to express the size of the project. The focus is on control and porogresu porductivity work in the development of software projects. The second section is devoted to monitoring quality control of source code with the complexity of functions and classes. By providing a proposal to use a minimum number of metrics to ensure good performance in project development.

How fear affects our projects.

Súkenník Ján

Abstract. Risk management in software projects is often being neglected. Main reason for that may be the phenomenon called risk-averse culture. Essay describes this phenomenon. Author argues that only one available solution to this problem exists. The solution is then discussed, and guidelines for risk management in software projects are suggested.

How and why to monitor the software project

Tóth Juraj

Abstract. Monitoring is a tool that is used for analyzing and gathering information about the project. It provides important data necessary for a successful project throughout the whole duration of the development. This essay offers essential insight and reflection on the issue of monitoring. It implicitly and explicitly discusses the methods of information gathering in the area of software projects and it also evaluates and compares them.