Project Scope Management Flashcards

1
Q

ITTOs: Plan Scope Management

A

Inputs:

  • Project Charter
  • Project Management Plan (Quality management plan, project life cycle, development approach)
  • EEFs
  • OPAs

Tools&Techniques:

  • Expert judgement
  • Data analysis
  • Meetings

Outputs:

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

Scope management plan

A
  • Defines how scope will be defined, developed, monitored, controlled and validated
  • Project Charter is the key input
  • Historical information from prior projects and EEFs will drive this as well
  • Is NOT the project scope statement
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Requirements Management Plan

A
  • How will you plan, track and report requirements activities
  • Configuration management activities
  • Requirements prioritization process
  • ## Metrics that will be used
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Requirements Traceability Matrix

A
  • Table that outlines the requirements, assumptions, status, details
  • Can also link the requirements to WBS
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Project Scope vs. Product Scope

A
  • Product scope = features and functions of the product we are delivering
  • Project scope = work to be completed in order to satisfy the project objectives
  • Product scope drives the project scope (symbiotic)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Product Scope

A
  • Characteristics of customers’ deliverables
  • Product backlog is adaptive
  • Derived from collected requirements
  • Will be validated at the end of the project to confirm that the scope was met
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Tailoring Scope Management Processes

A
  • Determine how much knowledge and requirements management is needed
  • What level of validation and control is needed
  • Development approach (scrum vs. agile)
  • How specific or stable are the requirements? how much flexibility is there?
  • Governance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Business Analyst

A
  • Gathers and defines requirements
  • Ensures that the requirements are met
  • Identify problems
  • Define the business needs
  • Recommend viable solutions for needs
  • Works collaboratively with the PM or can be the same persion
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Scope Management in Adaptive Environments

A
  • Scope is not fully defined at the start
  • Scope is refined over the life of the project
  • Requirements can emerge throughout the project
  • Time and cost are fixed but scope can vary
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Grooming the Backlog/Backlog Refinement

A
  • Product owner owns the backlog

- Product owner prioritizes the backlog items and adds new ones before the next sprint or iteration

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

ITTOs: Collect Requirements

A

Input:

  • Project Charter
  • Project management plan
  • Project Documents
  • Business case
  • Agreements
  • EEFs
  • OPAs

T&T:

  • Expert judgement
  • Data gathering (interviewing stakeholders, focus groups, questionnaires and surveys, bechmarking)
  • Data Analysis
  • Decision making
  • Data representation
  • Context Diagram
  • Prototypes

Outputs:

  • Requirements documentation
  • Requirements traceability matrix
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Benchmarking the Requirements

A
  • Comparing two or more system, businesses and approaches

- Set an external basis for performance

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

User stories

A
  • Items in the product backlogs
  • Defines the role (who benefits from the feature), goal (what the stakeholders aim to accomplish), motivation (benefit to the stakeholder)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Business Requirements

A
  • High level needs of the organization
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Solution Requirements

A
  • Features, functions and characteristics of the product or service
  • Functional - behaviors of the product (ex. amount of torque)
  • Nonfunctional - environmental conditions or qualities (ex. how much it hurts your hand when you turn it)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Stakeholder requirements

A
  • Needs of a stakeholder or stakeholder group
17
Q

Transition requirements

A

how to get from current state to future state (operational transfer)

18
Q

Project requirements

A
  • Actions, process or other conditions
19
Q

Quality requirements

A
  • Validation of the success of the project
20
Q

Defining the project scope statement

A
  • Developing a detailed description of the project and product
  • Describes the product, service or result
  • Establishes boundaries and acceptance criteria (what will and will not be included)
21
Q

Scope Baseline

A
  • Scope Statement
  • WBS
  • WBS dictionary
22
Q

ITTOs: Define Scope

A

Inputs:

  • Project Charter
  • Project Management Plan
  • EEFs
  • OPAs

T&T:

  • Expert judgement
  • Data Analysis
  • Decision making
  • Interpersonal and team skills
  • Product analysis

Outputs:

  • Scope statement
  • Project documents updates
23
Q

Project Charter vs Project Scope

A
  • Charter is higher level and more about project purpose

- Scope is more specific and is more about deliverables

24
Q

Work Package

A
  • Smallest item in the WBS

- Particular function that a particular function does or window in the project to build a house

25
ITTOs: Create WBS
Inputs: - Project management plan - Project documents - EEFs - OPAs T&T: - Expert judgement - Decomposition Outputs: - Scope baseline - Project document updates
26
Control Account Plan
- For work packages | - Way of segmenting different aspects of the project and defining what threshold that segment can't exceed (ex. budget)
27
Code of Accounts
- Numbering system/unique identifier in the WBS
28
What is in the WBS Dictionary?
- Code of account identifier - Description of work - Assumptions and constraints - Responsible organization - List of schedule milestone - Associated schedule activities - Resources required - Cost estimates - Quality requirements - Acceptance criteria - Technical references - Contract information
29
ITTOs:Validate Scope
Inputs: - Project Management Plan - Project Documents - Verified Deliverables - WPA Tools & Techniques - Inspection - Decision Making Outputs: - Accepted Deliverables - WPI - Change Requests - Project docs updates
30
ITTOs: Control Scope
Inputs: - Project Management Plan - Project Documents - WPD - OPA T&T: - Data Analysis (Variance & Trends) Outputs: - WPI - Change Requests - PMP Updates - Project Doc updates
31
Variance Analysis
- Performance measurements comparison - Magnitude of variation (high or low) - Determine cause and degree of variance - Analysis drives what corrective or preventative actions are needed
32
Trend Analysis
- Noticing a trend over time - Earned Value Management is a part of this - Improving or deteriorating - Degree of variance - Analysis drives corrective or preventative actions