Real Web Project Management: Case Studies and Best Practices from the Trenches

Classic Scope Control

Standard software development models are requirements-driven: They assume that the project team will be delivering a final product with characteristics that can be clearly defined up front. These methodologies provide a disciplined, sequential process for defining the schedule, budget, resources, risks, and scope. For the sake of simplicity, let's assume a representative process with four stages: Define, Implement, Control, and End (DICE). The hypothetical “DICE” approach has a few distinguishing characteristics.

• Define. All project requirements should be captured in the Define stage. The output of the Define stage is the project plan. The approved plan includes the scope, budget, and schedule. Project work is broken down ...