Change management is the process required to coordinate modifications in Scope.  It involves the following key steps: (1) Stakeholder identifies a change, (2) Review of the request, (3) Submission of the change to the CCB, (4) CCB approves or rejects the change, (5) If approved, coordinate the change, (6) Implement the change, (7) Measure the results, (8) Inform the CCB and stakeholders.

Scope creep refers to situations in which the scope of work gets out of control.  This problem can arise when there is: (1) Poor requirements analysis, (2) Inadequate stakeholder engagement, (3) Underestimation of the complexity, (4) Lack of change control, (5) Weak project management and coordination.

Scope verification involves formal acceptance of the project Scope by stakeholders and management.  This is typically achieved through: (1) Planning of the Scope process, (2) Collection of requirements, (3) Defining the Scope, (4) Creating a WBS, (5) Conducting internal workshops and brainstorming sessions to actively test the validity of the WBS, (6) Engaging management, stakeholders, clients and users to conduct a detailed review, (7) Once all changes have been implemented, conduct a formal sign off by all key stakeholders.

Good Scope management is essential to ensuring that a project can be completed successfully.  When developing this Scope, aim to ensure that the following is achieved: (1) Ensure that all Scope is focused on meeting the objectives, (2) Ensure that the descriptions are clear and scope all activities required to achieve the separate elements of the deliverables, (3) Identify overlaps and dependencies, (4) Define what is in or out of Scope, (5) Outline acceptance criteria, (6) Explain assumptions and their ramifications.

(1) Stakeholder identifies a change, (2) Review the request, (3) Submission of change to CCB, (4) CCB approves or rejects the change, (5) If approved, coordinate the change, (6) Implement the change, (7) Measure the results, (8) Notify the CCB and stakeholders.

(1) Identification Number, (2) Short Name, (3) Work package description, (4) Assigned to, (5) Estimated cost, (6) Account code, (7) Acceptance criteria, (8) Deliverables, (9) Assumptions.

(1) Identify project objectives, (2) Define the deliverables, (3) Outline the Scope description, (4) Explain the acceptance criteria, (5) Characterise exclusions, (6) Describe any constraints, (7) List any assumptions that have been made, (8) Outline the approach and resources needed.

(1) Elicitation, (2) Analysis - a. Analyse individual activities, b. Analyse individual procedures, c. Analyse organisational activities, d. Analyse organisational frames, (3) Specification (technical and other systems), (4) Validation.