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.

Sprint is enough for small, big required two plans.

Bohunická Ivana

Abstract. Planning is necessary part of software development and defines project direction from its beginning. Created plan lives with project its whole life, so it is necessary to prepare really good plan. In the essay, I would like to remind, that plan creation it not easy and it brings a lot of problems. Fortunately, many strategies of planning exist. Interesting strategy is the way of two plans- one pessimistic plan for customer and second optimistic plan for developers. Another strategy is agile development and its Scrum method. Scrum is oriented on humans and their relationships, processes are low-grade in this method. Effort of this essay is to estimate these two methods, compare them and recommend them depending on project type.

Agile software development impact on software quality

Calík Jakub

Abstract. Every software developer is trying to create software with best quality. Quality is not something that can be easily measured by the number of lines of code. There are several aspects that determine balance of the overall quality of software. Several methodologies and models for software development was made in order to create software product of good quality. However, not all of the methods and procedures of software development, place equal emphasis on all aspects of quality. While some aspects can have more weight in certain model, others could be put asside completly. Lately, become very popular agile development model. In this essay, I will try to explain how agile software development influence software quality aspects and how it can be improved.

Usefulness of monitoring and agile software development

Kollár Adrián

Abstract. To facilitate planning and improvement of monitoring of the development process, there are various metrics that try to measure a product or process itself. Software metrics, however, suffer from some problems which arise from the nature of the software itself. The essay will explain the nature of these problems and it will try to answer the question about contribution of metrics to software development process. An important issue is the agile software development, which is used by more and more companies these days. In accordance with the agile methodology, decisions are made by professionals and rely mainly on intuition. Recently, there were various modifications of metrics used for the needs of agile development process. If these metrics have to be meaningful, they have to be modified to reflect the agile development methodology. Can these metrics be beneficial? Is it useful to use them?

How much time should be devoted to the creation of documentation in agile development?

Láni Marek

Abstract. The problems associated with insufficient documentation have to be faced probably by 99% of programmers if not by all. The creation of documentation is not a difficult process of software development, but this process is generally not met with much likes. Even modern approaches to software development pay limited attention to it. Such an approach is also an agile development. Its motto says: "Working software over documentation" and its answer to the question of how much documentation is necessary is: "Just enough." However, examples from practice show that documentation is a very important part of a software project and there are instances where a working software can not exist without it. We also try to define how much documentation is "just enough" and we discuss the patterns of documentation related to agile development. These patterns are Fake documentation, Timestamps, Project dictionary, Electronic backup and Distinct activity. For each of these models there are provided examples under what circumstances is creating of a specific type of documentation favorable, and what problems will it help us to avoid. We also discuss the possible ways in which it could be improved and outline the pros and cons of each solution.