Essays collection 2012
Home Home SK
"motivation"
Jašš František

Abstract. Currently the software is used increasingly. It affects almost all the human activities. This is reason why, demands its development is growing. Is required not only high quality, but also the shortest time of delivery of the finished solution. In order to fulfill this could be a lot of effort, often hundreds of people. Cooperation as large, but also smaller groups of people requires a high degree of coordination. Every single team member must know what to do and when it needs to be done, because of timeliness. That's why planning is important. It seems that for large projects with large numbers of people involved in the solutions, is planning necessary, but is also needed in small teams, where coordination is not nearly so difficult? How to plan projects that people are not overwhelmed, but to prosecute dates yet? How to plan to not lose too much time for planning? Answers to these and other important issues I will discuss in this essay. In addition, I will discuss some important causes of failure of projects from the standpoint of planning, and from a different perspective. These factors are also an integral part of software projects and should take them into account in the planning process.


Ševcech Jakub

Abstract. A large part of the success of each project is the approach to the communication with people. In order to have product that people use, it is necessary to attract them and convince them that yours project is the right one. In the open-source projects, the communication with users have also another dimension. We try to create a community around our project which would not only enjoyed our product but would also contribute to it and would try to improve it. This essay describes means to establish a "relationship" with users and maintain the community as well as instructions on how to use these means for motivating people to participate in the project.


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