Basic principles
The reality of a technical project is which 100 of small tasks must occur to accomplish a larger target. Some of these tasks lie outside the mainstream and may be completed without worry about impact on project completion date. The other tasks lie on the Critical path if these critical tasks fall behind schedule the completion date of the full project is put into jeopardy.
The project manager's goal is to describe all project tasks identify the ones which are critical and then
Track their progress to ensure which is delay is recognized one day at a time. To accomplish this manager must have a schedule that has been described at a degree of resolution that enables the manager to monitor progress and control the project.
The Software project scheduling is an activity which distributes estimated effort across the planned project timing through allocating the effort to specific software engineering tasks. It is very important to note that whereas the schedule evolves over time. By During early stages of project planning a macroscopic schedule is build. This kind of schedule identifies all major software engineering activities and the product functions to which they are applied. As the project gets under way each entry on the macroscopic schedule is pre define into a detailed schedule. Here specific software tasks are scheduled and identified.
Scheduling for software development projects can be viewed from 2 rather different purposes. In the 1st, an end date for release of a computer based system has already been build. The software organization is constrained to distribute effort within the prescribed time frame. The 2nd view of software scheduling supposes which rough chronological bounds have been discussed but that the end date is group through the software engineering organization. The Effort is distributed to make best use of resources and an end date is described after careful analysis of the software. By unfortunately the 1st condition is encountered far more frequently than the second.