Summary - Project Scope Planning

In the previous chapters, we have successfully completed the Project Scope Planning section of Project Planning. Let us quickly summarize the key points we learnt in this topic.

• After a project has been initiated, the project management plan is developed to specify how the project at hand will be executed, monitored & controlled, and closed.
• The project management plan can contain subsidiary plans, such as a quality management plan, a risk management plan, a project scope management plan, and a scope baseline.
• The scope baseline consists of the project scope statement, work breakdown structure (WBS), and WBS dictionary.
• Collecting requirements is part of the scope planning, which creates requirements documentation.
• The project charter and requirements documentation are used to define the scope, which creates the project scope statement.
• The project scope statement is a document that defines the scope of a project, including the product scope, by stating what needs to be accomplished by the project.
• It includes project deliverables, product description, product acceptance criteria, assumptions and constraints, and project exclusions.
• The project scope statement and requirements documentation are input items to creating the work breakdown structure (WBS), which is a breakdown of project deliverables into manageable pieces called work packages, which in turn are used to develop the project schedule.
• The WBS is supported by another document called the WBS dictionary, which offers details for the WBS components.
• The scope statement, the WBS document, and the WBS dictionary combined constitute the scope baseline against which all change requests are evaluated.
• The WBS is the heart of project management, as it is used in managing many aspects of the project, including developing the schedule.

Previous: Before & After WBS

Next: Important Terms - Project Scope Planning

Summary - Introduction to Project Management Topics

Let us quickly summarize what we learnt in the previous chapters about the basics of Project Management:

• The activities inside an organization are generally organized into groups, which fall into two categories: operations and projects.
• Operations usually consist of ongoing routine work, whereas a project has a goal to generate a unique product, service, or result in a fixed time frame i.e.,, it has a planned beginning and a planned end.
• Organizations launch projects for different reasons, such as to meet a business or legal requirement or to take on an opportunity offered by the market.
• A project, like anything else in an organization, needs to be managed.
• Project management is the application of knowledge and skills to project activities in order to meet the project objectives.
• It involves performing a set of processes that constitute nine knowledge areas of project management:
      o Communication management
      o Cost management
      o Human resource management
      o Integration management
      o Procurement management
      o Quality management
      o Risk management
      o Scope management and
      o Time management.
• Each process is part of a knowledge area and has a membership in one of the five process groups:
      o Initiating
      o Planning
      o Executing
      o Monitoring & controlling and
      o Closing.
• The process groups represent different stages of a project lifecycle.
• Each project has a set of individuals or organizations that it influences positively or negatively, and these individuals and organizations are accordingly called positive and negative stakeholders.
• Some of these stakeholders may influence the project. Therefore, you must identify all the project stakeholders, positive and negative.
• The different project stakeholders might have different and conflicting expectations, which you as the project manager need to analyze and manage.
• The project environment consists of elements such as organizational culture, organizational structure, enterprise environmental factors, and organizational process assets.
• The structure of the performing organization could be functional, projectized, or matrix.
• In a Functional Organization project managers don't have much authority whereas in a projectized organization, the project manager is king. And there is the matrix organization which can be a combination of either extremes.
• Some organizations have a composite structure, which is a hybrid of these three basic structures.
• A project can be standalone or part of a program, which is a collection of interrelated projects and possibly non-project work.
• A project can also be part of a portfolio, which is a collection of programs, projects, and other related work.


Previous: Big Picture of Project Management

Next: Important Terms & Definitions