(lively music) When the work is identified, well understood and the order to complete the work is known, you can create the final schedule. You can do this by breaking down the work from more extended activities to shorter tasks. You can then assign resources, consider limitations along with constraints and risks, and make final adjustments using your knowledge of the critical path. The final schedule will represent a time model for a project, guide the project team in understanding who does what and when. And allow the project manager to track progress. On average, the work packages, which are the lowest level of activities in the work breakdown structure will be around a month long. For managing and tracking purposes, this period may be too long. Having tasks averaging a week or two will keep the project manager better informed about the project status. If there are any issues with the schedule, the project manager can take any necessary corrective action sooner. So let's break down the activities into tasks. While the project manager works with the entire team to develop the work breakdown structure and determine the work sequence, task identification can use a different approach. The project manager may perform task identification with the help of the resources most familiar with the various activities. Write the task lists using action verbs, like write the subroutine and build the frame. Each task will also need an estimate of its duration. As with previous estimates, consult with the team members performing the work. It will get their buy-in and they will be more likely to follow the plan. Compare the sum of the task durations to the estimated duration of the activity. They should be about the same, although some minor adjustments may be necessary. If there is a significant difference, this signals a need to reexamine the activity to ensure that it's well understood. Each task will need a predecessor, and successor. Connect the first task to the last task of the predecessor activity, and the last task to the first task of the successor activity. Examine the activities one by one, following each related path. When that path is exhausted, go back and follow the next path, continuing until you've considered all activities. Next, place the initial tasks on the timeline at the project's desired start date. The relationships, dependencies, task durations and lead and lag times will then guide the placement of the remaining tasks. Once the task timeline is complete, assign resources to the tasks to finalize the schedule.