Traditional or agile? Why should customer care?

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.

Hudačinová Silvia

Abstract. In this paper, we described the relationship between customer and manager. We deal with various management practices, metrics and methods for monitoring a project and their attitude towards customers. Discusses the customer's attitude to monitoring the project and why CBR is important for project monitoring. This paper mainly describes a model for project monitoring with stakeholders, whitch describes the idea of monitoring the project with the collaboration client.

Out-of-date documentation is useful, too

Ogurčák Filip

Abstract. Technical documentation is an essential but often ignored part of the final software product. Ignored in the sense, that attention is given mainly to the functionality of the final product and for regular updates of documentation no time remains. Documentation, however, is not only for final customer, but is also important for programmers, development team leaders and company management. In this essay I would like to focus on the fact, that out-of-date documentation has still enough additional value for customer, programmer and manager controlling the progress of the project. In this case is important developed product as a whole, connection between modules and representation of general functionality. Finally is showed an absence of a standard, which would make technical documentation unified and simplified.

Successful planning

Rešetár Jozef

Abstract. The majority of people dislike looking to the future and instead of this live the present as much as they can. They don’t think what follows their present actions. They don’t plan, it bothers. They don’t want to plan because this moment is for them the most they have. They don’t want to lose the moment they like because of stupid plan making. They don’t realize that planning is very important part of everyday working and although they plan simple things like - what I am going to do today – this is the most they can do. More difficult and important plans are done by them very rarely. They postpone making difficult plans to time when plans is not in need. Then they have to solve problems on the fly. Paradox is that planning is not timekiller, but can safe lot of time when it is done. The disgust to planning is testified also in software development. This fact leads me to the theme of this essay – Success planning. What is important for successful planning? What type of impact have good estimates on planning? How to face causes of failure in software development in terms of planning and scheduling management? And finally, why we failed to submit first prototype of out application in team project subject? You can find answers to these questions in this essay.