Project Scoping Flashcards
What is project scoping?
The planning and documentation of how the engineer is going to undertake the required tasks
What are the 4 main sections for scope of works?
- project management
- budget
- schedule
- communication
Project Management includes:
- point of accountability
- understanding of big picture
- maintain project control
Budget includes:
- monitor burn rate
- monitor efforts
- review of financials
Schedule includes:
- identify critical path
- represents big picture
- coordinates trades
Communication includes:
- focussed efforts
- proactive links
- PM intiated
The Product scope defines:
All about the product/ service features and functions
What the product will look like, how it will work, its features, etc.
The Project scope defines:
- requirements of the product
- work required to create
- defines also what is not in the scope to avoid scope creep
What comes first, product or project scope?
The product scope.
Must have a clearly defined product scope in order to develop a well-defined project scope.
Benefits of understanding scope:
- foundation for managing project change and risk management
- enables goal setting and a timeline to work towards
- key points for reporting on progress
What is a project brief?
A document that provides a summary of the idea or task and what work needs to be done to get there
Who is the project brief shared with?
People working on the project so they understand how the end product is achieved
Elements of a good project scope include:
- project objectives
- goals
- tasks
- sub-phases
- resources
- budget
- schedule
- constraints
- assumptions
What makes up a project scope?
- project objectives
- project justification
- product scope
- goals
- tasks and sub-phases
- gateways
- resources
- budget (product scope budget, project scope budget)
- schedule
- constraints
- assumptions
Examples of constraints:
- terms and conditions
- deadlines and milestone dates
- budget
- geometric or property
- material choice
- standards
- minimum requirements
- lines of communication
Examples of assumptions in project scope:
- budget
- task breakdown and sequence
- inclusion and exclusions
- programme
- resource requirements
Who prepares the product scope?
Typically the client.
Who prepares the project scope?
The client of the engineer, and typically both.
The client may issue a request with a few constraints or tender document
The engineer completes the project scope with assumptions, tender submission
Negotiated between client and consultant/ contractor
Who manages compliance with the project scope?
Typically compliance is managed where it best sits ( client or contractor)
What is scope creep?
Uncontrolled changes or continuous growth in a project’s scope.
Typically regarded as harmful to the project
When does scope creep occur?
When the scope of the project is not properly defined, documented or controlled.
Scope creep can be a result of:
- poor change control
- lack of proper initial identification of what is required to bring about the project objectives
- weak project management
- poor communication between parties
- lack of initial product versatility
Not scope creep when
budget, resources and schedule are increased along with the scope.
