Project scope 
Project scope is the parameter of the project. It defines what are the deliverables, requirements and expectations for the project and provides a baseline to exclude unrelated works. The project manager’s job is to ensure all necessary works for the project success are included. And this process is referring to as the project scope management.
Project scope management involves six processes, which are planning scope management, collecting requirements, defining scope, creating WBS, validating scope and controlling scope. These six interrelated steps provide an agreement between the stakeholders and project team to clarify expectation and requirements. The six processes also allow the team to understand how and what they should do in order to deliver the project within the deadline and without exceeding limited resources.
1. Planning scope management: This process answers the question “how will the team manage and maintain the scope” and “how to prepare required documents”. The team will review the project description from the project charter and project management plan to develop scope management plan and requirements management plan. The scope management plan defines how to prepare, maintain and control all management documents such as project scope statement, WBS and change requests. This step set the foundation for the scope management, as the team and manager will choose the most efficient way in controlling the process.
2. Collecting requirements: After defining the format of scope management, the team will need to meet with stakeholders as early as possible to determine what are the deliverables. There are many ways in collecting requirements such as interviewing stakeholders, hosting community meeting or workshop, handing out survey or questionnaires. This is a critical step because the more defined the deliverables are, the smaller the chance in changing deliverables. The cost of changing the scope or deliverables is higher at the later phase of the
Project scope management involves six processes, which are planning scope management, collecting requirements, defining scope, creating WBS, validating scope and controlling scope. These six interrelated steps provide an agreement between the stakeholders and project team to clarify expectation and requirements. The six processes also allow the team to understand how and what they should do in order to deliver the project within the deadline and without exceeding limited resources.
1. Planning scope management: This process answers the question “how will the team manage and maintain the scope” and “how to prepare required documents”. The team will review the project description from the project charter and project management plan to develop scope management plan and requirements management plan. The scope management plan defines how to prepare, maintain and control all management documents such as project scope statement, WBS and change requests. This step set the foundation for the scope management, as the team and manager will choose the most efficient way in controlling the process.
2. Collecting requirements: After defining the format of scope management, the team will need to meet with stakeholders as early as possible to determine what are the deliverables. There are many ways in collecting requirements such as interviewing stakeholders, hosting community meeting or workshop, handing out survey or questionnaires. This is a critical step because the more defined the deliverables are, the smaller the chance in changing deliverables. The cost of changing the scope or deliverables is higher at the later phase of the