Essays collection 2012
Home Home SK
"team"
Burger Roman

Abstract. It is not easy to do something we haven’t done yet. It is not easy to learn something new. And especially, it is not easy to determine if we are doing it the right way. Therefore we should be extra careful and diligent to understand the core of things. In this essay I will discuss my own experience in software development in newly assembled team. I will show which processes in software planning are hard at first even if you consider yourself skilled and I will also show which processes could be done easier with the appropriate approach.


Habdák Martin

Abstract. Monitoring is often used for better project planning. It follows the state of the project and helps to uncover errors which cause problems in software development. Monitoring provides a view on team behavior too. We can rate it on the basis of collected data. Results can be inaccurate when improper metrics are used. This Essay describes how can such a vagueness lead to bad relationships in a team. Many well established metrics can be used by the team members to pretend that they have done more work. Therefore various conflicts emerge. They tend to reflect on the project development. Team morale and efficiency is also reduced. Project managers often use easy to follow metrics, which incite such team problems. This essay shows that such metrics are unsuitable and presents alternatives to their use.


Tóth Juraj

Abstract. Monitoring is a tool that is used for analyzing and gathering information about the project. It provides important data necessary for a successful project throughout the whole duration of the development. This essay offers essential insight and reflection on the issue of monitoring. It implicitly and explicitly discusses the methods of information gathering in the area of software projects and it also evaluates and compares them.


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