INSY 4507 Chapter Notes - Chapter 7: Work Breakdown Structure, Scope Creep, Change Request

• School: Fordham University
• Department: Information Systems (Gabelli Undergraduate)
• Course: INSY 4507
• Professor: Dowdell

Document Summary

Chapter 7: plan scope management: process of developing plan that includes total scope of what needs to be done & what is excluded from the project, implementation & validation of scope, & control deviations from scope statement. Collect requirements: requirement: condition/capability needed by user to solve problem/achieve objective that satisfies standard/spec/any other formally documented need, collect requirements: systematic effort to understand & analyze stakeholder needs to define. & document needs & requirements w/ focus on meeting project objectives. Define scope: define scope: process of translating stakeholder needs & requirements into detailed specs of product outcomes & products. Reasons to define scope: vital in preventing scope creep, best time to gain customer understanding, estimate project cost, # & type of workers needed, project length & risks, & quality standards. Wbs formats: 1st lvl overall project, 2nd lvl depicts major deliverables, 3rd lvl depicts interim deliverables of major deliverables, etc.