ABSTRACT
Defining a project The previous chapter discussed how every organization has a slightly different way of approaching the official launch of a project. However, one of the core requirements is to identify the PM and key stakeholders. The basic roles for a charter were also discussed which consisted of formally giving delegation of authority to the PM and formally displaying management approval for the project. The objective of this chapter is to address the next step in the launch process which is to develop the scope planning. This that yields a scope management plan and the scope definition results in an updated scope management plan, scope statement and requested changes to the project scope (PMI 2008). Before reading this chapter, it is important to first understand the definition for a scope management plan and scope statement. PMI (2008) describes a scope management plan as how the project scope will be defined, developed, and verified. It will also describe how the WBS will be created and defined. Therefore, the scope management plan provides guidance on how the project scope will be managed and controlled by the PM and the team. It is contained within or a subsidiary of the project management plan. A project scope statement contains a description of the project scope which consists of information such as the deliverables, assumptions, constraints, and a description of the work that is to be accomplished by the project. The scope statement for the project is documented, so it will be the basis for making future project decisions and for confirming or developing a common understanding of project scope among the stakeholders.
