Project scope management

Question 1

project scope management

Answer 1

defining all the project work, and perform all the required work

Question 2

6 processes

Answer 2

1. plan scope management, planning how to do the other processes. This defines, create, validate and control.
2. collect requirements, get specific information
3. define scope, create scope statement reduce to written form
4. create WBS, scope deliverable with wbs to visualize what needs to be done.
5. validate scope, after create project deliverables sponsor inspect and validate the scope which leads to acceptance.
6. control scope, keep things on target, deliver what is needed and prevent unapproved changes. change request flows back to integrated change control process.

Question 3

8/80 Rule

Answer 3

A planning heuristic for creating the WBS. This rule states that the work package in a WBS must take no more than 80 hours of labor to create and no fewer than 8 hours of labor to create.

Question 4

Active observation

Answer 4

The observer interacts with the worker to ask questions and understand each step of the work being completed. In some instances, the observer could serve as an assistant in doing the work.

Question 5

Affinity diagrams

Answer 5

When stakeholders create a large number of ideas, you can use an affinity diagram to cluster similar ideas together for further analysis. similar to brainstorming, group ideas into clusters

Question 6

Alternatives generation

Answer 6

A scope definition process of finding alternative solutions for the project customer while considering the customer’s satisfaction, the cost of the solution, and how the customer may use the product in operations.

• benchmarking
• systems
• vendors
• materials
• resources

Question 7

Autocratic

Answer 7

A decision method where only one individual makes the decision for the group.

Question 8

Brainstorming

Answer 8

This approach encourages participants to generate as many ideas as possible about the project requirements. No idea is judged or dismissed during the brainstorming session.

Question 9

Change control system (CCS)

Answer 9

Documented in the scope management plan, this system defines how changes to the project scope are managed and controlled.

Question 10

Change management plan

Answer 10

This subsidiary plan defines how changes will be allowed and managed within the project.

Question 11

Code of accounts

Answer 11

A numbering system for each item in the WBS. The PMBOK is a good example of a code of accounts, as each chapter and its subheadings follow a logical numbering scheme. For example, PMBOK 5.3.3.2 identifies an exact paragraph in the PMBOK.

Question 12

Configuration management plan

Answer 12

This subsidiary plan defines how changes to the features and functions of the project deliverables will be monitored and controlled within the project.

Question 13

Context diagram

Answer 13

These diagrams show the relationship between elements of an environment. For example, a context diagram would illustrate the networks, servers, workstations, and people that interact with the elements of the environment.

Question 14

Focus groups

Answer 14

A moderator-led requirements collection method to elicit requirements from stakeholders.

Question 15

Functional analysis

Answer 15

This is the study of the functions within a system, project, or, what’s more likely in the project scope statement, the product the project will be creating. Functional analysis studies the goals of the product, how the product will be used, and the expectations the customer has of the product once it leaves the project and moves into operations. Functional analysis may also consider the cost of the product in operations, which is known as life-cycle costing.

Question 16

Funding limit

Answer 16

Most projects have a determined budget in relation to the project scope. There may be a qualifier on this budget, such as plus or minus 10 percent based on the type of cost estimate created.

Question 17

Interviews

Answer 17

A requirements collection method used to elicit requirements from stakeholders in a one-on-one conversation.

Question 18

Majority

Answer 18

A group decision method where more than 50 percent of the group must be in agreement.

Question 19

Mind mapping

Answer 19

This approach maps ideas to show the relationship among requirements and the differences between requirements. The map can be reviewed to identify new solutions or to rank the identified requirements.

Question 20

Nominal group technique

Answer 20

As with brainstorming, participants are encouraged to generate as many ideas as possible, but the suggested ideas are ranked by a voting process 1-5.

PM asks for many ideas and solutions as possible, then rank the concepts to help guide the requirements development

Question 21

Passive observation

Answer 21

The observer records information about the work being completed without interrupting the process; sometimes called the invisible observer.

Question 22

Plurality

Answer 22

A group-decision method where the largest part of the group makes the decision when it’s less than 50 percent of the total. (Consider three or four factions within the stakeholders.)

Question 23

Product acceptance criteria

Answer 23

This project scope statement component works with the project requirements, but focuses specifically on the product and what the conditions and processes are for formal acceptance of the product.

Question 24

Product breakdown

Answer 24

A scope definition technique that breaks down a product into a hierarchical structure, much like a WBS breaks down a project scope.

Question 25

Product scope description

Answer 25

This is a narrative description of what the project is creating as a deliverable for the project customer.

Question 26

Product scope

Answer 26

