Essays collection 2012
Home Home SK
"outsourcing"
Kráľovič Anton

Abstract. Monitoring as well as in practice means regular monitoring of progress in any software project. It's activity that has primarily helped by the software project manager for early detection of any shortcomings on his project, whether failure to meet pre-established schedule or not the client's requirements. Such monitoring is of course its advantages and also disadvantages. What are they and what is their proportion? As software projects ever shared and how to measure their "reliability"? In this essay I try to answer these questions.


Slotík Igor

Abstract. When creating a software product, especially at the beginning of its life cycle is a great need for communication. Implementation would not even really begun, if every developer did not know what has developed into components which can interfere with where and how to save changes to the developed product, who are his superiors. Lack of communication and organization will return in the form of conflict intervention in the source code, changes in technology, failure to meet inspection deadlines, or total failure of software development. Need for communication is particularly appreciable for distributed development. If you have distributed teams since the beginning of the problem to agree on important issues, software product development is threatened. In the essay, I want to think about when and even whether it is worthwhile to distribute the work and if so, what methods and approaches to solve the communication problem of distributed development.


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