Project Scope Management Flashcards

1
Q

What is project scope managment?

A

Project scope management includes processes required to ensure that the project includes all the work required and only the work required to complete the project successfully.

  • primarily concerned with defining and controlling what is and is not included in the project.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What are the processes in project scope management?

A

Processes in project scope management are:

  1. Plan scope management
  2. Collect requirements
  3. Define scope
  4. Create WBS (work breakdown structure)
  5. Validate scope
  6. Control scope
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is plan scope management process?

A

The PLAN SCOPE MANAGEMENT process is creating the scope management plan that documents how the project and product scope will be defined, validated and controlled.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is scope in the project context?

A

Scope in a project context, refers to:

  • Product scope - functions and features that characterize the product, service or result.
  • Project scope - the work performed to deliver the product, service or result with the specified product scope.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is the scope baseline?

A

The scope baseline is the approved version of the project scope statement, work breakdown structure (WBS) and WBS dictionary.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are inputs to the plan scope management process?

A

Inputs to the plan scope management process are:

  1. Project Charter
  2. Project managemment plan:
    • Quality management plan
    • Project life cycle description
    • Development approach
  3. Enterprise environmental factors
  4. Operational process assets
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the tools and techniques used in plan scope management process?

A

Tools and techniques used in plan scope management process are:

  1. Expert judgement
  2. Data analysis -> alternatives analysis
  3. Meetings
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the outputs of plan scope management process?

A

The outputs of plan scope management process ar;

  1. Scope management plan
  2. Requirements Management plan
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is the requiements management plan?

A

The requirements management plan is also referred to as business analysis plan describes how project requirements will be analyzed, documented and managed.

  • how requirement activities will planned, tracked and reported
  • configuration management activities such as how changes will be initiated, how impacts will be analyzed, how they will traced, tracked and reported as well as the authorization levels required to approve those change.
  • requirements prioritization process
  • metrics that will be used and the raionale for using them
  • traceability structure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is a requirement?

A

A requirement is a condition or capability that is required to be present in a product, service or result to satisfy a contract or other formally impossed speciication.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is collect requirements process?

A

Collect requirements process is the process of determining, documenting and managing stakeholders needs and requirements to meet objectives.

Key benefit is that it provides basis for defining project scope and product scope.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are inputs to collect requirements process?

A

Inputs to COLLECT REQUIREMENTS process are:

  1. Project Charter
  2. Project management plan
    1. 1 Scope management plan
    2. 2 Requirements management plan
    3. 3 Stakeholder Engagement plan
  3. Business Document such as Business case
  4. Project documents
    1. 1 Assumption log
    2. 2 Lessons learned register
    3. 3 Stakeholder register
  5. Agreements
  6. Enterprise environmental factors
  7. Operational process assets
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the tools and techniques used in collect requirements process?

A

Tools and techniques used in Collect Requirements are:

  1. Expert judgement
  2. Data gathering
    1. 1 Brainstorming
    2. 2 Focus group
    3. 3 Interviews
    4. 4 Questionnaires and surveys
    5. 5 Benchmarking
  3. Data Analysis ie. document analysis
  4. Decission making
    1. 1 Voting (unaniminity everyone agrees to a single course of action , majority > 50% of the group supports the idea, plurality largest block in a group decides even if majority is not reached)
    2. 2 autocratic decision making
    3. 3 multicriteria decision analysis
  5. Data representation
    1. 1 Affinity diagrams (large number of ideas are grouped for review and analysis)
    2. 2 mind mapping (consolidates ideas from individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas)
  6. Interpersonal and team skills
    1. 1 Nominal group technique (enhances brainstorming with voting)
    2. 2 Observation/ conversation
    3. 3 Facilitation
      1. 3.1 Joint application design/development (JAD)
      2. 3.2 Quality function deployment (QFD)
      3. 3.3 User stories
  7. Context Diagram
  8. Prototyping (eg. storyboarding)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are the outputs of Collect Requirements process?

A

Outputs of collect requirements process are:

  1. Requirements documentation (describes how individual requirements meet the business need for the project)
    1. 1 Business Requirements
    2. 2 Stakeholder requirements
    3. 3 Solutions requirements (functional requirements and non-functional requirements)
    4. 4 Transition and readiness requirements
    5. 5 Project requirements
    6. 6 Quality requirements
  2. Requirements traceability matrix (a grid that links the product requirement from the origin to the deliverables that satisfy them)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is define scope process?

A

DEFINE SCOPE is the process of developing detailed description of the project and product.

  • Key benefit is that it describes the product, service or result boundaries and acceptance criteria.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the inputs to define scope process?

A

Inputs to define scope process are:

  1. Project charter
  2. Project management plan
    1. 1 Scope management
  3. Project documents
    1. 1 Assumption log
    2. 2 Requirements documentation
    3. 3 Risk register
  4. Enterprise environmental factors
  5. Organizational process assets
17
Q

What are the tools and techiniques used in define scope?

A

Tools and techniques used in define scope are:

  1. Expert judgement
  2. Data analysis i.e. alternatives analysis
  3. Decission making - Multicriteria decission analysis
  4. Interpersonal and Team skill : Facilitation
  5. Product analysis
    1. 1 Product breakdown
    2. 2 Requirements analysis
    3. 3 Systems analysis
    4. 4 Systems engineering
    5. 5 Value analysis and
    6. 6 Value engineering
