Threads of the internal development in the tertiary sector

Danada Ondrej

Abstract. Organizations of the tertiary sector often have limited budget and that is why they have to develop their software projects at their own. This kind of projects has its’s own specifics and because of that there are different risks than in commercial projects of professionals. The purpose of this essay is to identify and briefly describe these specifics and compare these risks to the risks of ordinal software projects. The worst risk could be clearly considered the lack of staff, which threads more than in other kinds of projects and its’ consequences are bigger, too. Possibilities of avoiding these risks are also limited and it is necessary to look for special solutions. But some risks are because of some specifics, such as good domain knowledge insignificant and the thread is minimal.

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.

You may not want to, but I will lead you

Filčák Tomáš

Abstract. Monitoring is an important part of software development. There are many sources that discuss about different approaches, pros and cons, usability of knowledge and associated problems. Completely different topic is the impact of the choosen kind of metric application. It does not represent a different form, but a way of putting into practice. Each of method is specific and each provides a number of various affects in development itself, as well as relationships within a team and beyond. I would like to think about different ways of employees or software monitoring and influence of applicated method on employess and software behaviour or quality.

What kinds of traps are hidden within risk management?

Lihocký Michal

Abstract. Risk management is generally considered as an important part of software development, yet it happens very often that teams don’t support it. But how come that people are not willing to spend any resources to support risk management although they realize its importance? What prevents them to do so? What are main barriers in introducing risk management? Even after we successfully introduce risk management within a project, there are still many problems that we will face. What are the other problems we may face regarding risk management? Are there any recommended best practices in this field? Is there any concrete approach or model that would seem to be applicable in our project we develop within Team Project course? These are the main problems discussed in this essay.

I give finger our or foreigner

Ľoch Lukáš

Abstract. As a team we find ourselves in a simulated environment, which was created by a faculty, it’s teachers and students. Team is composed of 7 people and all of them are from the same country. This fact is an important factor for leading and communication within the team. I will be focusing on details of leader’s behaviour towards his subordinates in singlecultural team. I am taking a look at an example of studying in an eastern country, on which I will apply my own opinion about my domestic culture, which I have gained by my experience in the faculty. In the second view I will try to imagine working in a real environment, per se (including internationalism). In this section I will take a better look on pros and cons, of this team’s composition and in pros, I will try to find the solution for the problem that may appear in a singlecultural team. I am going to try to apply the final results on the simulated environment of the subject: Team project.

Risk without a gain

Mančík Gabriel

Abstract. Development and coordination of the software project is a challenging and often risky process. Aim of risk management is to study potential risks associated with development, predict them and minimize the likelihood of their appearance. This work is centred on risk management associated with outsourcing project to offshore companies, where a whole new risk factors arise. I address the fundamental issues and challenges related to the specific nature of the relationship between client and offshore supplier. My work analyzes the issue of the proper choice of supplier, risks arising from communication between different cultures and the problems associated with the physical distance of both parties. For all the discussed problems solutions are proposed.

Are tools for software development support really supporting?

Michalko Matúš

Abstract. Current market offers us a wide variety of various supporting tools that should make software development process much simpler, organized and cleaner. Amount of these tools and amount of their features is quite huge. Enriching these software products makes them more and more complex and harder to use. The more features these tools offer, the longer their learning curve is, moreover, overall time spent by their usage is increased during whole project development life cycle. Question is “which tools and which features are necessary and what’s their real contribution” Some tools like version control systems are “must have” software tools even on small projects, while advantages of other tools can be discussed. The decision about right tools that will be used on a project might have serious impact on whole project development. This essay discuss features and importance of various software tools, their possible difficulties and ideas how to make them even better and more supportive.

How to test games

Mikuda Šimon

Abstract. Making of the games surely belongs to more unconventional branches of information technologies, and therefore it is surely more entertaining. Games bring us new concepts which do not appear in other software projects and are critical in making of good games. In this essay author talks about issues and problems of testing games and more deeply analyzes this topic. He focuses on questions like: Is testing of games even necessary? In what is different game testing from game playing? What is best approach in game testing? The goal of this essay is to analyze basic principles of testing and their possible application on game testing process.

First write then sale

Piták Juraj

Abstract. In the origin of project there is mostly originated department of creating documentation. The documentation is created during whole life cycle of project. Many people do not think so, but it is part of final project. When capital is originated, some part goes on development of documentation. Some of big companies use the systems that can handle documentation. I used to use similiar systems. I compared when it is suitable to start using such systems. Since we put some financial part of project also on documentation, we have to create high-quality documentation. Usage of documentation management system do not provide high quality of documentation. If the documentation has high-quality, it tells about high-quality software. Writing good text is not easy at all. Writing requires high attention. Also it proceeds on documentation management. I mention how it is appropriate to write technical documentation. I devoted it in second part of essay.

Support tools: Which ones should we choose?

Puckallér Róbert

Abstract. From the perspective of developing software in teams we want to highlight the importance and utility of using support tools in different phases of software life cycle. We are focusing mostly on the possibilities of distributed teams, because on them we can best show what are these tools capable of providing. We describe important aspects to be taken into account when choosing the right tools, which is crucial, because the use of any random tool does not guarantee benefits.

Communication as a cause of failure of projects

Račko Michal

Abstract. Communication is in the case of projects involving multiple people important tool for solving problems. It helps the whole team to stay in touch and have access to fresh information about the project. However, is it necessary for each member of team to have overal picture of solution? Does he need all the information about what is happening in the team to work on his part of the solution? Is it necessary that everyone express himself to the overall solution? I will try to answer these questions and give the reader a picture of my view on this issue. I will introduce the reader into the problematic of communication in the team and express an opinion on individual communication practices used in the team management.

Successful planning

Rešetár Jozef

Abstract. The majority of people dislike looking to the future and instead of this live the present as much as they can. They don’t think what follows their present actions. They don’t plan, it bothers. They don’t want to plan because this moment is for them the most they have. They don’t want to lose the moment they like because of stupid plan making. They don’t realize that planning is very important part of everyday working and although they plan simple things like - what I am going to do today – this is the most they can do. More difficult and important plans are done by them very rarely. They postpone making difficult plans to time when plans is not in need. Then they have to solve problems on the fly. Paradox is that planning is not timekiller, but can safe lot of time when it is done. The disgust to planning is testified also in software development. This fact leads me to the theme of this essay – Success planning. What is important for successful planning? What type of impact have good estimates on planning? How to face causes of failure in software development in terms of planning and scheduling management? And finally, why we failed to submit first prototype of out application in team project subject? You can find answers to these questions in this essay.

Monitor, but check

Roško Bohuš

Abstract. The process of monitoring as whole is basic element of revealing of the work on project. It debates and analyzes methods of use cases, fuzzy logic and stakeholders to express subjective perspective of using these methods in larger or smaller projects and to reduce wasting of resources like time, costs and to achieve general success of project. It is important to find compromises in the solutions and offer ideal solution to customer. The monitoring must have goals and metrics. Then it helps to managers to direct the project, to keep it on correct way to its objectives and to reveal mistakes early, which could cause such wasting of time on development of project. We must perform it the way to help us and not to damage us.

Rise of forgotten son?

Šurek Marek

Abstract. Planning is one of the main components of development in any software product. We know different development models, which have its specifics. I’m interested in planning in Scrum methodology. My concerns belong to suitability of deployment in smaller and bigger software products. The highest importance is given to practical experience and usability in project planning. To cover complete area of Scrum, I based my opinion on practical and expert experience of people from business. I have also practical experience from middle size company which I’m going to share. Using Scrum in team project I consider as next area which deserves to discuss in adequate range.