Essays collection 2012
Home Home SK
"planning"
Belanji Juraj

Abstract. When a man stands in front of a problem, the first instinctive thing that occurs to him is to create a plan to solve that problem. Although that plan is not formally written, each person creates a plan in his mind. For creating a software product, a plan is also needed. The plan is the cornerstone of creating a good software product. As each person is a unique individual, so must any new plan be unique. But is this really true? Is it possible to create a plan, which would be a blueprint for creating new plans? This essay identifies errors that occur while creating a plan. The essay offers a different view on universal planning, and shows that sometimes a universally created plan yields better results than a newly created one.


Beliansky Michal

Abstract. Every one of us is unique man with goals and desires after entire life. We usually lead up all our materially, mentally and human resources to achievement all of these goals. We are consciously or unconsciously managing a planning our life under the influence. From the point of view this plans can be compared to project planning. We plan more extensive operations to achievement our goals in advance and mostly alone, or with your family, our loved ones, team mates. Effective using of visualization tools which are full of functions isn´t any speciality. Current support planning tools offer to beginner many functions with which we can´t meet in ordinary planning.


Bisták Andrej

Abstract. The planning of a software project is one of the most important parts of the whole process, because without a good plan it’s not possible to manage the project, identify necessary activities and resources effectively and thus gain the satisfactory result. But plans are not the same. According to older theories, the result of a project was understood as a concrete state, that if was achieved, the project was successful. This approach had proved not to be the most correct and the most appropriate for the software projects. Modern understanding of planning accepts as a successful project also the set of points that create a cube in a space. This approach is called a semi-quantitative reasoning. This is and effective method for planning and forecasting software project and in addition provides the flexibility and ability to cope with uncertainty and unforeseen situations during software development to project managers.


Feješ Adrián

Abstract. When someone encounters a difficult problem to be solved, first he does is to start thinking about possible solutions. If he founds a suitable solution then he starts focusing on its implementation. A software project can also be seen as a problem and we can define steps and resources that are needed to realize the project, which is a process of creating the project plan. Of course the larger the scope of the project and the more people involved is on its solution, the project plan will be more complex and increases its importance. How does the size of the project influence its planning? Is the approach to planning small project and large project the same? Searching for answers to questions like these is the subject of this essay. To find answers it is necessary to explain the significance of term small software project.


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.


Jašš František

Abstract. Currently the software is used increasingly. It affects almost all the human activities. This is reason why, demands its development is growing. Is required not only high quality, but also the shortest time of delivery of the finished solution. In order to fulfill this could be a lot of effort, often hundreds of people. Cooperation as large, but also smaller groups of people requires a high degree of coordination. Every single team member must know what to do and when it needs to be done, because of timeliness. That's why planning is important. It seems that for large projects with large numbers of people involved in the solutions, is planning necessary, but is also needed in small teams, where coordination is not nearly so difficult? How to plan projects that people are not overwhelmed, but to prosecute dates yet? How to plan to not lose too much time for planning? Answers to these and other important issues I will discuss in this essay. In addition, I will discuss some important causes of failure of projects from the standpoint of planning, and from a different perspective. These factors are also an integral part of software projects and should take them into account in the planning process.


Kuka Radovan

Abstract. Planning is undoubtedly very important. I tis said that i tis better to have a bad plan, as have no plan. This applies not only for managers, but also for developers. They should plan work on theyr tasks. This essay provides a way, how to efficiently create personal plans. It also suggests a method to simplify time estimation.


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.


Neslušanová Lenka

Abstract. Common people can imagine planning like a notepad where they can write important dates or like a phone reminders, which beeps in an important moment. The same concept also includes complex processes which keeps order and control of the huge IT companies all over the world. Maybe not everyone gets in the organization of that size in his life, but planning is an important element of any company and in some way we use it daily in real life. The main idea of the essay is focused on selected factors influencing the planning and their different involvement in agile development and the the waterfall model. I would like to show what are the advantages of one approach over the other in dealing with these factors, or which should be focused in each approach more or less.


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.


Left Separator
monitoring software project metrics function points plan planning software product risk management test driven development error effective communication sofware metrics software development team problems development software quality development support management extreme programming pair programming Scrum communication relations control progress subversion git critical path method project planning estimation agile development risks motivation requirement collection testing use case points support tools support tools outsourcing team size estimation version management quality cooperation risk documentation project software versioning conflict