IT项目管理范围管理(第五章).pptVIP

Chapter 5: Project Scope Management What is Project Scope Management? Planning Scope Management Collecting Requirements Defining Scope Creating the Work Breakdown Structure (WBS) Verifying Scope Controlling Scope Using Software to Assist in Project Scope Management * Scope Control Scope control involves controlling changes to the project scope. Users are not sure how they want screen to look or what functionality they need to improve business performance. Developers are not sure how to interpret user requirements. Goals of scope control are to: Influence the factors that cause scope changes. Ensure changes are processed according to procedures developed as part of integrated change control. Manage changes when they occur. To do a good job of scope control Do a good job of scope definition and scope verification. Developing a process for soliciting and monitoring changes to project scope. Tools to scope control Change control system Configuration management Replanning project scope Variance analysis Variance is the difference between planned and actual performance. * Suggestions for Improving User Input Develop a good project selection process and insist that sponsors are from the user organization. Place users on the project team in important roles. Hold regular meetings with defined agendas, and have users sign off on key deliverables presented at meetings. Deliver something to users and sponsors on a regular basis. Don’t promise to deliver when you know you can’t. Co-locate users with developers. * Suggestions for Reducing Incomplete and Changing Requirements Develop and follow a requirements management process. Use techniques such as prototyping, use case modeling, and JAD to understand user requirements thoroughly. Put requirements in writing and keep them current and readily available. Create a requirements management database for documenting and controlling requirements. Conduct adequate testing throughout the project life cycle to verify that the projec