2 Agenda Questions? IP part 1 Late IP Part 2 Due Oct 10 (or maybe Oct 14)Group work days Oct 3Assignment 3 DueDue September 30 prior to classAssignment 4 PostedRead Case Study 4.3, Problems with John (page 130) and 5.4, Classic Case: The Ford Edsel . (page 167). Complete and upload the answers to the Questions at the end of each case study. In addition, complete the MS Project Exercise Project Outline-Remodeling an Appliance on page 171 of the text. Upload a MS project file (*.mpp) Due Oct 7Exam 1 on Oct 7Chaps 1-5 Open Book Open Notes 80 min.Scope Management
4 Chapter 5 Learning Objectives After completing this chapter, students will be able to:Understand the importance of scope management for project success.Understand the significance of developing a scope statement.Construct a Work Breakdown Structure for a project.Develop a Responsibility Assignment Matrix for a project.Describe the roles of changes and configuration management in assessing project scope.
5 Project ScopeProject scope is everything about a project – work content as well as expected outcomes.Scope management is the function of controlling a project in terms of its goals and objectives and consists of:1) Conceptual development 4) Scope reporting2) Scope statement 5) Control systems3) Work authorization 6) Project closeout
6 1) Conceptual Development The process that addresses project objectives by finding the best ways to meet them.Key steps in information development:Problem/need statementInformation gatheringConstraintsAlternative analysisProject objectives
7 Problem Statements Successful conceptual development requires: Reduction of overall project complexityGoals and objects are clearly statedReference points are providedComplete understanding of the problem
8 2) Statement of Work (SOW) A SOW is a detailed narrative description of the work required for a project.Effective SOWs containIntroduction and backgroundTechnical descriptionTimeline and milestonesClient expectations
9 Statement of Work Components BackgroundObjectivesScopeTask or RequirementsSelection CriteriaDeliverables or Delivery ScheduleSecurityPlace of PerformancePeriod of PerformanceStatement of work.docx
10 Scope Statement Process Establish the project goal criteriacostscheduleperformancedeliverablesreview and approval gatesDevelop the management plan for the projectEstablish a work breakdown structureCreate a scope baseline
12 Work Breakdown Structure (WBS) A process that sets a project’s scope by breaking down its overall mission into a cohesive set of synchronous, increasingly specific tasks.What does WBS accomplish?Echoes project objectivesOffers a logical structureEstablishes a method of controlCommunicates project statusImproves communicationDemonstrates control structure
13 Example WBS Making a PBJ Gather materials Assembly Consumption Get 2 slices of breadGet peanut butterGet jellyGet butter knifeAssemblyUsing knife spread 1/8” layer of peanut butter on one side of one slice of breadUsing knife spread 1/8” layer of jelly on one side of the other slice of breadPlace two slices of bread together with peanut butter in contact with jellyConsumptionBite off a chunk of PBJChewSwallow
14 Defining a Project Work Package Work package forms lowest level in WBS.Work package has a deliverable result.Work package has one owner.Work package may be considered by its owner as a project in itself.A work package may include several milestones.A work package should fit organizational procedures and culture.The optimal size of a work package may be expressed in terms on labor hours, calendar time, cost, reporting period, and risks.
15 Work Breakdown Structure and Codes 1.01.21.31.22.214.171.124.126.96.36.199.11.3.2The project is the overall project under developmentDeliverables are major project componentsSub-deliverables are supporting deliverablesWork Packages are individual project activities
16 Sample WBS in MS Project 2010 PBJ.mppFigure 5.7
22 3) Work Authorization The formal “go ahead” to begin work Follows the scope management steps of:scope definitionplanning documentsmanagement planscontractual documents
23 Contractual Documentation Most contracts contain:RequirementsValid considerationContracted termsContracts range from:Lump SumCost Plusalso called“Turnkey”
24 4) Scope Reportingdetermines what types of information reported, who receives copies, when, and how information is acquired and disseminated.Typical project reports containCost statusSchedule statusTechnical performance
26 5) Types of Control Systems ConfigurationDesignTrend monitoringDocumentAcquisitionSpecificationtemplates\Project Exception report.doctemplates\Technology Project Assessment xls
27 6) Project Closeout The job is not over until the paperwork is done… Closeout documentation is used to:Resolve disputesTrain project managersFacilitate auditingCloseout documentation includes:Historical recordsPost project analysisFinancial closeout
28 Reasons Why (IT) Projects Fail PoliticsNaïve promisesNaïve optimism of youthStartup mentality of fledging entrepreneurial companies“Marine Corps” mentalityIntensive competition caused by globalizationIntense competition caused by appearance of new technologiesIntense pressure caused by unexpected government regulationsUnexpected and/or unplanned crises
29 Using MS project 2010 (and ProjectLibre) Many of the required functions/reports in Project management are part of MS project 2010Industry wide acceptanceDo not use Wizard till you are comfortable with MS projectFile New Blank ProjectEnter Project and allDeliverablesSub deliverablesWork packagesIndent using arrows to show decompositionTemplateActual projectMore on MS Project as we progress through course
30 SummaryUnderstand the importance of scope management for project success.Understand the significance of developing a scope statement.Construct a Work Breakdown Structure for a project.Develop a Responsibility Assignment Matrix for a project.Describe the roles of changes and configuration management in assessing project scope.