Project Scope Management Processes

Project scope management consist the process need to ensure that the project include all the work required to complete the project successfully. Its main concern is with defining and controlling what is required and what is not required in the project.
One of the primary causes of project failures is poor management of project scope, because the project manager or the business analyst does not spend enough required time on defining the work scope thoroughly or there was a lack of scope management process which leads to high chance of project failure
These process are:

Plan scope management- The scope management is related to the areas of cost, time and risk management of project so when the scope is not well defined, it may cause inconsistences and many failures that having the chance of happening throughout the project life cycle

Collecting requirements -Defining and documenting the features and functions of development process and product created during the different development stages. Using the different elicitation techniques like interview, focus group and facilitated workshops, JAD, questionnaires and survey, observation etc. can use to gather requirements from relevant stakeholders.

Defining scope-Reviewing the project requirements, project charter, documentations and organizational process assets helps to create Scope statements. It is a brief summary of the project constraints, assumptions and dependencies with other projects or a statement of what constitutes project success.
Creating Work Breakdown Structure- breaking the large project deliverables into smaller and more manageable components which helps easily track of the project progress and can timely delivery of smaller functionality to the stakeholders. With this the project manager or the business analyst will be able describe the results of a project in a way that is clear to the project team and at the meantime capture the order and sequence of the work which is necessary to produce these outcomes

Assigning the scope- Once all the work needed to achieve the project has been identified the our next step is to assign the work to the people responsible for accomplish the task and the input of work is WBS and the project schedule that identifies when each activity or task should occur and the Resource Requirements Matrix which identifies the skills required to accomplish the activities, this matrix used to select the project team.

Validating and verify the scope-Formalizing the acceptance criteria of project deliverables where delivered functionality meets the specifications of the project and it is used as a guarantee that the project is delivering the promised quality in its work.

Controlling change scope- Change to the scope may occur the new ideas that gained on the project changes in the original conditions or assumptions of the project for new opportunities arises . Changes are not only necessarily made to correct a situation but also could include changes in approaches or strategies that will impact the project scope. Project manager or business analyst should use the Project Scope Change Control Plan defined to manage the process or change request, obtain approval and incorporate and communicate the changes

Register Lessons Learned- At the end of each project development phase there is a need to capture the lessons learned in managing the project scope which include the causes or reason why something did not went according to plans and the causes that contributed to success, and the actions the project took to deal with an issue or challenge.