Essay Collection 2009

Abstract:Managing software projects is becoming more and more complicated by the continued increase in the complexity of software systems. Due to limited resources, software teams demand tools to better manage their projects. In this essay, I focus on software management support in a smaller team. I use my experiences from working in a team on subject Team Project on the Faculty of Informatics and Information Technologies at Slovak University of Technology in Bratislava. Based on my experiences, various support tools are described. Explanations, how a team should choose its support tools are given, together with what is considered to be the most important when choosing them. Finally, other methods how to support software project management are presented.

Abstract:Risk management in software development is an essential part of the whole process and therefore it is necessary to allocate enough time for it. It is possible to avoid some risks with proper risk management. However in some cases risk must be taken, because it is not possible to avoid it. In that case more time has to be spent for this serious part of project. Risk management can be divided according to expected length of its duration. Some risks in a short-term project may not cause problems in a long-term project and vice-versa. This paper will discuss and analyse some risks from my experiences in the work and in our team project. This project takes place on the university field. Then question „Why is risk managment in short-term project important?“ will be settled. It will be proven, that risk managment should not be neglected.

Abstract:Production of software projects in team use to be sometimes difficult not only due to requirements or complexity of solved problem, but also due to personal differences of team members. Because exist many approaches to identify psychological type of man and studies researching relationships between psychological types in collaboration on projects, it is required to use these information and apply them in solving problem of increasing quality of relationships, communication and results of work. In future cooperation will be whole team working much better, than it would be working without these experiences. By solving the problem of confrontation of team members with different psychological types, we will be analyzing in this work.

Abstract:Actual state of software project often varies from projected state during its life. There are number of factors that cause this problem and it’s not ever possible to take them into account at the time of writing the plan. Properly implemented software monitoring makes it possible to detect deviations soon. Because of negative economic impact of these deviations, monitoring provides valuable information to the management to correct them. Essay deals with the process of software project monitoring, important metrics as well, evaluation and usage of collected metrics in management.

Abstract:This essay focuses on topic of project planning in conditions, that are not ideal for software development. Author explains how to overcome obstacles, that might be caused by several reasons. These reasons might be – underestimation of efforts, insufficient knowledge of project domain, or time pressure. In such conditions, there is not easy to create comprehensive and reasonable project plan. In essay author tries to analyze strategies that can reduce, or eliminate problems, which are caused by inappropriate project planning. Author also discusses the topic of replanning and inexactness in planning. In the conclusion of essay are mentioned theses which can be useful for creating flexible project plan.

Abstract:This essay is focused on managing human resource in specific conditions. My goal is to bring different point of view on software project. In the scope of the topic I discuss common problems, such as tracking tasks or assigning responsibility. My ideas and know-how is mapped to useful tools, which can be used to support project management. I tried to solve well known problems, which may occur in distributed projects where co-workers work in different geographical places, especially in their home. This essay also provides vision and design of tools which should effectively help in mentioned scope.

Abstract:Some years ago, SE has been described as a branch concerning of theory, methods and tools needed for software development. Nowadays we know that there is much more to endow with in SE, not mentioning branches merging tendency. Software project demands beside high technical rank also a focus on people who form it. Those are bearers of ideas and technology, but also personality traits and world reception. This reception changes the world and therefore the project as well. In this essay I endow with the influence overview of specific personality traits on project fruitfulness. I examine the influence of a team leader and communication on the team mood that rules in the team and considerably designates what the final product shall be. I try to offer a different view on the notion conflict, the way I try to show the coherence among conflict, emotion, introspection and motivation.

Abstract:Management of quality is very important in the development of any product. In the software engineering especially. Satisfied customer is our goal and satisfaction is largely influenced by quality of the software. The essay discusses the methods used in the field of quality management, focusing on perhaps the most popular method - testing. From the lot of literature and lot of opinions about testing I want to choose the best practices of what, how and when to test software products. Methodic of developing software based on testing – Test Driven development will also be analyzed. I will try to point out the advantages of this modern methodic used in modern approach of developing software – agile and extreme programming.

Abstract:Paper brings a look on the field of detection and solving the problems that appear during software projects. Several examples are discussed. Paper focuses on scope of confrontation of human approach with automated analytical methods for project support.

Abstract:The paper discusses planning in general and the need for planning. It presents several common mistakes related to planning in projects and explains their implications on project success. Although it focuses on software projects, the need for planning is explained on several real-life examples. The paper also proposes several ways of avoiding these mistakes.

Abstract:Software development brings a lot of different risks, which with wrong technique usually leads to worse quality of final product or violating scheduled plan. This paper aims at identification of the most important reasons of creation of these risks. It also tries to find and advise the best tools and techniques for analysis and management of risks, while the main object of interest is a team project with lesser team members. Risks are noticed in the context of impact on plan fulfillment and resource management. The paper should answer questions like: how the risks develop? How to properly identify and effectively eliminate these risks? What support tools for risks management exist?