Essay Collection 2011

Abstract:There is still high percentage of unsuccessful software development team projects. Therefore, research about management of such projects is getting considerable amount of attention. Studies reveal that theoretical knowledge and technical skills of team members do not guarantee success of a project. Personality traits of people in a team are proving to also play an important role in team projects endeavors. Discovering which personality factors are relevant for specific tasks in software development is just one of the many fields of research. Using personality inventories such as Myers-Briggs Type Indicator and Five Factor Model, this essay provides analysis of positive and negative effects of different personalities on selected roles in small team projects. Great deal of research is being focused on the personality of project manager, while other roles are still short of complex theories.

Abstract:Software engineering recognizes several methods that are used in order to ensure that the output quality meets the requirements given by software systems. One of the methods is testing. Throughout time, due to the relevance and essentiality of this method, several different methodologies, approaches and theories were established. Therefore the issue of testing became more complex and hence more difficult to master. As a result, even in medium-sized projects, it cannot be performed by programmers and system developers only at the present time. Instead, software systems are subjected to specialized verification, which is focused on finding errors and weaknesses. The verification is performed by a specialized team, which outlines the results in reports. The professionals in the team are experts, who focus on the testing discipline only, and have to meet certain prerequisites in order to be qualified for the job. This essay deals with testing from their point of view. It discusses the justification of existence of such testing professions and explores various forms of testing and job opportunities in this area.

Abstract:In 1989 Harry W. Boehm identified top ten risks of software development. These risks are still actual. Conditions and the environment of a small project are different. Bounds between the team members are not strong. Their motivation does not depend on a salary. Mitigation of possible risks is crucial for the project success. The essay brings new view to these risks in a small project environment. We will try to identify, which risks are the most dangerous. We compare different methods to identify risks. We focus on persons and risks related with them. We use project risk analyze to improve project control. We discuss the risk impact on the project planning. We will compare classic methods of risk mitigation with optimistic planning methods. We determine the impact of both methods on the project plan.

Abstract:Project managers are people who are responsible for planning, distributing of tasks, and controlling the completion of these tasks in a project. This work is difficult, therefore it is necessary for managers to use support tools in most projects. These support tools help to create reports about tasks, help a manager to visualize the current status of project or estimate project's price easily. How does the usage of support tools affect the cost of a final product? Does it raise or reduce the price of a product which a customer has to pay for? Can the usage of support tools have an effect on efficiency of employee’s work? In this essay I want to express my opinion on these questions and introduce the reader to this field.

Abstract:It is a well known fact that communication problems between team members belong to one of the major problem in software development. Ineffective communication can extend the entire development process and cause many other problems and misunderstandings, which affect the final quality of the delivered product. Today we know several ways how to communicate and also we have today available many alternatives of support means to us that communicate with each other and allow easier. However, we often see in the behavior of developers, that extend to the more specific ways, and other ignored. In this essay I would like to describe a means of communication in small development teams, which involved developers prefer to choose and use, and indicate problems that are likely to use these particular compositions occur. Consequently, I would like to focus on opportunities as could be possible to reduce the inefficient communication as far as possible by using some effective ways of communication.

Abstract:Nowadays there is the development of information technology, technology generally and it demands for software product become more important. It is necessary to manage and coordinate project software teamwork. To be succesful we need good management and we can provide an excellent product to a customer. We need to know process, its state and objective judgement to be able to manage it. The important part of the management is using the right metrics, which can express the state of the project. The objective of the essay is to indicate which information can be won by the project manager from version control system and metrics, which can be applied.

Abstract:Planning is a very important part of client – developer communication and it takes part in every part of a project’s lifecycle. It contains estimation of project effort, resources and schedule. There are plenty of different planning methods and their success is highly dependent on project type and the project team. This essay focuses on comparison of various planning and estimation strategies based on different project characteristics that have the greatest impact on them. Because estimates change all over the project life cycle, it is necessary to be prepared for changing the early estimates. This essay describes various changes and risks, which result in changing of plans and estimations and following the plans schedule on the project’s result. The last part of this essay is devoted to application of the whole analysis to our team project.

Abstract:Nowadays, risk is all around us. Every day we are in contact with dangers, from which it is impossible to escape. There is the same problem in software development. What's more, software development can often be accompanied by an even greater risk. In this essay I want to point out the risks that influence small team that solves the two-semester project. I follow the risks which belong to list of TOP 10 according to Boehm and I try to express my views to various dangers that threaten the project. I discuss these risks identified in the list of TOP 10 from the perspective of a small team. I also point out different strategies that attempt to minimize the risks arising in the software. First of all I try to identify what kind of strategies to use in specific situations. It depends especially on experiences of the team and nature of the project.

Abstract:SCRUM is presently a very popular methodology for software development. Like any other team, the SCRUM team needs to monitor it's projects to be successful. In this essay I focus on metrics that can be used when monitoring projects in SCRUM teams, especially the ones that can be used to enhance team planning. I show how usage of even a small number of metrics can lead to a sufficient number of useful results. This essay also clarifies how to evaluate measured outputs correctly, what questions to ask and how can one apply discovered knowledge to team management.

Abstract:Software projects are getting more and more complicated and complex. Hundreds of people work on them on a day to day basis. It is no longer a secret that skillful management is the key to a project being a success. Projects are made up of people – one who can guide them is on the best path to success. This is the main reason why project management tools are on the rise. These tools provide a large scale of options for software project management. They can help in making software development processes much more efficient and feasible. If used right, they can bring satisfaction to all involved parties. They provide tools for task planning, task assignment, human resources management and communication. This essay discusses the adoption of these tools in small and medium sized teams. It further goes on to show the advantages each of these tools brings to project management. Finally it shows if these tools have a positive impact on the project management, or if it is something completely different that makes software projects „tick“.

Abstract:When we perform a complex activity, we can solve it successfuly on time, if we plan it. In the best case, it is uncomfortable to perform an unplanned activity. If we were behind the schedule, it would be too late to raise the pace. Vice-versa, if we made too much effort, we would be too exhausted. Therefore, it is important to make the best plan possible to meet all the delivery deadlines, but also to prevent people from getting burnt out of working on the project. After such a plan is created, it is in general interest to keep following the plan. If the plan is not followed, it loses its purpose and a correction is needed. There are many factors influencing following of the plan. One of its important parts is to assign tasks to team members. This part influences the following of the plan, too.

Abstract:In this essay we explore advantages and disadvantages of software testing, while we look at complications and simplifications of testing in actual software development. We search for solutions of some basic testing problems. We look at possibilities of testing in small team working on a short-time project. We try to find methodologies of testing that ease resting in such team. We describe the SCRUM methodology of software development, which abstractly defines used testing approaches. Advantages and disadvantages of test driven development are evaluated, because they are mostly used in this methodology. Before end we try to offer an alternative testing approach, which uses aspect oriented approach of software development and evaluate positive and negative effects.

Abstract:All of us have met in our live with plans and estimates. Planning and estimation appear in the development and creation of software products and represent an important part during the period of its life cycle. Uncertainty in the development of products belongs to its main features. So if we want to create a project plan, we use estimates and estimation process. A separate estimate is based on the nature of the product, analysis and choice of estimation methods. Estimation process is not the easiestof activities. If the estimate is set incorrectly, it usually leads to overrun plans. Also there are many other reasons leading to the overrun projects. The process of estimating the error-prone. Nobody want to fight a war with estimations.It is in our intrest to know them better.