At this point, we can split the project into three distinct parts: development, content population, and testing. However, that doesn't mean that it will necessary follow that these parts will be done in succession. For smaller, less complex projects, you can complete each part after the other. In larger projects, it's not always practical or advisable to take that approach. Chances are you'll have to release some features to the client for review or provide a snapshot of the development to the client for content population. Of course, taking a staging approach with a number of releases has its advantages and disadvantages.
In the case of smaller projects or projects without extensions, you can create a straightforward project plan. Those of you familiar with Microsoft Project can present a formal project plan in the form of a Gantt chart. Alternatively, a Word document will also suffice. The tool is not that important; the key is to communicate what tasks...