Proj. Mgnt - SCOPE (Topic 4)

0.0(0)
studied byStudied by 0 people
0.0(0)
full-widthCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/22

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

23 Terms

1
New cards

What is the 2nd stage of the project management process?

Planning

2
New cards

Name five key processes in planning.

  • Scope

  • Work Breakdown Structure (WBS)

  • Schedule

  • Cost

  • Risk.

3
New cards

Define project scope.

The work required to deliver the project.

4
New cards

What is scope creep?

Uncontrolled changes to project scope, adding unauthorized features or work.

5
New cards

What is a scope statement?

A written description of project scope, deliverables, assumptions, and constraints.

6
New cards

Why is a scope statement important? (4)

  • Guides team’s work during execution

  • Builds on charter by describing project deliverables in greater details and work needed to produce them

  • Develops common understanding among stakeholders

  • Aids detailed planning.

7
New cards

What are the key elements of a scope statement?

  • Scope description

  • Deliverables

  • Acceptance criteria

  • Exclusions

  • Constraints

  • Assumptions.

8
New cards

Why is “to design a bridge” a poor scope statement?

Too vague, lacks detail and measurable criteria.

9
New cards

Give an example of a good scope statement.

“To design a bridge that meets state road design standards, accommodates a 1-in-100 year flood, and complies with environmental regulations.”

10
New cards

Impacts of Scope creep (3)

  • Increased costs

  • Time delays

  • Project failure

11
New cards

Name sources of scope change. (5)

  • Errors / Omissions

  • Value-adding opportunities

  • Competitive pressures

  • Budget changes

  • Personnel changes

12
New cards

Why is a change control system needed

To manage inevitable changes and prevent scope creep.

13
New cards

What are steps in a change control system? (7)

  • Review requested changes

  • Identify impacts of change

  • Evaluate pros / cons of requested changes

  • Install a process so authorised individuals may accept or reject changes

  • Communicate change to concerned parties

  • Updates all documents (WBS, Cost, Schedule baseline)

  • Prepare reports that summarise changes to date their impacts

14
New cards

What is a WBS?

A visual, hierarchical outline of project deliverables and tasks.

15
New cards

What are two forms of WBS?

  • Graphical (tree) form

  • List (tabular) form

16
New cards

What are two approaches to creating WBS?

Top-down (start with overall deliverable) and bottom-up (start with tasks).

17
New cards

What are the steps to create a WBS? (5)

  1. Identify deliverables/sub-deliverables with team.

  2. Identify key deliverables from scope statement.

  3. Break deliverables into work packages.

  4. Create WBS dictionary (details of work packages).

  5. Share WBS with team.

18
New cards

What is a WBS dictionary?

Document describing deliverables in detail (owner, cost, schedule, quality requirements).

19
New cards

How is a WBS structured?

Top-down, more detail at each level.

20
New cards

What are characteristics of a WBS? (5)

  • Graphical hierarchy

  • Visualizes project

  • Created with team input

  • Prevents omissions

  • Aids communication.

21
New cards

What makes an effective WBS?

  • Covers all deliverables/milestones

  • Created by Project manager and team

  • Visual → info is easily grasped and organised

  • Adaptable & accessible → so team can access and act quick.

  • Be a living document → dependencies and risks can affect timeline / scope

22
New cards

Why is scope control critical? (2)

  • Prevent scope creep

  • Ensure project success.

23
New cards

Why is WBS critical?

Breaks project into manageable parts, aids planning, communication, and control.