Chapter 5 Project Scope Management

Chapter 5 Project Scope Management
In this chapter we will cover the following topics: Project Scope Management Plan Scope Management Scope Management Plan Project Scope Statement Collect Requirements Perform Requirement Analysis Define Scope Create Work Breakdown Structure (WBS) Advantages of WBS Validate Scope Control Scope Please click next to begin the chapter. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-1

Project Scope Management Contents
Scope Management overview Scope Management Processes Plan Scope Management Collect Requirements Define Scope Create WBS Validate Scope Control Scope Project Scope Statement Scope Management Plan Requirements Management Plan The topics covered in this chapter are: Scope Management Overview Scope Management processes Plan Scope Management Collect Requirements Define Scope Create WBS Validate Scope Control Scope Explanation and importance of the Project Scope Statement Explanation and importance of the Scope Management Plan Explanation and importance of the Requirements Management Plan PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-2

Scope Management Learning Objectives
By the end of this chapter, you should be able to: Explain the purpose and importance of project scope management Name the Scope Management processes Explain the purpose of each process and associated activities By the end of this chapter, you should be able to: 1. Explain the purpose and importance of Project Scope Management 2. Name the Scope Management processes 3. Explain the purpose of and activities performed in each process PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-3

Inov8Solutions Inc – Quality Educational Services For Professionals
Kamran: Not sure if we have copyright for this photo. See if you can suggest an alternate picture or text. Else delete this slide This is a good illustration of scope management related to software development. If scope is not defined and documented properly, the results can be disastrous, and the final product may not meet client’s requirements. Poor scope management can also mean over budget and missed deadlines for the project. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-4

Who manages the Scope ? According to 2004 Gartner Survey results, the top 3 risks threatening the success of e-projects are: Unstable, constantly changing requirements (66%) Poor requirement specification (55%) Client behavior such as approval delays, requirement changes and poor communication (42%) Project Manager is responsible for managing Scope. In a survey, conducted by Gartner Group in 2004 the top 3 risks threatening the success of projects are related to Scope. Unstable, constantly changing requirements, due to poorly defined scope at the beginning of the project, can affect project success. Poor specifications can also results in scope changes. If you put out a product that is not according to the specifications, it will come back for further development leading to increased costs for the project. This can add additional costs to the project. Lastly, client behavior and communication problems also result into project scope to change and the success of the project. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-5

Project Scope Management
Plan how scope will be defined, validated, and controlled Includes all work required to complete project successfully Defines and controls what is and is not included in the project Prevents gold plating customer should be given what they asked for and no more The following tasks are outcomes of this process: Scope Management Plan Approved detailed project scope statement WBS/WBS dictionary which forms the scope baseline of the project What is Scope Management? This includes all the work that is required to complete the project successfully. Project scope statement defines all the work that will be performed, and when all of the work and tasks are completed the project is finished. It is important to mention what is out of scope to clearly communicate to the client what will not be done in the project. It is better to explicitly mention what is out of scope in the scope statement or Statement of Work (SOW). What is gold plating? By definition it is an extra feature or service that your provide your client without their asking at no charge. The intention may be good on the providers part to satisfy the client. However, it can come back as either additional work or there could be support related issues associated with the extra feature which will add up to the overall cost of the product life cycle. According to PMI, gold plating should be avoided at all costs. It is best to deliver what the client asked for – no less and no more. The outcome of this process is an approved detailed project scope statement. It should detail what is in scope and what is out of scope and can be referenced during the project as a guideline. WBS dictionary is an output of this process. WBS is the work breakdown structure and the dictionary lists all the definition of tasks/terms in the project. These are the scope baseline of the project and they feed into the scope statement. In the Project Scope Management the processes include: -Plan Scope Management is the process in which the Scope Management Plan is developed. -Collecting requirements is by a dialogue where the client sends you requirements and business analysts are involved in clarifying the requirements that are unambiguous. This happens during planning process group. - Defining Scope for the product or project. This happens during Planning process group of the project. Once you have the scope, you create work breakdown structure (WBS). WBS is a decomposing of work to smaller tasks. This happens during the Planning Process Group. Validate scope is getting a signoff from the client for end product. Please refer to page 145 or Rita Mulcahy’s book for an illustration. This happens during monitoring and controlling. Control scope happens during monitoring and controlling. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-6

Scope Management Processes
Note to Kamran: Can this be animated so that each row is highlighted as it’s being mentioned in the narration? Process Process Group Plan Scope Management Planning Collect Requirements Define Scope Create WBS Validate Scope Monitoring and Controlling Control Scope The Scope Management processes are: Plan Scope Management Collect Requirements Define Scope Create WBS Validate Scope Control Scope The Plan Scope Management, Collect Requirements, Define Scope, and Create WBS processes are part of the Planning Process Group The Validate Scope and Control Scope processes are part of the Monitoring and Controlling process group PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-7

Review Quiz Which one of the following is not a process in Scope Management? Plan Scope Management Create WBS Verify Scope Plan Requirements The correct answer is C. Verify Scope is not a Scope Management process. The correct name of the process is Validate Scope. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-8

5.1 Plan Scope Management Output is Scope Management Plan Documents how scope will be defined, validated, and controlled Describes how project scope will be managed and how scope changes will be integrated into the project Plan Scope Management is the process that creates the Scope Management Plan. The Scope Management Plan documents how the scope will be defined, validated, and controlled. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-9

Project Scope Statement
What needs to be done to accomplish the requirements Information from Sponsor about risk, budgets and schedule Input for planning process group High level WBS, Cost estimates and scheduling milestones Measurement of success and acceptance criteria Need to be revised or refined to reflect approved changes Helps understanding of project scope among all stakeholders Provides documented basis for making future project decisions In the Scope statement, you state what will be part of the project and what is excluded from it. To complete the Scope Statement, information is needed from sponsors about the budget, risks and time schedule. These are your constraints. It is best to understand the constraints before starting the project. The Scope Statement is an input to the planning process. At this stage, the Work Breakdown Structure or WBS is at a high level. Decomposing it further will happen in the later stage. Part of the Scope Statement is a measurement of success and acceptance criteria. What is considered a failed product? What is considered an accepted product? You have to agree with the client on the measurement scale for your product or project. If you know the expectations then it is easier to meet them. Scope has to be constantly reviewed in any project. Therefore, scope statement is most often reviewed and changed. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-10

5.2 Collect Requirements Collect requirements is the – Process of defining and documenting stakeholders needs to meet the project objectives Defining and managing customer expectations Foundation of WBS, Cost, Schedule and quality planning May consist of project and product requirements Project requirements include business /project management/delivery requirements Product requirements include technical/security, performance requirements As we discussed in an earlier slide, collect requirements is the process of defining and documenting the client’s or stakeholders needs to meet the project objectives. Collect requirement is the foundation for WBS. WBS cannot be created without proper requirements or knowledge of activity that you are supposed to do. From WBS, estimated schedule and budget is generated. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-11

Review Quiz In the context of Scope Management, in which process would the techniques of interviews, focus groups, prototypes, and benchmarking be utilized? Plan Scope Management Collect Requirements Validate Scope Create WBS The correct answer is B. These are some of the tools and techniques utilized in the Collect Requirements process in Scope Management. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-12

Perform Requirement Analysis
This chart illustrates Perform Requirement Analysis relating to Stakeholders, people behavior, and user experiences and highlights the overlapping of various analysis. At the beginning of the project, the project manager must check the stakeholder register and see who are the stakeholders and what are their requirements. Project Manager has to asses if the stakeholders are supportive of the initiative or if any are against the project. Project manager then determines the communication plan with the stakeholders. Each stakeholder might have a different requirement or mode of communication. The communication plan should detail the method of communication with the stakeholders and the frequency of the interaction. At the end of this activity, there will be a definitive set of requirements and an output will be a requirement management plan. Now that the Project Manager has the requirements, they would have to be maintained. Requirement management plan details how the requirements will be managed throughout the project. Requirement Traceability matrix is a tool that is utilized to track people role and responsibilities assigned to them. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-13

5.2.1 Collect Requirements Inputs and Outputs
Class Group Activity – 30 Minutes Divide Class into 3 groups (3 to 4 students in each group) Discuss and brainstorm the inputs/outputs Present your inputs/outputs to the rest of the teams Check and compare your inputs/outputs with PMBOK® Guide 5th edition No Script. Class Activity. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-14

5.3 Define Scope Define Scope is the– Process of developing a detailed description of project/product Product Scope: Features and function that characterize a product or service Project Scope: Work that may be done to deliver a product with the specified feature and functions Results in preparation of a detailed Project Scope Statement, critical to project success Project Scope Statement is based on deliverables, assumptions, constraints documented during project initiation Developed during the planning process Analyze existing assumptions, constraints Once the requirements are defined, we start to add more details to them in the Define scope process where we take the requirements and determine what is in scope or not in scope. By definition, define scope is a process of developing a detailed description of the project or a product that is being developed. In define scope a written project statement is developed that consists of the Product and Project Scope. The result is a Project Scope Statement depicting the details of the project. The Scope statement lists the product or service that will be delivered at the end of the project. During project initiation, it is very important to include all the details on deliverables, assumptions, and constraints to ensure that the understanding of all the stakeholders is captured. You can have a multi-phased approach where a preliminary scope statement is prepared initially during initiation phase. This also helps in getting sign-offs from the client at an early stage. After gathering all the information, a final scope statement can be developed during the planning process. A multi-phased approach is usually considered in larger and complex projects. PMBOK now has another box specifying Tools and Techniques. The tools used in developing Scope Statement include Expert judgment from SMEs (Subject Matter Experts), Product analysis, Identifying alternatives, and workshops (Project manager might want to hold workshops with the end users). PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-15

5.3.1 Define Scope Inputs and Outputs
Class Group Activity – 15 Minutes Divide Class into 3 groups (3 to 4 students in each group) Discuss and brainstorm the inputs/outputs Present your inputs/outputs to the rest of the teams Check and compare your inputs/outputs with PMBOK® Guide 5th edition No Script. Class activity. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-16

5.4 Create WBS Create WBS is – Process of subdividing project deliverables and project work into smaller/more manageable components Decomposition of work to be executed by project team Each descending level of WBS represents an increasingly detailed definition of project work WBS organizes and defines total scope of project and represents work specified in the approved Project Scope Statement Work Packages are the lowest level WBS components Work Package can be scheduled, cost estimated, monitored and controlled Work in a WBS refers to work products or deliverables which is a result of the efforts Now that we have collected the project requirements and defined scope, the Project Manager or the team decomposes the work into smaller and smaller work packages that are detailed and defined. This process is called create WBS or Work Breakdown Structure. WBS is created for the purpose of better estimating of time and cost for the project. Estimate of Time and cost at the work package level and then it is rolled up for the entire project to get the overall project timeframe and cost. Developing WBS also helps in the management and controlling of the project as it is easier to track down the activity at the work packages level. How far do you decompose? The idea is to breakdown the project to smaller components that are easy to tack. The lowest level is the work package level. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-17

5.4.1 Create WBS Inputs and Outputs
Class Group Activity – 15 Minutes Divide Class into 3 groups (3 to 4 students in each group) Discuss and brainstorm the inputs/outputs Present your inputs/outputs to the rest of the teams Check and compare your inputs/outputs with PMBOK® Guide 5th edition No Script. Class Activity. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-18

This illustration is an example of a Work breakdown structure
This illustration is an example of a Work breakdown structure. As you will notice, the activities list is generated in the WBS which will then be used to set milestones. Source: PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-19

This illustration details the Work Breakdown Structure levels 1, 2 and 3 for an aircraft manufacturing unit. Source: PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-20

Advantages Of WBS Provides project team with an understanding of all tasks associated with the overall project plan Facilitates communications and co-operation between and among project team and stakeholders Indicates the impact of their work on the project as a whole and helps prevents changes Provides basis for estimating staff, cost, time… Justifies need for staff, cost, time.. Helps team members to see the roles Work breakdown structure is an important document. It list the in-scope and out of scope activities and tasks. Work breakdown Structure helps with the communications and co-operation between project team members and the stakeholders. When the project is decomposed into the lowest level, it is easy to estimate costs and time it will take to complete tasks. WBS is also beneficial in justifying the need to acquire resources including staff. WBS helps project team with a clear understanding of all tasks and their role and responsibilities associated with them. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-21

Group Exercise Exercise Duration - 30 Minutes Divide Class into 3 groups (3 to 4 students in each group) Select a project and break it into various tasks as discussed with your instructor No Script. Class Activity. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-22

5.5 Validate Scope Validate Scope is the – Process of formalizing acceptance of completed project deliverables Reviews deliverables with customer or sponsor to ensure satisfactory completion Scope verification is acceptance of the deliverables while Quality control on the other hand is concerned with correctness of deliverables and meeting quality requirements specified for the deliverables Quality control is generally performed before scope verification; can also be performed in parallel Main outputs are Accepted deliverables The goal for Vdalidate Scope is to gain formal acceptance of the project scope from the client or stakeholders at the end of each milestone or at the end of the project. It is the process of formalizing acceptance of completed project deliverables. The output of Validate scope is accepted deliverables. Review of deliverables with the client or sponsor is conducted to ensure that all the expectation are met. Quality control on the other hand is concerned with meeting quality specifications for the deliverables, and it is usually performed before scope verification or in parallel with Verify scope. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-23

5.5.1 Validate Scope Inputs and Outputs
Class Group Activity – 15 Minutes Divide Class into 3 groups (3 to 4 students in each group) Discuss and brainstorm the inputs/outputs Present your inputs/outputs to the rest of the teams Check and compare your inputs/outputs with PMBOK® Guide 5th edition No Script. Class Activity PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-24

5.6 Control Scope Control Scope is the – Process of monitoring status of project/product scope Manages changes to the scope baseline Ensures that all requested changes, recommended corrective or preventive actions are processed through Perform Integrated Change Control process Manages actual changes when they occur Uncontrolled changes are often referred to as project scope creep Change is inevitable; mandates some type of change control process Main output is Work Performance Measurements Control Scope happens during the Monitoring and Controlling process group. It is the process of managing scope change and change requests. Project manager ensures that the scope is not getting too far from the baseline. Any uncontrolled changes in the project including cost or schedule changes are referred to as Scope Creep. As with any project, there are changes. Control scope mandates that there is some type of change control process. The main output of Control Scope process is Work Performance Measurements. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-25

5.6.1 Control Scope Inputs and Outputs
Class Group Activity – 15 Minutes Divide Class into 3 groups (3 to 4 students in each group) Discuss and brainstorm the inputs/outputs Present your inputs/outputs to the rest of the teams Check and compare your inputs/outputs with PMBOK® Guide 5th edition PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-26

Common Problems: Project Management
Manager task not effectively implemented Work breakdown structure too generic to be meaningful Gantt chart ignored Poor effort estimates Team effort doesn’t buy into plan Some of the common problems in Project Management arise because manager tasks are not implemented effectively. Another issue can be due to the work breakdown structure being to generic and not defined well to have any meaning. Scheduling problems may not get detected if proper tool such as the Gantt chart is not utilized in project management . Other common problems in Project Management are poor effort estimates and lack of team buy-in the project, which can cause motivational issues and therefore delays of quality issues. This completes Ch 5. Please proceed to the next chapter on Time Management. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-27

Chapter Summary Project Scope Management Purpose Importance Scope Management processes: Plan Scope Management Collect Requirements Define Scope Create WBS Validate Scope Control Scope 3. Plan Scope Management: Scope Management Plan Requirements Management Plan Here is a summary of the contents of this chapter: Project Scope Management is the Knowledge Area that involves defining the work that will be done on the project and making sure that work and ONLY that work is performed. If the scope is not defined and managed properly, the results could be disastrous for the project. As the illustration on slide 3 demonstrates, scope mismanagement could mean that a product is delivered to the customer that is nothing like the product the customer requested. The Scope Management processes are: Plan Scope Management Collect Requirements Define Scope Create WBS Validate Scope Control Scope Plan Scope Management is the process in which the Scope Management Plan is created. The Scope Management Plan defines how the project scope will be defined, managed, and controlled. The Requirements Management Plan is also created in the Plan Scope Management process. The Requirements Management Plan documents how the project and product requirements will be analyzed, documented, and managed. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-28

Chapter Summary 4. Collect Requirements Requirements Documentation Requirements Traceability Matrix 5. Define Scope Project Scope Statement 6. Create WBS WBS 7. Validate Scope Accepted Deliverables 8. Control Scope Work Performance Information and Change Requests The Scope Management Plan and the Requirements Management Plan becomes inputs to the Collect Requirements process. The project and product requirements are gathered and documented in the Collect Requirements process. Various tools and techniques are utilized to gather these requirements. The output of this process is Requirements Documentation and the Requirements Traceability Matrix. The Scope Management Plan and Requirements Documentation becomes inputs to the Define Scope process. In The Define Scope process, a detailed description of the project and product are developed. The main output of this process is the Project Scope Statement. The Project Scope Statement provides a detailed description of the project and product scope. It provides details on the deliverables of the project and the work required to produce those deliverables. The Project Scope Statement becomes an input to the Create WBS process. In the Create WBS process, the project work is broken down into manageable pieces components using the technique of decomposition. The main output of this process is the Scope Baseline, which consists of the Project Scope Statement, WBS, and WBS Dictionary. Validate Scope is the process that involves acceptance of the completed project deliverables. Accepted deliverables are the main output of this process. The Control Scope process involves monitoring the project and product scope and managing the scope baseline. Work Performance Information and Change Requests are the main outputs of this process. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-29

End of Chapter Question 1: Which one of the following is not a process in Scope Management? Plan Scope Management Create WBS Verify Scope Plan Requirements The correct answer is C. Verify Scope is not a Scope Management process. The correct name of the process is Validate Scope. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-30

End of Chapter Question 2: In which process is the Project Scope Statement created? Create WBS Create Project Scope Statement Plan Scope Management Define Scope The correct answer is D. The Project Scope Statement is created in the Define Scope process. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-31

End of Chapter Question 3: The project manager has detected that the client has added more work to the project. In which process is the project manager functioning? Change Control Control Scope Plan Scope Management Validate Scope The correct answer is B. In the Control Scope process, the project manager and team monitor the project and look for changes to the scope of work. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-32

End of Chapter Question 4: Project work is broken down into manageable tasks using which technique? Clustering Segmentation Decomposition Deconstruction The correct answer is C. Decomposition is the technique of breaking down the project work into manageable tasks. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-33

End of Chapter Question 5: A hierarchical structure that contains manageable units of work called work packages that can be used to estimate time and cost is called: WBS Project Scope Statement Requirements Traceability Matrix Project Management Plan The correct answer is A. The Work Breakdown Structure or WBS is a hierarchical structure that that is created using the technique of decomposition. The lowest level of a WBS are called work packages which are used to estimate time and cost for the project. PMP, CAPM, PgMP, PMI-SP , PMI-RMP, OPM3 and PMBOK are registered marks of Project Management Institute, Inc Inov8Solutions Inc – Quality Educational Services For Professionals 5-34

Chapter 5 Project Scope Management

Similar presentations

Presentation on theme: "Chapter 5 Project Scope Management"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Chapter 5 Project Scope Management

Similar presentations

Presentation on theme: "Chapter 5 Project Scope Management"— Presentation transcript:

Similar presentations

About project

Feedback