Defines the product or service that will come about as a result of completing the project. It defines the features and functions that characterize the product. Features and functions.

Question 27

Project assumptions

Answer 27

A project assumption is a factor in the planning process that is held to be true but not proven to be true.

Question 28

Project boundaries

Answer 28

A project boundary clearly states what is included with the project and what’s excluded from the project. This helps to eliminate assumptions between the project management team and the project customer.

Question 29

Project constraints

Answer 29

A constraint is anything that limits the project manager’s options. Consider a predetermined budget, deadline, resources, or materials the project manager must use within the project—these are all examples of project constraints.

Question 30

Project objectives

Answer 30

These are the measurable goals that determine a project’s acceptability to the project customer and the overall success of the project. Objectives often include the cost, schedule, technical requirements, and quality demands.

Question 31

Project requirements

Answer 31

These are the demands set by the customer, regulations, or the performing organization that must exist for the project deliverables to be acceptable. Requirements are often prioritized in a number of ways, from “must have” to “should have” to “would like to have.”

Question 32

Project scope

Answer 32

This defines all of the work, and only the required work, to complete the project objectives. the required work in order to satisfy the objective.

Question 33

Project scope management plan

Answer 33

This project management subsidiary plan controls how the scope will be defined, how the project scope statement will be created, how the WBS will be created, how scope validation will proceed, and how the project scope will be controlled throughout the project.

Question 34

Requirements documentation

Answer 34

This documentation of what the stakeholders expected in the project defines all of the requirements that must be present for the work to be accepted by the stakeholders.

Question 35

Requirements management plan

Answer 35

This subsidiary plan defines how changes to the project requirements will be permitted, how requirements will be tracked, and how changes to the requirements will be approved.

Question 36

Requirements traceability matrix (RTM)

Answer 36

• This is a table that maps the requirements throughout the project all the way to their completion.
• name
• link to business and project objectives
• project scope and wbs entry
• relevant data, coding, cost or schedule
• status as active, cancelled, deferred, etc.

Question 37

Schedule milestones

Answer 37

The project customer may have specific dates when phases of the project should be completed. These milestones are often treated as project constraints.

Question 38

Scope creep

Answer 38

Undocumented, unapproved changes to the project scope.

Question 39

Scope validation

Answer 39

The formal inspection of the project deliverables, which leads to project acceptance.

Question 40

Stakeholder analysis

Answer 40

A scope definition process where the project management team interviews the stakeholders and categorizes, prioritizes, and documents what the project customer wants and needs. The analysis is to determine, quantify, and prioritize the interests of the stakeholders. Stakeholder analysis demands quantification of stakeholder objectives; goals such as “good,” “satisfaction,” and “speedy” aren’t quantifiable.

Question 41

Systems analysis

Answer 41

A scope definition approach that studies and analyzes a system, its components, and the relationship of the components within the system.

Question 42

Systems engineering

Answer 42

This project scope statement creation process studies how a system should work, designs and creates a system model, and then enacts the working system based on the project’s goals and the customer’s expectations. Systems engineering aims to balance the time and cost of the project in relation to the scope of the project.

Question 43

Unanimity

Answer 43

A group decision method where everyone must be in agreement.

Question 44

Value analysis

Answer 44

As with value engineering, this approach examines the functions of the project’s product in relation to the cost of the features and functions. This is where, to some extent, the grade of the product is in relationship to the cost of the product.

Question 45

Value engineering

Answer 45

This approach to project scope statement creation attempts to find the correct level of quality in relation to a reasonable budget for the project deliverable while still achieving an acceptable level of performance of the product.

Question 46

WBS dictionary

Answer 46

A WBS companion document that defines all of the characteristics of each element within the WBS.

• code of account details
• description of work
• assumptions and constraints
• responsible organization
• list of schedule milestone
• associated schedule activities, etc.

Question 47

WBS template

Answer 47

A prepopulated WBS for repetitive projects. Previous projects’ WBSs are often used as templates for current similar projects.

Question 48

ITTOs & Work breakdown structure (WBS)

Answer 48

A deliverables-oriented breakdown of the project scope. decomposition of the project scope. deliverable oriented, visualizes the project, deterrent to change, what is in scope and out of scope

• inputs: pm plan, scope management plan, project documents, project scope statement, requirement documents, EEFs and OPAs
• Tools and techniques: expert judgment, decomposition
• Outputs: WBS, scope baseline, project documents updates of assumption log, requirement docs

Question 49

Work package

Answer 49

The smallest item in the WBS.

Question 50

Work performance information

Answer 50

