The project start date here plays a key role because based on the start date and the

end date, all the

tasks and sub-tasks involved in the project are further broken down and planned accordingly. The
identification, scheduling and budgeting of each task are essential as this will let the project manager
assign a deadline for each task and monitor if the project is maintaining its overall deadline. The entire
task is assigned to individual or group owners, and they make sure that each of the tasks is performed in
a well-coordinated manner.

The next section is related to the client details for which the project is assigned. The client part is the
name of the client for whom the project has been taken into consideration. The address part is the
postal address of the client on which formal communication can be made in case if need be. The phone
and email are again focused on the client firm, which is generally required for any contact to be made.

This section is the most crucial section of every project tracking template because this is where all the
information gets noted in. The project manager has to closely track the project based on all the
information filled here and plan accordingly. The entire project and its related tasks are broken down
into smaller sub-task here and are tracked accordingly. Every subtask is given a title, and further, the
tasks under each sub-tasks are tracked individually.

The task structure goes according to the hierarchy like 1, 1.1, 1.1.1, 1.1.1.1 and so on. The description
column gives the description of each task and the sub-tasks involved within it. Each task or sub-task has
a specific owner or the one who has to take responsibility for it. The start and end date is an essential
thing to track because this is what the project manager is interested in to see each of the tasks and the
sub-tasks involved are well in tack and there are no backlogs involved.
The note section can be used to make certain notes by the task owner regarding some backlogs or
comments about some incidents or resource allocation, or it can be anything relevant and useful for the
task. Here the main tasks are divided into three parts labelled with numbers 1, 2 and 3. Taking the
example of Task 1, we can see there are two sub-tasks involved which have been marked as 1.1 and 1.2.
Again task 1.2 has another sub-task under it which is marked as 1.2.1.

Finally, 1.2.1 has two sub-tasks under it which is further marked as 1.2.1.1 and 1.2.1.2. We can also see
each task and sub-task has an individual assigned to who the main owners of each task. This generally
follows a hierarchy pattern where the key task is assigned to a senior position of an organization. Then
the drill-down of the task goes from a high to junior position level accordingly. Similarly, even for main
task 2 and 3, the subtasks are shown categorically and follows a similar breakdown to what was shown
in the above example of Task 1.

The mechanics of the procedure result in the creation and update of the project visibility chart. The
vehicle for this procedure is the estimating and scheduling form. The form integrates the key steps of
the procedure and flows through to provide the data for the project visibility chart.

Mekanisme hasil prosedur dalam pembuatan dan pembaruan dari bagan visibilitas proyek. Sarana
untuk prosedur ini adalah bentuk estimasi dan penjadwalan.

The Accomplishment Value Procedure (AVP) highlights actual completion of milestones and ignores
partial completion. It provides the mechanism for identifying those milestones in the development
process that have specific deliverable documents which signal the completion of a milestone.
Once the milestones are identified and resource estimates are associated with each, the sequence of
events can be scheduled. Next is the calculation of the “value” of each milestone.