Drafting a Schedule
One of the most common problems we have seen with class Web projects is underestimating the amount of time it will take to accomplish each step. Perhaps the most effective way to prevent this from happening is to draft a realistic project schedule. A class that meets for two hours twice a week is not going to pull a Web site together in two weeks. But it also may be difficult to pull it together in 12 or 16 weeks, if access to computers is limited.
The sample schedules below might be used as a model for drafting your production schedule(s). They are designed for class projects that follow a standard Web development process, and you'll likely want to adapt it to meet your particular needs.
Even with a project schedule, it is often difficult to gauge the time it will take to finish a project. Much depends on the depth of the lessons that accompany the projects, participants' skill levels (either in language or computer competency), the amount of writing and editing expected, the amount and complexity of graphics or multimedia elements involved, and the level of technical support required. With those warnings in mind, we suggest planning for at least 30-40 hours of class time for a comprehensive project.
Last Updated October 23, 2003