Habdák MartinAbstract. 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.Pomothy AdamAbstract. Nowadays, testers are usually considered to be temporary one-shot employees. They are given only test scripts and rules, how to report found errors and they are supposed to do their jobs. However, testers are equivalent to a development team. They have the same goal – to deliver a high quality product to a customer. The communication is crucial for these two teams. However, if new testers are hired for every project, they have no relationship to developers and they are also in brand new environment. As a result, their communication is too formal and inefficient. That is the reason, why it is important to have a static team of testers as it is in case of developers. Good relationships or friendships result in much better cooperation. To achieve as effective communication as possible, it is also important to choose team leaders of both teams (it is common in case of developers, but not in case of testers). Team leaders coordinate other members of team, they are aware of current tasks and they communicate with external world in the name of whole team.
|