The document discusses managing scope creep in IT projects. It defines scope creep as occurring when the scope of a project expands without control. Scope creep happens due to poor requirements, lack of change control, underestimating complexity, and gold plating. After scope creep, projects miss deadlines, go over budget, and provide lower returns. To reduce scope creep, the document recommends implementing scope change control processes, defining clear requirements, and using agile methodologies with frequent stakeholder feedback.
Related topics: