SPM-Week-5.ppt - Week-4 Project Scope Management Project Scope Management Monitoring Controlling Processes Planning Processes Enter phase Start project

SPM-Week-5.ppt - Week-4 Project Scope Management Project...

This preview shows page 1 - 10 out of 53 pages.

Week-4 Project Scope Management
Project Scope Management Knowledge Area Process Initiating Planning Executing Monitoring & Contol Closing Scope Collect Requirements Define Scope Create WBS Verify Scope Control Scope Enter phase/ Start project Exit phase/ End project Initiating Processes Closing Processes Planning Processes Executing Processes Monitoring & Controlling Processes
Project Scope Management Scope refers to all the work involved in creating the products of the project and the processes used to create them. Scope can refer to Product Scope & Project Scope A deliverable is a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes. Project scope management includes the processes involved in defining and controlling what is or is not included in a project. Don’t assume that requirements were determined before project began (not part of the project) Attitude to say no to unnecessary scope. It should go to project approval process
Project Scope Management Processes Scope planning : Deciding how the scope will be defined, verified, and controlled. Scope definition : Reviewing the project charter and preliminary scope statement and adding more information as requirements are developed and change requests are approved. Creating the WBS : Subdividing the major project deliverables into smaller, more manageable components. Scope verification : Formalizing acceptance of the project scope. Scope control : Controlling changes to project scope. 4
Scope Planning and the Scope Management Plan The scope management plan is a document that includes descriptions of how the team will prepare the project scope statement, create the WBS, verify completion of the project deliverables, and control requests for changes to the project scope. Key inputs include the project charter, preliminary scope statement, and project management plan. 5
5.1 Collect Requirements The process of defining and documenting stakeholders’ needs to meet the project objective Balance stakeholder’s requirement: prioritizing requirement & resolve conflicts Inputs 1. Project charter 2. Stakeholder register Tools & Techniques 1. Interviews 2. Focus groups 3. Facilitated workshops 4. Group creativity techniques 5. Group decision making techniques 6. Questionnaires and surveys 7. Observations 8. Prototypes Outputs 1. Requirements document 2. Requirements management plan 3. Requirements traceability matrix
Collect Requirement Techniques (1) INTERVIEWS : Directly talk with stakeholders FOCUS GROUPS : Interactive discussion with qualified Stakeholders & Subject matter experts FACILITATED WORKSHOPS : Focused cross functional stakeholders. JAD Joint application design, QFD Quality function development Helps determine critical characteristic of new product development Start by collecting customer need - VOC: Voice of the Customers
Collect Requirement Techniques (2) GROUP CREATIVITY TECHNIQUES : Brainstorming, Nominal group technique: enhance brainstorming with voting and ranking

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture