COMM 153 Lecture Notes - Lecture 14: Scope Creep, Scope Statement, Project Charter
9 Jan 2017
School
Department
Course
Professor
Document Summary
Why: components, project overview, goals, project deliverables, project requirements, out of scope items, high-level/initial time and cost estimates, roles & responsibilities, product acceptance criteria, assumptions, constraints. Lowest level of wbs: deliverables are broken down far enough when costs and time can be accurately estimated. & one individual can be assigned one wp. Wysocki"s pain curve: planning early & effectively, project planning follows project initiation, begins with project scope statement. Creates shared understanding of what is in project & what is not. Project scope statement components: project overview, goals, project deliverables, project requirements, out of scope items, high-level/initial time and cost estimates, roles & responsibilities, product acceptance criteria, assumptions, constraints. Natural sequence of scoping/project scope management 3 main activities: define requirements, customers & users tell you requirements; project managers facilitate. Establish critical success factors (csfs: specify scope (via project scope statement, develop a work breakdown structure (wbs) Identify final products, then decompose into interim deliverables: bottom-up.
