Project Scoping Flashcards
Project scoping definition
planning and documentation of how the Engineer is going to undertake the required task
Product Scope
- features and functions that characterise a product, service or result
- all about the product itself
Project Scope
- the work performed to deliver a product, service or result, with the specified features and functions
- all about the project
Project Brief definition
a document that provides a summary of the idea or task, how you imagine it working, and what work needs to be done to get there
Elements of a good Project Scope
- project objectives
- goals
- tasks
- sub-phases
- resources
- budget
- schedule
- constraints
- assumptions
Project Justification
statement regarding the needs the project addresses
Tasks
the specific activities required to deliver the end product
Methodology
description of how to complete all tasks
Sub-phases
tasks within tasks, often running in parallel
Gateways
hold points against which approval must be received prior to progressing to the next task
Resources
personnel, tools and materials to be employed on each task in order to develop and deliver the Product Scope in accordance with the project scope
The Budget
a constraint defined within the Project Scope
- it can cover the product scope and/or the project scope
Product Scope Budget
the available or target cost for a product
Project Scope Budget
the available fees or remuneration available in undertaking tasks to deliver the product
- how the engineer earns a living
The Schedule
a programme or sequence that individual tasks will be undertaken in order to deliver the Project scope
- will often include milestones that must be achieved prior to other tasks commencing
Project Scope constraints
rules or limits within which a project must be delivered and are binding on all parties
Examples of Project Scope constraints
- terms and conditions (the contract)
- deadlines and milestone dates
- budget
- geometric or property
- material choice
- standards
- minimum requirements
- lines of communication
Project Scope Assumptions
decisions made in the preparation of a Project Scope that determine the way a project will be developed/managed
- assumptions are statements about how you will address uncertain information as you conceive, plan and perform your project
Examples of Project Scope Assumptions
- budget
- task breakdown and sequence
- inclusions and exclusions
- programme
- resource requirements
Who is the product scope prepared by
Typically by the CLIENT
Who is the project scope determined by
either the CLIENT or the ENGINEER, and typically BOTH
Scope Creep
uncontrolled changes or continuous growth in a project’s scope
- typically regarded as harmful
- common place
Causes of Scope Creep
- poor change control
- lack of proper initial identification of what is required to bring about the project objectives
- weak project management or leadership
- poor communication between parties
- lack of initial product versatility
- can occur when the scope of a project is not properly defined, documented or controlled
Results of Scope Creep
- cost overrun
- program delays
- reputational damage
Not scope creep
if the budget, resources and schedule are increased along with the scope, the change is usually considered an acceptable addition to the project (a variation) and the term “scope creep” is not used
Scope of Works Factors
- Project Management
- Budget
- Schedule
- Communication
