The Commerce of Content
Manager's Tookkit:
How to Set Project Guidelines (Part 2 of 4)

Project Management | People Management | Business Management | Information Design Models, Processes, and Techniques | Home

Set the Proposed Schedule

Setting the proposed schedule involves these steps:

  1. Estimating the size of the project
  2. Estimating the total length (in number of work days) needed to complete the project
  3. Establishing intermediate deadlines.

Estimating the Size of the Project

The information design that you developed in Phase Four should be complete enough that you can accurately estimate, within 20 percent, the total size of the information product.

To get a rough estimate of the size of the completed communication product, add up the number of:

Then, add a fudge factor to determine the total size of the project:

If you are dealing with Add the following to the length
Extremely stable subject matter 10 to 20 percent
Somewhat stable subject matter 20 to 30 percent
Untable subject matter as much as 50 to 100 percent

For example:

  1. Suppose that, as a result of your information design, a user’s guide will be 156 pages.
  2. You assess that the subject matter is somewhat stable.
  3. Add a 30 percent fudge factor:

To compute the 30 percent fudge factor:

156 *.3 = 46.8

Add the fudge factor

156 + 47 = 203

The estimated number of pages is 203

Top

Estimating the Total Length (in Work Days) of the Project

Determine the total number of work days needed for the project.

A work day is not the same as a day. Athough a week contains 7 days, it only contains 5 work days. In this step,you calculate the total number of work days needed to complete the project.

You can compute this number in one of two ways.

When You Set the Final Deadline. This is the ideal situation, in which you establish the final deadline for the project based on the amount of time needed to complete the project. To compute the total number of work days needed using this method, you use the appropriate estimating formula based on the medium you are using. For example, if you are preparing a printed manual, you would use the formula for estimating the development time for print.

The fundamental concept underlying each of these estimating formulas is the concept of "finished" work. A finished page represents all of the work involved in preparing the page, including review time, management time, editing time, and preparation of graphics--not just the technical writer's time.

Communication Medium Formula for Estimating Total Development Time (in Work Days)
Print Total days needed to complete a printed project

Number of pages / rate (about 1.5 to 2 finished pages/day) = number of work days

Online Total days needed to complete an online project

Number of screens / rate (3 to 4 finished screens/day)= number of work days

Audiotape Hours needed to complete a finished script

Number of finished minutes / rate (6 - 8 minutes a day) = number of work days

Videotape Total days needed to complete a finished minute of production

Number of finished minutes / rate (1-3 minutes per day) = number of work days

Live Hours needed to complete a finished hour or presentation

Number of hours of the final presentation / rate (20 hours of work for each hour of a finished presentation)= number of work work hours

Convert the number of work hours to number of work days (6 to 8 hours/work per day)

Because work rates vary widely among organizations and among types of projects, I cannot offer a definite rate for the number of hours needed to complete a finished page, finished topic, or finished minute. As a rule of thumb, I suggest the following estimates. Your time will almost certainly vary, but until you have experience, these estimates will provide you some realistic means of measurement:

Finished pages: 1 every 4-6 hours

Finished screens: 1 every 3-5 hours

Using this formula to estimate the total time needed to develop the user's guide mentioned earlier:

Example of Calculating the Length of a Project

Total days needed to complete a printed project

Rate (about 1.5 to 2 finished pages/day) * number of pages = number of work days

Assuming that the user’s guide has 203 pages and that we are choosing a a rate of 1.5 pages/day (assuming that the writer likely to work on the project has a moderate pace), the total number of workdays needed is:

1.5/203 = 135.33

How many work weeks are involved? To get the basic number of work weeks, divide the total number of days--in this case, 135--and divide by 5: 27 weeks.

But you have not yet considered time away for holidays, sick leave, and other purposes. Add 20 percent to your estimate to arrive at the total number of work weeks needed to complete the project:

27*.2=5.4

The total number of weeks estimated for this project is 27 + 5.4 (fudge factor), or 32.4 weeks.

When Your Client Has an Inflexible Final Deadline: Often, when clients approach you to develop a communication product, they have an inflexible final deadline when they need for you to have the finished product available. In such instances, the firm deadline must be the final deadline.

All the same, compute the total time needed to complete the project as you would using the other method. Although you might not have all of this time available to prepare your communication product, you might be able to use this estimate to request that additional people work on the project or that you purchase additional computer software and hardware.

