Project Scope Management

The objectives covered in this chapter make up 9 percent of the exam, equivalent to about 12 questions. Study the whole chapter in detail.

  • PDF / 319,817 Bytes
  • 37 Pages / 439.37 x 666.142 pts Page_size
  • 60 Downloads / 179 Views

DOWNLOAD

REPORT


4 Project Scope Management The objectives covered in this chapter make up 9 percent of the exam, equivalent to about 12 questions. Study the whole chapter in detail. It’s enough to just remember the name of the input, tools and techniques, and outputs. You should know what is in a given input item that the given process uses and how that helps in generating the output, and what a given tool or technique does in a given process. You should be very clear about the elements and their purposes inside each component of the scope baseline: scope statement, Work Breakdown Structure (WBS), and WBS dictionary. While studying this knowledge area and its processes, pay attention to how the tasks can be tailored and adapted as needed, and recognize an agile environment in action; for example, continual assessment generates change requests which lead to changing plans—i.e., adapting.

© Paul Sanghera 2019 P. Sanghera, CAPM® in Depth, https://doi.org/10.1007/978-1-4842-3664-2_4

136

Chapter 4 | Project Scope Management

CAPM Exam Objectives Project Scope Management: 1. Understand the six project management processes in the project scope management knowledge area. 2. Identify the input, tools and techniques, and outputs defined in the six processes in project scope management. 3. Identify key concepts and tailoring consideration for project scope management and key roles in scope management. 4. Identify the purpose and elements of a Work Breakdown Structure (WBS) for both product and project scope. 5. Understand project scope management for agile/adaptive projects, including the use of prototypes.

After the project has been initiated, as discussed in the previous chapter, you need to develop a project management plan, which becomes the primary source of information for how the project at hand will be executed, monitored and controlled, and closed. The project plan development involves developing subsidiary plans, of which one important plan is the scope management plan. How important is the scope management plan? If a product is not in the scope, it will not and should not be produced. Before you start defining the scope, you need to know what the project and product requirements are. In other words, you need to collect requirements based on the needs and expectations of the stakeholders and in line with the project objectives. Once you have defined the scope based on these requirements, it needs to be broken down into concrete, manageable tasks that can be assigned and performed. This is accomplished through what is called the work breakdown structure (WBS). Planning and controlling the project scope is crucial to the success of the project. Without it, the project can easily go off track. The primary purpose of project scope management is to ensure that the required work (and only the required work) is performed to complete the project successfully. If changes in the work requirements are made, they must be controlled—that is, the scope must be controlled. Also, before the outcome of the project is offered for acceptanc