Essays collection 2013
Home Home SK
"software"
Calík Jakub

Abstract. Every software developer is trying to create software with best quality. Quality is not something that can be easily measured by the number of lines of code. There are several aspects that determine balance of the overall quality of software. Several methodologies and models for software development was made in order to create software product of good quality. However, not all of the methods and procedures of software development, place equal emphasis on all aspects of quality. While some aspects can have more weight in certain model, others could be put asside completly. Lately, become very popular agile development model. In this essay, I will try to explain how agile software development influence software quality aspects and how it can be improved.


Dulačka Peter

Abstract. Team creating is challenging task when one needs to combine not just quality characteristics of a team member, but personal characteristics to supplement other team members as well. Operation of the team using Scrum is even more important because of practically no time for hesitance. In this essay I discuss importance of team member in a team, problems one can cause and impact of individual on quality of whole team work. I explain the case when a small problem can contain more complex and hidden problems and according to my experience I try to propose methods how to deal with such a problems. Essay judges one’s characteristics and their influence on team members, work progress and final result, options of team members present when a problem occurs and most common problems connected with a person’s characteristics.


Kyžňanský Michal

Abstract. Word quality and mainly the one referring to software represents a magical concept which unfortunately suffers from being unfulfilled from the very beginning of usage of word software. Every management mainly deals with the people and that is the reason why I as a quality manager focus on approach to the people, how to be closer to them and pull the whole development team in a nonviolent way to achieve new levels of software quality. Quality manager often experiences sciamachy because on the one hand flawless software is utopia and on the other introducing new practices that will raise the quality level is not an easy task. Programmers ego and old established practices are just a few of the many problems that are waiting to be solved by quality manager. I am focusing mainly on the procedures and behaviour which can result in reduction of problems connected to quality crisis if properly established and integrated. Important weapons that quality manager can use is sensible approach, gaining trust on every level of organisation and development team and setting objectives. Fulfilling of these objectives must be measurable and in the end will increase quality not only in front of customers but also give programmers sense of good work. To be successful as a quality manager owners and managers must clearly see the benefits brought by activities connected to quality management by means of reducing costs for future development.


Left Separator
plan schedule communication software project team monitoring agile development customer risks risk Scrum planning risk management version management management disadvantages quality software extreme programming pair programming motivation success support tools version control quality management documentation agile methods software development tasks software metrics team project documentation management project metrics waterfall model manual guide development support small teams usability testing software quality support tools development support management software configuration quality control version control system efficiency agile methods of software development