18
Q

What are the outputs of define scope process?

A

The outputs of define scope process are:

  1. Project scope statement which contains:
    • project scope description (progressively elaborated)
    • project deliverables
    • acceptance criteria
    • project exclusions
  2. Project document updates
    1. 1 Assumption log
    2. 2 Requiremens documentation
    3. 3 Requirements traceability matrix
    4. 4 Stakeholder register
19
Q

What is project scope statement?

A

Project scope statement is the description of the project scope, major deliverables and exclusions.

  • documents the entire scope, including project and product scope
  • describes the project’s deliverables in detail
  • provides common understanding of project scope among stakeholders
  • has explicit exclusions that can assist in managing stakeholder expectations
  • provides the baseline for evaluating whether requested work is within or outside the project’s boundaries
20
Q

What is Create WBS process?

A

Create WBS is the process of subdividing project deliverables and project work into smaller manageable components.

  • provides the framework of what has to be delivered
21
Q

What are the inputs to Create WBS process?

A

Inputs to the create WBS process are:

  1. Project management plan
    • Scope management plan
  2. Project documents
    1. 1 Project scope statement
    2. 2 Requirements documentation
  3. Enterprise environmental factors
  4. Operational process assets
22
Q

What is a WBS (Work breakdown structure)?

A

A work breakdown structure (WBS) is a heirarchical decomposition of the total scope of the work to be carried out by the project team to accomplish the project objectives and create required deliverables.

23
Q

What is a work package?

A

A work package is the lowest level of the WBS where planned work is contained.

  • can be used to group activitities where work is scheduled, estimated, monitored and controlled.
  • associated to a single control account.

NOTE: work in WBS refers to work products or deliverables that are the result of activity and not the activity itself

24
Q

What are the tools and techniques used in create WBS process?

A

Tools and techniques used in create WBS process:

  1. Expert judgment
  2. Decomposition
25
Q

What is decomposition?

A

Decomposition is a technique used to dividing and subdividing project scope and project deliverables into smaller and more manageable parts.

26
Q

What are the outputs of create WBS process?

A

Outputs of create WBS process are:

  1. Scope Baseline
  2. Project document updates
    1. 1 Assumption log
    2. 2 Requirement documentation
27
Q

What is the scope baseline?

A

Scope baseline is the approved version of the project scope statement, WBS and WBS dictionary.

28
Q

What is a control account?

A

A control account is a management control point where scope, budget and schedule are integrated and compared to the earned value for performance measurement
- a control account has two or more work packages

29
Q

What is a planning package?

A

A planning package is a work breakdown structure component below the control account and above the work package with known work content but without detailed schedule activities.

30
Q

What is Validate Scope?

A

Validate scope is the process of formalizing acceptance of the completed project deliverables.

Key benefit is it brings objectivity to the acceptance process and increases the probability of final product, service or result acceptance by validating each deliverable.

31
Q

What are inputs to Validate Scope?

A

Inputs to Validate Scope are:

  1. Project management plan:
    1. 1 Scope management plan
    2. 2 Requirement management plan
    3. 3 Scope baseline
  2. Project documents updates:
    1. 1 Lessons learned register
    2. 2 Quality reports
    3. 3 Requirements documentation
    4. 3 Requirements traceability matrix
  3. Verified deliverables
  4. Work performance data
32
Q

What are the tools and techiques in the Validate Scope?

A

Tools and techniques in Validate Scope are:

  1. Inspection
  2. Decision making i.e. voting
33
Q

What are the outputs of Validate Scope?

A

Outputs of Validate Scope are:

  1. Accepted deliverables
    - formal acceptance documentation is forwarded to Close Project or Phase process
  2. Work performance information
  3. Change requests
  4. Project documents updates:
    1. 1 Lessons learned register
    2. 2 Requirements documentation
    3. 3 Requirements traceability matrix
34
Q

What is Control Scope?

A

Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.

Key benefit is that scope baseline is maintained throughout the project.

35
Q

What are inputs to Control Scope?

A

Inputs to Control Scope are:

  1. Project management plan:
    1. 1 Scope management plan
    2. 2 Requirements management plan
    3. 3 Scope baseline
    4. 4 Configuration management plan
    5. 5 Change management plan
    6. 6 Performance measurement baseline
  2. Project documents
    1. 1 Lessons learned register
    2. 2 Requirements documentation
    3. 3 Requirements traceability matrix
  3. Work performance data
  4. Organization process assets
36
Q

What are tools and techniques of Control Scope?

A

Tools and techniques of Control Scope are:

  1. Data Analysis
    1. 1 Variance analysis
    2. 2 Trend analysis
37
Q

What are the outputs of Control Scope?

A

Outputs of Control Scope are:

  1. Work performance information
  2. Change requests
  3. Project management plan
    1. 1 Scope management plan
    2. 2 Scope baseline
    3. 3 Schedule baseline
    4. 4 Cost baseline
    5. 5 Performance measurement baseline
  4. Project documents updates
    1. 1 Lessons learned register
    2. 2 Requirements documentation
    3. 3 Requirements traceability matrix