Pearl diving
What do you think about project scheduling prior to the class? How do you think differently now? Please identify three ways in which your thinking has changed after the class. And, why?
Prior to the class, to me project scheduling was to schedule the activities that will take place during the project, but, after the class I realized that apart from the activity scheduling it also include cost scheduling also.
Prior to the class I thought that project scheduling is a one man i.e. the project manager’s job, but, after the class I realized that effective project scheduling can only be done with inputs from everybody on the team and the involvement of the stakeholders.
Prior to the class I had a view that first project scheduling is done then it is combined with the work breakdown structure(WBS), but, after the class I came to know that scheduling and work breakdown structure goes hand in hand and is an integral part of the project schedule.
Just as the development of the project plan components the scheduling of the project is also an iterative process.
Scheduling of the project is broken down into the following heads:
1) Defining the schedule type
2) Defining milestones
3) Estimating the duration of the task
4) Defining the priorities
5) Defining the critical path
6) Identifying the risk
7) Reviewing the results
Defining the milestones is a key part of project scheduling. The completion of key actions is defined by milestones. Milestone is a cluster of many activities. Completion of the project is distributed into various milestones which when completed shows the progress of the project.
Defining the critical path is also an important aspect of project scheduling. It is basically the longest path through a project. It determines the earliest possible completion of the work. The critical path is carefully managed because if critical path is not followed properly then it would detour the whole project.
Identifying risk is also an integral part of
Prior to the class, to me project scheduling was to schedule the activities that will take place during the project, but, after the class I realized that apart from the activity scheduling it also include cost scheduling also.
Prior to the class I thought that project scheduling is a one man i.e. the project manager’s job, but, after the class I realized that effective project scheduling can only be done with inputs from everybody on the team and the involvement of the stakeholders.
Prior to the class I had a view that first project scheduling is done then it is combined with the work breakdown structure(WBS), but, after the class I came to know that scheduling and work breakdown structure goes hand in hand and is an integral part of the project schedule.
Just as the development of the project plan components the scheduling of the project is also an iterative process.
Scheduling of the project is broken down into the following heads:
1) Defining the schedule type
2) Defining milestones
3) Estimating the duration of the task
4) Defining the priorities
5) Defining the critical path
6) Identifying the risk
7) Reviewing the results
Defining the milestones is a key part of project scheduling. The completion of key actions is defined by milestones. Milestone is a cluster of many activities. Completion of the project is distributed into various milestones which when completed shows the progress of the project.
Defining the critical path is also an important aspect of project scheduling. It is basically the longest path through a project. It determines the earliest possible completion of the work. The critical path is carefully managed because if critical path is not followed properly then it would detour the whole project.
Identifying risk is also an integral part of
References: http://www.cioarchives.ca.gov/itpolicy/pdf/pm3.4_planning_project_schedule.pdf http://www.slideshare.net/ciprian/project-planning-1027489