Publishers of technology books, eBooks, and videos for creative people

Home > Articles

  • Print
  • + Share This
This chapter is from the book

Creating Schedules

Projects need a schedule, and people respond to deadlines. Whether in a check-off list, calendar view, text in an email, or a weekly breakdown, there are many different ways to communicate timeline and sequence. In addition, a project schedule should emphasize immediacy of needs. Distribution of a schedule is the proverbial lighting of a fire under everybody's seat. It is a wake-up call with an obvious message: "We are starting now. Here is what is due and when." Strive for clear communication. Fully explain how missed deadlines have a domino effect. Many clients do not understand that when they are late with feedback, it retards the flow of the schedule and therefore the final delivery date. Some client education may be necessary and, if done in a goal-oriented manner, will probably be appreciated.

We recommend approaching the scheduling task in two ways. First, create an overview schedule that shows methodology chronologically. Then build a detailed date-by-date format that itemizes deliverables and approval reviews according to due dates. One follows and evolves out of the other; each communicates the message from a different perspective. Get both schedules approved by the client. Leave nothing up to interpretation.

No one should ever have to dig for a deadline. This information should always be available, front and center, and perhaps even emailed or posted to the online staging area as a weekly reminder. Schedules should communicate a sense of urgency and should keep both your team and your client on track.

Overview Schedule

The overview schedule is just that, an overview. Easily referenced and descriptive, it's an excellent forum to present a big picture view — the whole project, complete with methodology and breakdown of major milestones and deliverables. This schedule, which can be quickly built, is appropriate both for the proposal stage and kick-off meeting and throughout the project as a point of reference.

Begin by separating the project into weeks or months as well as into phases and steps. We suggest using the core phases put forth in this book. See [3.15] for a generic example.


none 3.15 A sample 10-week overview schedule shows methodology and a summary of tasks and deliverables. (This example is in a simple table format created in Microsoft Word. Use whatever format best communicates to your client and your team.)

Detailed Schedule with Deliverables

Action items — deliverables being submitted or milestones that need to be met — push both team members and the client forward. A detailed schedule with deliverables becomes a concise, day-by-day list of action items. It communicates pacing to everyone involved, and pacing is critical to keeping the project on track.

The detailed schedule with deliverables grows out of the overview schedule. Keep your overview for reference (and, of course, update it if suddenly the scope balloons from 8 weeks to 13), but itemize and delineate on the detailed schedule [3.16]. Keep schedules current as the project moves forward and changes, and make sure schedules are easily accessible in your staging area. Communication is the key to avoiding schedule lags.


none 3.16 A detailed 10-week schedule with deliverables breaks the project down into weeks and days. (Set up in table format using Microsoft Word, specific deadlines and deliverables are clearly identified.)Core Processdefine projectplanning,detailed schedulesplanningschedulesprojectsdefinitionplanning, . planningschedulesplanning

  • + Share This
  • 🔖 Save To Your Account