Status of the deliverables: the work that’s been started, finished, or has yet to begin.

Question 51

Planning Project Scope Management

Answer 51

Creates two project management subsidiary plans:

1. Scope management plan
2. requirements management plan

Question 52

ITTOs Plan Scope Management

Answer 52

• Inputs: project charter, project management plan, quality management plan, project life cycle description, development approach, EEFs and OPAs
• Tools & Techniques: expert judgment, data analysis, alternatives analysis, meetings
• Outputs: scope management plan , requirements management plan

Question 53

business analysis

Answer 53

• gathering requirements
• need assessment, understand the problem what trying to solve
• collaborate with PM to identify problems, define business needs, recommend solutions
• elicit, document, and manage stakeholder requirements in order to meet business and project objectives
• facilitate the successful implementation
• BA has requirements responsibilities
• PM has project delivery responsibilities

Question 54

considerations for adaptive environments

Answer 54

• scope is not fully defined at start
• process for scope refinement
• emerging requirements in adaptive

Question 55

Inverted Triangle

Answer 55

• in predictive: scope is fixed where time and cost varies aka triple constraints
• in adaptive: time and cost is fixed where scope varies aka agile traingle of constraints

Question 56

Groom the Backlog

Answer 56

adaptive environment:

• product owner owns the backlog
• backlog refinement is the prioritization backlog items
• entire project team may participate in the backlog grooming: team can do this much work in this timeframe

Question 57

collecting Project Requirements

Answer 57

• process of determining, documenting, and managing requirements
• can collaborate with Business analyst
• requirements help define the product scope and project scope
• can be collected upfront if the predictive environment or collect throughout if adaptive
• collect requirements performed once or at predefined points

Question 58

ITTOs Collect Requirements

Answer 58

• Inputs: project charter, PM plan, scope management plan, requirements management plan, stakeholder engagement plan, project documents, assumption log, lessons learned register, stakeholder register, business documents, business case, agreements, EEFs and OPAs
• Tools and Techniques: expert judgment, data gathering, brainstorming, interviews, focus groups, questionnaire, surveys, benchmarking, data analysis, document analysis, decision making, voting, data representation, mind mapping affinity diagrams, team and interpersonal skills, meetings, context diagram, prototypes
• Outputs: requirements documentation, requirements traceability matrix

Question 59

Managing Requirements 6 types

Answer 59

1. business requirements: higher-level needs of organization
2. stakeholder requirements: needs of stakeholders
3. solution requirements: features, functions and characteristics of the product service, functional describe behavior of product, nonfunction describe environmental conditions or qualities ex ergonomic
4. transition requirements: current state to future state
5. project requirements: actions, processes, or other conditions
6. quality requirements: validate successful completion of a project deliverable or fulfillment

Question 60

define scope

Answer 60

• project scope statement
• scope baseline: project scope statement, project wbs, project wbs dictionary
• adaptive: define high-level vision, detailed scope by iteration

Question 61

ITTOs Define Scope

Answer 61

• Inputs: project charter, pm plan, scope management plan, project documents, assumption log, requirement documents, risk register, EEFs, OPAs
• Tools & Techniques: expert judgement, data analysis, multicriteria decision analysis, decision making, interpersonal and team skills, facilitation, product analysis
• Outputs: project scope statement, project documents updates, assumption log, requirement docs, requirement traceability matrix, stakeholder register

Question 62

Product Analysis

Answer 62

• product breakdown
• requirement analysis
• systems analysis
• systems engineering
• value engineering
• value analysis

Question 63

ITTOs & validate scope

Answer 63

• inspection driven processes
• customer inspects the project work
• phase and project completion
• review, audits, walkthroughs
• leads to formal project acceptance
• inputs: pm plan, scope management plan, requirement plan, scope baseline, project docs like lesson learned register, quality reports, requirement docs, RTM, verified deliverables, work performance data
• Tools and techniques: inspection, decision making, voting
• Outputs: accepted deliverables, work performance information, change requests, project docs updates, lesson learned, requirement docs, RTM

Question 64

ITTOs & controlling Project Scope

Answer 64

• monitor status of the project and product scope
• maintain scope baseline integrity, keep project in scope
• inputs: pm plan, scope management plan, requirements management plan, change management plan, configuration management plan, scope baseline, performance measurement baseline, project docs, lesson learned register, requirement docs, RTM, work performance data, OPAs
• tools and techniques: data analysis, variance analysis, trend analysis
• outputs: work performance information, change requests, pm plan updates, scope schedule cost baselines updates, performance measurement baseline, project docs updates, logs, lessons learned, requirement docs, RTM