Essays collection 2012
Home Home SK
"agile development"
Ivanec Peter

Abstract. Planning is important and integral part of every project, not only that software oriented. Using agile methodology - Scrum - is planning more intensive and critical than in other types of software development. In individual few-weeks-long sprint is necessity to plan and meet short term goals specified for that-which sprint. If the project wants to end successfully, it has to be well planned and all specified deadlines have to be met. But what is the successful project and who decide, if concrete project is successful or not? Planning deadlines of projects alone is not enough. There are known certain agile programming factors, which connections with successful Scrum project were proven. Therefore is planning in this essay described as a tool, which gives the project potential of success? Is it everything that is needed to guarantee success? Is setting a project plan only really enough? What planning needs to include, so project based on this plan will be successful?


Macošínec Branislav

Abstract. This work shows why it is important to create documentation. Documentation is generally considered a necessary evil in the software development. My goal is to show that this is may not be good documentation and creating even a supports the process of software development hence the successful completion of the project. Consequently addressed the question: What is a document which contains? This work also shows how agile software development to build the documentation. Later in the document briefly outline what you should be good contains. The paper also addresses the question: Why do people need documentation. Additionally, this document contains the principles of documentation and its breakdown. At the end of the work I deal with documentation describing the distribution areas.


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