For example, suppose that the client needs the user's guide just described in 29 weeks, even though you have estimated that the project needs 32. By making the client aware that you have removed 3.4 weeks from the schedule (about 12 percent of the total time of the project), you might need 12 percent or more of another resource to make up for the lost time. (Note that the addition of a person for the rest of the time is not an even exchange. A person might be available to fill in for the 12 percent of the time, but they also need to be trained and kept informed about the project, which adds to the time needed.)

Top

Establishing Intermediate Deadlines

The calculation you just made indicated the total time needed to develop the communication product. This time includes not only the time needed for drafting the information product, but also for copying and distributing review drafts, producing the communication product, and duplicating it. The time includes not just your time, but also that client, subject matter experts, and others who review the draft communication product, the editor, production staff, and others.

Your next challenge is to identify the intermediate deadlines so that each person has sufficient time to do their job. These intermediate deadlines are called milestones.

The eleven phases in the process that you read about earlier for developing a communication product represent most of the milestones; but additional milestones are included because they alert various people who play a role in the process of developing technical communication products when their assistance is needed:

This number of milestones is longer than the number listed in this book. The list presented here has additional phases for reviewing each intermediate work product in the planning phase with clients. This list also has separate phases for preparing and reviewing the second and third drafts; the discussion in this book combines all of the discussions of reviews into one chapter and revisions into another. Note, however, that this list does not contain the phase for maintaining the communication product, because that milestone is an ongoing task that occurs after the deadline.

The amount of time assigned to each step is a percentage of time of the total project (Hackos, 1994). To assign intermediate deadlines, then, you would divide the time between now and the final deadline into 4 main chunks, each with these percentages:

Milestone Percentage of Total Project
Assessment

Usually not indicated as separate milestones but need to be accounted for in your planning:

  • Research
  • Interviews
  • Report of the needs analysis
  • Approval for the report
  • Write objectives
  • Prepare evaluation plan
  • Receive informal approval for the objectives and evaluation plan
10-15%;
Design

Usually not indicated as separate milestones but need to be accounted for in your planning:

  • Choosing form and medium
  • Structure (outline, book elements)
  • Preparation of original design plans
  • Review and revision of design plans with client
  • Review and revision of design plans with potential users
  • Approval of the content proposal
  • Preparation of product guidelines (editorial, technical, production, and usability guidelines)
  • Prepare schedule, budget, and staffing plans
  • Final approval for the project plan
15-20%
First draft 25%
First review (editing, usability, technical). Be realistic with review time; people cannot review 600 pages of text in a day or two. Also, make sure that you leave time for copying (if distributing printed review copies) and mailing (to and from you) as well as time for meetings to clarify review comments. Part of the total time of developing the first draft, but you need to inform reviewers when copies are going to be sent.
Second draft 15%
Second review  
Third draft (optional) 10%
Third review (optional)  
Final draft 5%
Production. ALthough not separately reported in a schedule, leave sufficient time for:
  • Copyediting
  • Preparation of golden code and a camera-ready copy
  • To printer
10%
Shipping and distribution 1-4 weeks, depending on publishing method

Assuming that we have 32.4 weeks to design and develop the user's guide mentioned earlier, we would assign time as follows:

Milestone Percentage of Total Project Date
Assessment

Usually not indicated as separate milestones but need to be accounted for in your planning:

  • Research
  • Interviews
  • Report of the needs analysis
  • Approval for the report
  • Write objectives
  • Prepare evaluation plan
  • Receive informal approval for the objectives and evaluation plan
10-15%; 3-4.5 weeks.
Design

Usually not indicated as separate milestones but need to be accounted for in your planning:

  • Choosing form and medium
  • Structure (outline, book elements)
  • Preparation of original design plans
  • Review and revision of design plans with client
  • Review and revision of design plans with potential users
  • Approval of the content proposal
  • Preparation of product guidelines (editorial, technical, production, and usability guidelines)
  • Prepare schedule, budget, and staffing plans
  • Final approval for the project plan
15-20% 4.5 - 6 weeks
First draft 25% 8 weeks.
First review (editing, usability, technical). Be realistic with review time; people cannot review 600 pages of text in a day or two. Also, make sure that you leave time for copying (if distributing printed review copies) and mailing (to and from you) as well as time for meetings to clarify review comments. Part of the total time of developing the first draft, but you need to inform reviewers when copies are going to be sent. Set aside 1.5 weeks of the 8 weeks.
Second draft 15% 4.5 weeks
Second review   Set aside 1 week of the 4.5 weeks
Third draft (optional) 10% 3 weeks
Third review (optional)   Set aside 1 week of the 3 weeks.
Final draft 5% Rounding down, set aside 1 week.
Production. Although not separately reported in a schedule, leave sufficient time for:
  • Copyediting
  • Preparation of golden code and a camera-ready copy
  • To printer
