 The project scope statement defines what are we going to do for our project.

If you
recall, it's one of the three elements of the iron triangle, along with cost and schedule
 Project scope statements can be divided into two parts: 1- product scope - what we will
deliver to the customer and 2- service scope - what work we will do to deliver the
product.
 The project scope statement is just one but essential part of the project scope
management. The scope management process starts in the planning stage of a project.
 A Project Charter, Stakeholder, and Prototype are the key requirements or deliverables
needed to be collected and analyzed to complete the project scope.
The Scope Management plan describes the project scope and documents how it will be further
defined, validated, and controlled.

The documentation of the scope of the project will explain the boundaries of the project,
establish the responsibilities of each member of the team, and set up procedures for how a work
that is completed will be verified and approved. This documentation may be referred to as the
scope statement, the statement of work, or the terms of reference./ The project scope statement
describes the fundamental goals of the process, it describes the benchmark again we are going
to be judged.

 Collection of requirements could be from project charter or the project contract.

However, if these requirements are hidden:
 The first approach is to read and incorporate available data in the
requirements traceability matrix (review the project charter, contract, bid
documents, or specifications, to the extent they exist.
 The next step is to survey the stakeholders (Face-to-face interviews,
facilitated workshops, formal surveys or questionnaires).
 Look to similar products and projects to incorporate similar requirements
that have been used in the past.
 To be considered a successful project: to satisfy technical requirements, organization's
strategic goals and the overall quality requirements for the product or service.
 Review requirements:
 Reconcile conflicting requirements.
 make sure each requirement has a single meaning and that any ambiguity
is removed
  To develop Requirements Traceability matrix: Track requirements, links each
requirements to business value and ensure that each requirement is included in the
project.
 The approved project scope statement becomes our agreement on the products and
services we will deliver as part of the project. It also includes the agreed acceptance
criteria that outline how we will know that we've met the requirements. It includes the
approved requirement matrix
 Scope validation is a confirmation by the customer, and other identified stakeholders, that
the deliverables from the project meet their needs. Inputs: Requirements, Traceability
matrix and checked deliverables. Tools & techniques used: Inspection and Group
decision making. Output: Accepted deliverables, defected deliverables, request for
requirements change,
 Scope control process is important in managing project by identifying, evaluating,
controlling, and approving changes of the project. In order to deliver our project on an
agreed schedule and budget, we must control the scope. Good scope control includes:
 Key attributes: Documented and approved process, contains layers of
authority (project approval, change control board approval, executive
approval), adapted to organization and project needs, based on validated
scope, accepted process to modify the baseline, outline roles and
responsibilities, change requests must be writing, benefits of changes
+roles +responsibilities +approval process must be documented, decision
authorities must be appointed and agreed, approved changes must be
incorporated in the plan, scope changes must be communicated and a set
of standardized tools used.
 Key roles: originator (person requesting the change), coordinator (person
who records the proposed change in the change log and shepherds it
through the process), assessment body (evaluates the change and makes
recommendation) and decision makers (authority to approve the change)
and implementers (mambers acting on a change).
 Each proposed change has to be documented in Change Log. It contains a
record of all the proposed changes, ID, origination date, originator,
description of the impact, assessment (cost, schedule, quality impacts),
disposition and approvals and approvals dates. / it should be published in
monthly reports.

The project scope statement describes the fundamental goals of the process, it describes the
benchmark again we are going to be judged. The scope control process is a way we continually
compare ourselves to that benchmark and make adjustments to the projects scope management
plan.
Question 1
Talk about a project that you've worked on that was affected by scope creep. Based on what you've
learned so far in the course, what are some things you could have done to keep the project in
scope?

I was working as a part of program manager team responsible to handle the management of a
project and to ensure a proper coordination between the customer and the service providers. The
scope of the project is to design, implement, operate, and maintain a distribution network with
customer and metering services. The project scope was really solid and all the parties were
agreed on during several workshops and meetings at the beginning of the project. The first phase
of the project was the preparation of services related to project mobilization in terms of vehicles,
equipment, and personnel required to prepare for a seamless and organized transition of
responsibilities with the existing division staff of the respective service territory which the
Service Provider is awarded. In addition, the service provider has to refurbish and set up all
existing area offices with all necessary equipment and this task was supposed to be conducted
within 2 months. However, some of the customer’ employees were against the implementation of
the project so they refused to cooperate with the program manager and service providers so
instead of facilitating the SP’s works they asked for some unnecessary changes and additional
requirements. Actually we had to accept their requests in order to maintain a good work
environment between SP and the customer’ employee and of course to get their approval on the
implemented works and hence to be eligible for payment. Unfortunately, this issue has extended
the deadline of the mobilization task. Although that the “Change to the Scope Services” section
was clearly added in the project scope management plan, but it didn’t elaborate the details of
“Change Requests” in terms of what is in scope and what is out of scope and how to raise the
change of without affecting the timeline and cost of each task and hence of the whole project. In
our case, we had to include in the Change management plan, that not all the customer’
employees are eligible to ask unnecessary requests from the Service Providers and any requested
change has to be communicated first to the Head of Division in order to prioritize the requests
before communicating them to the Service provider.

however to had to agreed Based on this experience, I think that in order to avoid such problem
we had to

In order to convince them we we had to conduct several site visits for the same division in order
to ensure that
during the implementation of the project we had to face a shortage in some electrical materials
need for construction works. Accordingly,