5. Scope Management Processes 1. . 3. Scope Requirements Scope
DefinitionManagement Plan Definition and Verification 5. 4. Project
closeout Scope Control and scope and Reporting assessment
6. Scope Management Processes 1. 2. 3. Scope Requirements Scope
DefinitionManagement Plan Definition and Verification 5. 4. Project
closeout Scope Control and scope and Reporting assessment
7. Scope Management Processes 1. 2. 3. Scope Requirements Scope
DefinitionManagement Plan Definition and Verification 5. 4. Project
closeout Scope Control and scope and Reporting assessment
8. Scope Management Processes 1. 2. 3. Scope Requirements Scope
DefinitionManagement Plan Definition and Verification 5. 4. Project
closeout Scope Control and scope and Reporting assessment
9. Scope Management Processes 1. 2. 3. Scope Requirements Scope
DefinitionManagement Plan Definition and Verification 5. 4. Project
closeout Scope Control and scope and Reporting assessment
10. 1. Scope Management Plan How will requirements be gathered
and documented? How will changes to scope be controlled? How will
scope management processes be reviewed?
11. 2. COLLECTING REQUIREMENTS Is defining and documenting
stakeholders needs in order to meet the objectives of the project
Requires documenting the needs and expectations of the sponsor and
other key stakeholders Enables stakeholder expectations to be
clarified
12. 3. Scope DefinitionThe scope statement must initially
contain clear descriptions of :-Project Goal: the overall purpose
of the projectProject Objectives: what the project is aiming to
achieveProject Deliverables: what products or services be produced
toachieve the objectivesThe scope statement then defines what work
will be done to achievethe objectives and deliverables
13. Project Objectives Concise statements of what the project
is to achieve Specific Measurable Achievable Relevant Timely Agreed
Define Measure and Evaluate
14. DeliverablesA deliverable is a product or service that the
project will produce.Project deliverables must be agreed before the
project begins.Examples of deliverables for a project to build a
new swimming pool:- Swimming pool (built to specification) Pool
cover Warranty documents Maintenance manual
15. 3. Scope StatementThe scope statement defines what work
will be done to achieve the objectives and deliverables and what
work will not be included in the project (but could be assumed by
the customer to be included)
16. 3. Scope StatementOUTCOMES Provides a basis for defining
work to be done and resources needed Improved accuracy of project
estimates Enables review, verification and approval of scope by
stakeholders Enables any later changes to be defined and
controlled
17. Scope Statement Example Swimming Pool ConstructionIn Scope
Out of ScopePool (built according to specification) Landscaping
around poolPool cover Pool heaterWarranty (2 years)Maintenance
manual
18. Other sections to include in yourscope statementPROJECT
CONSTRAINTS A constraint is something that will put a restriction
on your project e.g. Two week closedown over Christmas
19. Other sections to include in yourscope statement
(cont)PROJECT ASSUMPTIONS An assumption is what you assume to be
true but there is a risk that it may not be e.g. You may assume
that there will be no rock to excavate when you dig the hole for
the pool. Risk: you may need special equipment and more time if you
strike rock.
20. Other sections to include in yourscope statement
(cont)RELATED PROJECTS These are projects that will have an impact
on your project or will be impacted by it. It is important to see
the whole picture
21. Develop a Scope Statement Needs Identify stakeholders &
their needs DeterminationWHAT?WHEN? Establish project objectives
and deliverablesHOW?HOW? Define scope, constraints, assumptions
(risks) Project appraisal Define what is not in scopeHOW? (but
stakeholders may assume is in scope) ( Approval and confirmation
Verification and Approval Scope Statement
22. SCOPE CREEPSmall changes to projects are often difficult to
detect butmay build to large changes that cause project problems
Scope creep is common early in projects Can be caused by client
requirements for additional features, new technology, poorly
defined requirements/design, unidentified assumptions/risks Can
alter: The organisations cash flow requirements Project resource
requirements Time to deliver Quality May have a flow-on impact on
other projects
23. CHANGE TO SCOPE Scope changes can be positive and even
necessary e.g. Legislative changes Company policy changes
Correction of specification errors Requires that: The original
baseline is well defined and agreed with the client Clear
procedures are in place for authorising, documenting and
communicating the change Affected project areas are adjusted
quickly, e.g. time and cost
24. CHANGE TO SCOPE Consider the human impact Frequent changes
to scope can be demoralising for the team and can result in the
project goals being altered. This impacts team cohesion, affects
project rhythm and lowers productivity
25. CHANGE CONTROL PROCESS
26. CHANGE CONTROL PROCESS1. Log the change Complexity Change
CR# STATUS Title Description Proposer Date Logged Impact
Description Comment (H,M,L) Cat-egory
27. CHANGE CONTROL PROCESS 2. Define the change and the
solutionProject / System / Process Affected: Change
Title:Description & Reason for Change:Other options
considered:Impact of Not Implementing Change:
28. CHANGE CONTROL PROCESS3. Assess the impact time, cost ,
quality, resources, riskImpactsCustomer: Business: Technical:Select
CommentsCost Variance $ Benefits Variance $
RiskScopeMilestonesResourcesQualityOther [specify]
29. CHANGE CONTROL PROCESS 4. Accept or reject the changeChange
Request FormChange Request Approval:Project Sponsor Signature: .
Date:
30. CHANGE CONTROL PROCESS5. Update documentation6. Communicate
the changeControl Document Affected:Project Brief Budgets /
BenefitsBusiness Case Milestone PlanConcept Paper Business
RequirementsProject Management Plan Technical DocumentsScope
Project Schedule
31. ASSESSING SCOPEMANAGEMENT Review the scope management
processes and determine performance Did you achieve your objective?
Did you deliver everything you committed to? Did you have scope
creep? What lessons can be learned about scope management? Which
tools and techniques have you used? Were they useful and what did
you learn? How will you transfer your lessons learned to
others?
32. End of Module 3 (ScopeManagement)You now need to complete
the following Scope assignments for your case study project and
submit them to your tutor.1. Scope Statement2. Change control