�ݺ�ߣ

This document discusses negotiating schedules for developing content-heavy websites. It notes that such sites require frequent changes, are global in scope, and involve multiple editors producing content continuously. Schedules are often too tight and not based on sound planning. The document advocates discussing quality requirements like maintainability, conceptual integrity, consistency, analyzability, and testability up front. It provides techniques for negotiating, like illustrating long-term costs of technical debt. Maintainability is key to avoiding legacy systems that become too expensive to change.