Essays collection 2012
Home Home SK
"development"
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.


Pomothy Adam

Abstract. 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.


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