Essays collection 2012
Home Home SK
"critical path method"
Horváth Róbert

Abstract. Planning and scheduling are the activities we do in our everyday life and oftentimes we do not even think about them. Those processes take place not just in our life, but in software project development as well. To create a quality schedule, which is a necessity for further stages of software development, we can choose from several methods. It could be hard to choose proper method, which fits our project specifics, just by its definition. In this essay I describe my opinion on which method to use based on project specifics. I focus on their advantages and disadvantages. Problem is that choosing a right method does not guarantee creation of a good schedule. It is easy to make mistakes in the process, which could lead to failure. Therefore I identify the most common mistakes in process of planning to help managers with avoiding them.


Mihalik Matej

Abstract. Critical path method is currently a very wide-spread and popular method used in planning of software and many other types of projects. A reader who does not have a complex understanding in the field of project planning can often stuble in the dark when it comes to the choice of which method to use in planning of a specific project. This paper is aimed exactly at such readers, since we will take a closer look at the critical path method planning, its usage in the real life projects, and we will try to answer the question of why should we consider using this method, and when is it most beneficial for our goals. We will present the method's various characteristics, and afterwards the method's pros and cons. In the end we will discuss the method's appropriateness for various kinds of projects, considering their size, as well as the development model used.


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