Essays collection 2012
Home Home SK
"project planning"
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?


Krátky Peter

Abstract. This essay discusses the process of creating accurate time estimations of the project plan. In the beginning I concentrate on the necessity of the accurate time estimations and issues resulting in the overrun of the estimation. Next I introduce wide-spread technique to get a detailed look of the project as a basis of the time estimations creation. I acquaint the reader with the cardinal groups of the methods to create time estimations and I compare them particularly in the point of view how they are influenced by presence resp. absence of the human factor. In connection with this I underline the importance of liability and fairness in creating estimations. Finally I answer the question of which method is the best choice in the time estimation process with respect to character and environment of 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