Abstract:The complexity of software is constantly increasing. You can hardly find a software project where one or two developers are enough. Management or control people are not as trivial as it seems to be. It is necessary to deal with planning, sharing documents, controlling tasks etc. Actually software tools were created for these purposes. Supporting software is the think that can make our life easier. They can also help us to focus on the real problems. In this essay I am writing about supporting tools. I am focusing on small software projects just like team projects. In the final part of this essay I am trying to look at phrase “supporting tool” in same kind of different way. Motivation like supporting tool.
Abstract:The purpose of software project planning is to measure the amount of work and create a project implementation schedule. Latest trends in software engineering, in particular agile methods of software development, consider the ability to adapt to changes to be more important than strict plan adherence. However, adaptability does not mean lack of planning. It is only different approach to planning. Unlike classical methods of development, only short plans are being made by the whole team along with customer representative. After finishing the plan, new one for next phase of development is made. In the long-term, only basic purposes of project are indentified, however. They do not have the characteristic of a plan, but only of requirements software should fulfil once finished. This system of planning is useful mostly in smaller projects, since in bigger projects, problems might arise. The purpose of this essay is to point out advantages and possible risks of this approach to software project planning.
Abstract:Because result of software development process is to create a product, the question arises as to ensure its quality. However, unlike other products, software quality is measured and also heavier and more difficult to define. We can not specifically say what is good software. The quality can be seen from several angles - from the perspective coder, project manager, end users, etc.. Nowadays, more and more companies providing software solutions and so the quality is one of the factors that affect their market position and reputation are firm. One method of quality assurance and software testing is. In this essay I will describe some of the problems of testing but mainly compare different approaches to testing methodologies used by some as not every methodology is built on the same testing. And also describe the principles of testing used in agile software development methodologies and compare them with traditional approaches.
Abstract:During development process of software product, managers indicate and consecutively analyse risks and their impact on software project. Readiness, adequate analysis of eventual risks and plan of reaction are attributes of successful project. One of the reasons for complete ending of project is willful or unknowing imponderableness or no recognition of risks. One of the worst risks is unexpected risk. Despite of occurrence this kind of risk, all projects aren’t unsuccessful. Management of risks is necessary process. Essay provides basic informations about management of risks and it´s particular phases. It´s concern on phase of analysis and planning. Essay concerns on analysis of risk and tries to answer on the question what is necessary to do for elimination of risk. Essay tries to notice on the biggest risks in the software development.
Abstract:Project monitoring provides us with an information base of great value to project planning and managment. By closely observing activities of each team member connected with changes made to the project we try to reach the goals of a complex analysis and prediction. Companies nowadays have different technological resources at their disposal, like sofisticated camera systems that can be used as means to monitor their employees and their social networks. This essay is a mere introduction to the subject of monitoring of software projects. It also states some positive and negative aspects of software project and team monitoring. The question we ask ourselves is what the effective magnitude of paranoia of project monitoring is.
Abstract:Each person is unique and irreplaceable character, different from all others. This high differentiation is not a little problem, which impede us to achieve the generally applicable answer to the question of what what properties or personable assumptions create personality, and which approaches or methods we get to know this properties with. Managment many times does not take under consideration something different than specialistic classification, when allocating human resources and creating team groups, working on software project. Is it important from managment point of view to know personalities, when creating a team? How to explain the differences in reactions between individual members of the team? Do the properties of personality still exist? We will try to answer all these questions in this essay, by deriving mainly from respective, personal experiences. We will back up some arguments with exploration, which carried out in set zone and observed an influence of personable characteristics on team work from many points of view.
Abstract:Communication is in a team certainly irreplaceable. There is a lot of methods of team communication, but exists a few methods, which is used often, but don`t correctly everytime and thus reduce it effectiveness. In this essay, I`ll primary focus on feedback in team, which is very important in good motivation and team members review, but if is used incorrectly, it can be counterproductive. The next part of essay is brainstorming, which is in present often used method to make some new ideas. In brainstorming is necessary to obtain a few principles. Finally, my essay is about problems in communications and their sollutions. The bad communication in team may result in bad cooperation in the team and therefore delayed, but in some cases failed projects.
Abstract:A fair amount of software projects generally does not fulfill user expectations, is delivered late, or runs over the budget. Ineffective project management is cited as one of the most serious reasons of these failures. Software project management tools can alleviate the process of tracking tasks and managing project. In particular, this essay deals with the possibilities of task tracking in teams using software project management tools. The selection of an appropriate software project management tool is very important issue as well because the wrong usage of this tool can put project at risk or cause new threats.
Abstract:Right estimate of the software project is good assume for its successful completion, especially if there is an extensive project. It is essential to estimate the correct size, on which depends the amount of needed human resources, the total time needed for completion and ultimately its cost. There are different metrics to estimate the size of project, by which we would be able to exact measure and compare different project to each other. The essay deal with whether it still makes sense to estimate the size of the project for many years used metric - lines of code, and whether it would be preferable to focus on its alternatives. I discuss the shortcomings mentioned estimation using metrics and why now may not be so reliable as in the past.
Abstract:Nowadays there are a lot of companies in the world, which create a lot of software. Every company tries to create software, that is customer satisfied with. Customers want quality software, but in many cases happends, customers are not satisfied with quality of the software. That brings some negative aspects like loss of time, new investments, decrease of profit. This essay deals with software quality. There are suggested some tips in this essay, how to proceed by creating quality software and how to test software.
Abstract:Risk analysis and planning became in time an importatnt part of the software development cycle. As the project became more complex, the more important is to stress risk analysis. On the other hand, in simple projects is complex analysis counterproductive. This essay deals with more views on project management and risk analysis by using the newest technologies.
Abstract:Monitoring in software project could early reveal risks endangering the software development process. If it’s bargaining of goal achieving, plan completing or requests achieving, techniques of monitoring are presenting us indicators, properties of software development process and its parts. In dependence of nature and range of indicators we can expect presence or not-presence of more or less serious risks of software project. Risk is or eliminable or minimize-able by interventions, non-eliminable, or it will disappear by itself in time. It is important to discover, what sort of problem we are dealing with. Risks mostly implies of indicators captured by software process monitoring. But knowing about the presence of risk is not enough. Interventions leading to problem solutions or even question about solvability of risk are primary, if we want to ensure the success of software project. This essay is discussing the process of revealing and solving critical states and risks, and importance of communication as effective resource by this process. This communication and its properties depend on nature and seriousness of risk, and is resource to discover occasions of risk presence. We reveal answers of problem solvability questions based on discovered occasion or occasions, and we can execute necessary, suitable interventions and by that ensure fluency and safety of software development project.
Abstract:The aim of this essay is to show the ways of distribution of team roles in software development teams, show and pinpoint problematic personal traits and quirks and suggest solutions for these. Team membership personal profiles are analyzed according to the Myers-Briggs type indicator and application of this scheme to software development teams. Following this analysis particular negative personal traits are identified and solutions to conflicts caused by these are suggested. These solutions are based on author’s personal experiences with teamwork and team leading and from a questionnaire distributed to several IT professionals working in field of software development. The title “Who shall bring the coffee” is an analogy to one of the upper mentioned solutions, where problematic team members are given those tasks that are not critical or important to the course of project.