LO7 Scope Management

Question 1

Product Breakdown Structure

Answer 1

Hierarchical representation of products - clear unambiguous scope.
Product broken down into categories - deliverables allocated to suppliers / specialist.
Then broken down further - scope fully understood before work begins.
Presented to stakeholder to verify completeness.
Provides baseline and can be used to create WBS.

Question 2

Work Breakdown Structure

Answer 2

Graphical Hierarchical representation of activities required to produce the products in the PBS
Suppliers / specialists help identify these activities and developed WBS used for analytical (bottom-up) estimation of cost and level of effort.
Used to create work packages to handover to suppliers / specialists.
Ensures work fully costed and understood before work starts.

Question 3

Requirements Management - Gather Requirements

Answer 3

Early in project lifecycle.
Include SMEs and users.
What do they want - success criteria.
Output = centralised documented list of all functional and non-functional requirements.

Question 4

Requirements Management - Analysis

Answer 4

Gaps / overlaps / conflicts
Unique and verifiable
Traceable and trackable
Make sense of success criteria - USER STORIES
Solutions and constraints
Acceptance criteria

Question 5

Requirements management - baseline

Answer 5

Agreed and signed off (steering group)
Feeds solutions / options
Evaluate options - cost, time, budget, maturity
Changes subject to formal change control.
Agree priority of baselined requirements.
Common understanding of what project will achieve.
Valuable information for lessons learned.

Question 6

Config Management - Identification

Answer 6

Each item identified and given unique number
Accurate accounting and tracking
PBS used
Baseline for implementing any approved scope changes
Identifies items which do not require config management e.g. progress reports / logs - saves effort

Question 7

Config management - Verification and audit

Answer 7

Checks actual scope accurately reflected in config documentation prior to handover.
Helps mitigate risk of discrepancies.
Independent of project team - stakeholder confidence.
Input into lessons learned.

Question 8

Change control - Raise and log

Answer 8

Capture details of CR
Formal process
Change request form - allows further analysis of impact on scope, cost, schedule and resources
Provides confidence to team members that changes have controlled point of entry

Question 9

Change control - intitial evaluation

Answer 9

Decide whether to complete further analysis. Protects project from spending time / resources on changes that should not be implemented.
Decision point on funding further analysis.
Documented decisions input into lessons learned.

Question 10

Change control - update plans and implement

Answer 10

Implement and update documentation, config records etc.
Formal link between Change Control and Config Management
Successful transfer of product to BAU.
Comms to stakeholders to make them aware change has been accepted and status report re progress of implementation.

Question 11

Output

Answer 11

Tangible or intangible product delivered by project.

Question 12

Outcome

Answer 12

The changed circumstances or behaviour that results from the use of an output and leads to realisation of benefits.

Question 13

Benefit

Answer 13

Positive and measurable impact of change.