If you take all you tasks from the WBS, and your estimates how long they will take and, when they could start and finish, you have the ammunition to create one of the icons of project management: The Gantt Chart. It is a good way to visualize to information you have before you. And, because it's considered an Icon, using it in your communication will set some stakeholders at ease.

Related link
Burn-Down Chart Instead of Gantt
The Death Of Gantt Charts?
Reality Refuses To Follow Your Plan

Basically, a Gantt chart is an overview of tasks. You put weeks, days or months at one side, and the tasks at the other. You draw fat lines to indicate the period the task will be performed.

Put next to the task the name of the person who will do the job, and you come a long way in creating your Gantt chart.

Making A Gantt Chart With Excel (video)

PERT; almost as good as Gantt charts

If Sesame street has Bert and Ernie, Project Management has PERT and Gantt charts… PERT is a notation technique, which has a lot of fun features I will not discuss. The good thing however on creating a PERT chart is that you have to think about the relations between tasks. Can task X start before task Y? Do they have to end together? Must they start at the same time? etc. If you think in this way about your tasks you can create graphs like shown below.

Before you can pour your coffee, you have to get up. Before you can get dressed, you have to be up. You don't have to be dressed to pour the coffee. However, you have to be dressed and had your coffee before you can leave for the office.

Suppose "Pouring coffee" takes you 5 minutes, and "Getting dressed" 15 minutes. Suppose your wife pours your coffee. In that case the time it will take you to get up and leave home is the total time for "Getting up" + "Getting dressed" + "Going out". Say, that is 30 minutes.

As long as your wife stays under the 15 minutes, you have no delay. Only if she decides to make you an espresso, you are late. You see why? This is very useful information. Not for the example I used, but for the project you have to take on. It shows you who has to wait for who, and stuff like that. It shows that a delay of one task, does not automatically mean a delay of the entire project. All the tasks that have this property however, are called the "Critical Path". These activities have to be done sequentially, will take the longest in that time frame, and a delay in one of the tasks within the critical path, will cause a delay in the entire project.

Related link
Burn-Down Chart Instead of Gantt