Essays collection 2012
Home Home SK
"team size"
Kubis Viliam

Abstract. Selecting the right method of risk management is a crucial decision that needs to be made at the beginning of a project. Incorrect risk management method choice can lead to complete failure of risk management process, which will significantly endanger the succes of the whole project - it can lead to a complete haltdown and failure of the whole product. Analyzing and thinking about a particular risk management methodology to choose is one of the toughest decisions a project manager has to make. According to what criteria can a project manager choose the right risk management method? Are all presented methods pricipally equal and usable for each and every project? Is team size and geographical structure significant and important in the decision making process? We strive to answer these and many other questions, or at least provide hints which will lead to making the correct decision - and in turn success of the whole project.


Sládeček Peter

Abstract. In the execution phase of a project, the hidden mistakes are brought into the creating solution. If they are not discovered, they brought the fatal consequences like an unsuccessful release of the project. The mistakes can be eliminated at the beginning with an application of monitoring metrics, when their fixing takes just a few hours. So why do project managers not make more effort and finance costs to the monitoring? Do they worry about inefficiency, which are adopted? Do they hold an opinion, that planning and managing are the sufficient conditions of the successful? A main goal of this essay is brought the readers to the necessity of using monitoring in small and big teams. It will be showed that managers can be use received information in the planning and managing this or future project.


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