10% 3 weeks.
Shipping and distribution 1-4 weeks, depending on publishing method 3 weeks

Next, you assign specific dates to each activity. That is mostly a straightforward activity. But when assigning deadlines for reviews, make sure you leave sufficient time to copy the draft (at least 2 days, even with quick copy services) and send it to reviewers (at least another 2 days, even with express mail) and for reviewers to return the draft to you (at least another 2 days).

Even if you are planning to conduct reviews with online copies (called an electronic review), leave at least 1 day at each end of the review for distribution. Although networks often deliver information the moment you transmit it, they sometimes "clog up" and do not deliver your files to the intended receiver for several hours or days.

The bulk of the time needed for production is needed for producing the communication product, which also includes time needed for duplicating it. The time needed for duplication varies, but is fixed by the printer or, for diskettes and CDs, by the duplication house. On shorter jobs, the time needed for duplication will be longer than 10 percent of the total job and this schedule will vary.

Finally, notice that there's a fair amount of flexibility in assigning dates; the estimating formulas are just that--for estimating.

Assuming that the start date is February 1:

Milestone Percentage of Total Project Date
Assessment

Usually not indicated as separate milestones but need to be accounted for in your planning:

  • Research
  • Interviews
  • Report of the needs analysis
  • Approval for the report
  • Write objectives
  • Prepare evaluation plan
  • Receive informal approval for the objectives and evaluation plan
10-15%; 3-4.5 weeks.

Febrary 1-22

Design

Usually not indicated as separate milestones but need to be accounted for in your planning:

  • Choosing form and medium
  • Structure (outline, book elements)
  • Preparation of original design plans
  • Review and revision of design plans with client
  • Review and revision of design plans with potential users
  • Approval of the content proposal
  • Preparation of product guidelines (editorial, technical, production, and usability guidelines)
  • Prepare schedule, budget, and staffing plans
  • Final approval for the project plan
15-20% 4.5 - 6 weeks

February 22-March 29

First draft 25% 8 weeks.

May 25

First review (editing, usability, technical). Be realistic with review time; people cannot review 600 pages of text in a day or two. Also, make sure that you leave time for copying (if distributing printed review copies) and mailing (to and from you) as well as time for meetings to clarify review comments. Part of the total time of developing the first draft, but you need to inform reviewers when copies are going to be sent. Set aside 1.5 weeks of the 8 weeks.

Review drafts sent May 13.

Second draft 15% 4.5 weeks

June 30

Second review   Set aside 1 week of the 4.5 weeks

Review copies sent June 23.

Third draft (optional) 10% 3 weeks

July 25. Note that a half-week was added here; early July is a vacation time and factored into the schedule.

Third review (optional)   Set aside 1 week of the 3 weeks.

Send July 18

Final draft 5% Rounding down, set aside 1 week.

August 2

Production. Although not separately reported in a schedule, leave sufficient time for:
  • Copyediting
  • Preparation of golden code and a camera-ready copy
  • To printer
10% 3 weeks.

August 23

Shipping and distribution 1-4 weeks, depending on publishing method 3 weeks

September 13

After preparing the schedule, you might adjust dates to accommodate your needs. For example, you might change the deadline for second draft because you have vacation time scheduled in June.

Last, you review the proposed schedule with your client. Because your schedule depends on your client completing reviews at the scheduled time, ask the client for a signed commitment to completing all reviews on schedule. If the client does not meet a scheduled review date, make sure that you get a written commitment that you have the right to delay final completion of the project one work day for each work day the reviews are delayed.

Once you have a committed schedule, publish it and make reviewers, editors, and others on the project team aware well in advance when you need their services. Occasionally remind them (people forget otherwise) so that you have the assistance you eed, at the time you need it.

Top

Related Resource: Work sheet for planning a schedule

How to Set Project Guidelines
1. (previous) Identify the assumptions underlying a project
2. Set the proposed schedule
3. (next) Set the proposed budget
4. Name the project team and their responsibilities

Project Management | People Management | Business Management | Information Design Models, Processes, and Techniques | Home

(c) Copyright. 1999, 2000, 2001, 2002. Saul Carliner. All rights reserved.