0% found this document useful (0 votes)
21 views9 pages

Chapter 5 (Qusthion)

Uploaded by

maherarafat16
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views9 pages

Chapter 5 (Qusthion)

Uploaded by

maherarafat16
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 9

Assignment

1. All of the following are true about the project scope management plan EXCEPT:

- It enables the creation of the WBS from the detailed project scope statement.

- It describes how the scope will be defined, developed, monitored, controlled, andvalidated.

- It can be formal or informal, broadly framed or highly detailed, based on the needs of the

project.

- It is not related to the project management plan.

2. Collect Requirements is the process of determining, documenting, and managing stakeholder


needs and requirements to meet project objectives. All of the following are true about this process
EXCEPT:

- The project's success is directly influenced by active stakeholder involvement in the discovery and
decomposition of needs into requirements and by the care taken in determining, documenting, and
managing the requirements of the product, service, or result of the project.

- Requirements become the foundation of the WBS. Cost, schedule, quality planning, and sometimes
procurement are all based upon these requirements.

- The development of requirements begins with an analysis of the information contained in the
project charter, the risk register, and the stakeholder engagement plan.

- Requirements need to be elicited, analyzed, and recorded in enough detail to be included in the
scope baseline and to be measured once project execution begins.

3. You are involved in collecting requirements for your project. You are likely to use the stakeholder
register for all of the following EXCEPT:

- Identifying stakeholders who can provide information on the requirements.

- Capturing major requirements that stakeholders may have for the project.

- Capturing main expectations that stakeholders may have for the project.

- Evaluating the product breakdown structure (PBS) associated with each of the key

stakeholders.

4. You are developing a document that links product requirements from their origin to the
deliverables that satisfy them to help ensure that each requirement adds business value and to
manage changes to the product scope. This is known as the:
- Configuration management system.

- Business case.

- New product development matrix.

Requirements traceability matrix.

5. An output of the Define Scope process is:

- Work breakdown structure (WBS).

- Resource breakdown structure (RBS).

- Project scope statement.

- Scope and schedule delays control plan.

6. All of the following are true about the project scope statement EXCEPT:

- It is an output of the Validate Scope process.


- It describes, in detail, the project's deliverables and the work required to create those
deliverables.
- It provides a common understanding of the project scope among project stakeholders.
- It may contain explicit scope exclusions that can assist in managing stakeholder
expectations.

7. Which of the following statements is true about the work breakdown structure (WBS)?

- The WBS is a hierarchical decomposition of the total scope of work to be carried out by the
project team to accomplish the project objectives and create the required deliverables.
- The WBS is a simple list of project activities in chart form.
- The WBS is the same as the organizational breakdown structure (OBS).
- The WBS is the bill of materials (BOM) needed to accomplish the project objectives and
create the required deliverables.

8. The following is an example of a constraint associated with the project scope that limits the
team's options in scope definition:

- A predefined budget or any imposed dates or schedule milestones that are issued by the
customer or performing organization.
- The threat of a strike by a subcontractor.
- Existing relationships with sellers, suppliers, or others in the supply chain.
- The method used to measure project performance.

9. An input to the Define Scope process is:

- The type of contract detail language.


- Project charter.
- Work breakdown structure (WBS).
- Decomposition.
10. What is the WBS typically used for?

- To organize and define the total scope of the project.


- To identify the logical person to be project sponsor.
- To define the level of reporting that the seller provides the buyer.
- As a record of when work elements are assigned to individuals.

11. The following is true about the WBS:

- The WBS is another term for the bar (Gantt) chart.


- Each descending level of the WBS represents an increasingly detailed definition of the
project work.
- Work not in the WBS is usually defined in the scope statement of the project.
- The WBS shows only the critical path activities.

12. Which of the following is true about the Validate Scope process?

- It is the process of formalizing acceptance of the completed project deliverables.


- It is not necessary if the project completes on time and within budget
- - It occurs primarily when revisions or changes are made to project scope.
- Scope validation is primarily concerned with correctness of the deliverables, whereas
quality control is primarily concerned with acceptance of the deliverables and meeting the
quality requirements specified for the deliverables.

13. You are managing a global project that involves stakeholders in several international locations.
You are likely to consult the WBS dictionary to find:

- The language translation of technical terms used in the project.


- Detailed deliverable, activity, and scheduling information about each component in the
WBS.
- Information relating the legal constraints of relevant international locations to the
development of the WBS.
- Strengths, weaknesses, opportunities, and threats (SWOT) of key stakeholders and their
impact on the WBS.

14. Which of the following is NOT an output of the Control Scope process?

- Work performance information.


- Change requests.
- Project documents updates.
- Accepted deliverables.
15. All of the following are true about the Control Scope process EXCEPT:

- Control Scope is the process of monitoring the status of the project and product scope and
managing changes to the scope baseline.
Control Scope is used to manage the actual changes when they occur and is integrated with
the other control processes.
- Scope changes can be avoided by developing clear and concise specifications and enforcing
strict adherence to them.
- Controlling the project scope ensures that all requested changes and recommended
corrective or preventive actions are processed through the Perform Integrated Change
Control process.

16. describe capabilities that are temporary and are no longer needed after the new
product/service/result is ready.

- Business requirements
- Solution requirements
- Quality requirements
- Transition requirements

17. Agile scope planning is especially useful when:

- Solution requirements are emerging all the time.


- Quality requirements are not stable.
- Business requirements are not stable.
- Scope is well understood at the beginning.

Interactive Content
1. What is the lowest level of the WBS at which the cost and activity
estimates for the work can be reliably estimated and managed?
A) Work package
B) Scope baseline
C) Work product
D) Project deliverable

2. The team is committed to ensuring that each requirement adds


business value by linking it to the business and project objectives. Which
document should the team use to ensure this goal is met?
A) Requirements traceability matrix
B) Work breakdown structure (WBS) dictionary
C) Requirements documentation
D) Requirements management plan
3. Which document contains the information that describes how the
formal verification and acceptance of the project deliverables will be
obtained?

A) Communications management plan


B) Scope management plan
C) Statement of work
D) Scope verification document

4. Upon analysis, the client communicates that the deliverables


produced do not meet the acceptance criteria established. Given this
feedback, which process is it possible that the team did not complete
correctly?
A) Define scope
B) Control quality
C) Control scope
D) Validate Scope

5. Which group decision making technique involves utilizing a


structured, four-step brainstorming and voting method?
A) Nominal group technique
B) Voting
C) Facilitation
D) Multicriteria decision-making

6. Subdividing the major deliverables, determining their feasibility, and


identifying the tangible components of each deliverable are all part of
which of the following?
A) Organizational breakdown structure
B) Bill of materials
C) Work breakdown structure
D) Resource breakdown structure

7. Why are change requests often an output of the Validate Scope


process?
A) Any issue found with the verified deliverable requires that a change
request be submitted
B) Change requests are the result of acceptance of deliverables by the
customer in order to align
scope with customer requirements
C) Each change request has to be validated because it is considered
complete
D) If a verified deliverable is rejected upon inspection, a change request
can be created to repair the defect

8. Which of the following correctly explains the term "progressive


elaboration"?
A) Elaborating the tracking of the project progress
B) Changing project specifications continuously
C) Project specifications becoming more explicit and detailed as the
project progresses
D) Elaborating the tracking of the project specifications with a change
control system

9. You are leading your team in decomposing the WBS using a top-
down approach. Which of the following best describes the characteristic of
a work package.
A) Smallest amount of work for which cost and duration can be estimated
and managed
B) Individual deliverables
C) Groups of components within the WBS
D) Highest level of the WBS

10. What scope definition technique is used to generate different


approaches to execute and perform the project work?

A) Product analysis
B) Alternatives analysis
C) Expert judgement
D) Build vs. buy

11. Change is inevitable in most projects, but scope change can also
cause added time and cost to the project. You are creating a plan to
control how changes to the project scope will be permitted. This plan is
which one of the following ?

A) Change control system


B) Cost management plan
C) Project scope management plan
D) Risk management plan

12. Mary is the project manager for the HGQ Project. Her project is part
of a program in her organization. Thomas is the program manager, while
Joan is the project sponsor. Who creates the WBS
A) Mary
B) Thomas
C) Joan
D) Project team
13. A major component of project planning and management is the
project's work breakdown structure. The smallest item in WBS is called
what?
A) a leaf project
B) A task
C) A work package
D) A deliverable

14. Who is responsible for documenting all potential projects


requirements and ensuring that the correct decisions are made to select
which requirements are within or outside of the project's scope?
A) Project management team
B) Functional manager
C) Project sponsor
D) Customer

15. What is the method of obtaining early feedback on requirements by


providing a working model of the expected product before actually
building it?
A) Benchmarking
B) Context diagramming
C) Prototyping
D) Brainstorming

16. What is the correct order of scope management processes that are
used to successfully translate high-level requirements into a clear
objective scope defining the bounds of a project?
A) Plan Scope Management, Define Scope, and Create WBS
B) Collect Requirements, Define Scope, and Create WBS
C) Collect Requirements, Create WBS, and Define Scope
D) Create WBS, Collect Requirements, and Define Scope

17. Which of the following defines how the project requirements are to
be analyzed, documented, and managed?

A) Configuration management plan


B) Requirements management plan
C) Scope baseline
D) Schedule baseline

18. During the collect requirements process, not all of the needs may be
met!
A) True
B) False

19. Affinity Diagram is a technique used to consolidate ideas created


through individual brainstorming sessions into a single map to reflect
commonality and differences in understanding and to generate new ideas.
A) True
B) False

20. Define scope process may be started as soon as the collect


requirements process has been completed.

A) True
B) False

Lab 5.2
Match the statement with the project scope statement components given for a Game
Development Project.
1. The game must have fewer than 15 defects per 10,000 lines of
code.
- Acceptance Criteria
- Project Assumptions
- Project Constraints
- Project Exclusions
- Project Requirements

2. There will be four graphic designers reporting to the art director, and six programmers
and four testers reporting to the development manager.
- Acceptance Criteria
- Project Assumptions
- Project Constraints
- Project Exclusions
- Project Requirements

3. No more than 15 people can be allocated to work on the game at any time.

- Acceptance Criteria
- Project Assumptions
- Project Constraints
- Project Exclusions
- Project Requirements

4. Scenery artwork.

- Acceptance Criteria
- Project Assumptions
- Project Constraints
- Project Exclusions
- Project Requirements

5. The product will not include bug fixes for the previous version.

- Acceptance Criteria
- Project Assumptions
- Project Constraints
- Project Exclusions
- Project Requirements

6. The game needs to run on a machine with 1 GB of memory or less.

- Acceptance Criteria
- Project Assumptions
- Project Constraints
- Project Exclusions
- Project Requirements
Lab 5-4 Scope Validation vs Cont
1. Project and his team verifying the deliverables to check for variances.
- Validation
- Control

2. Classic Contracting Company had just completed a project phase. Project manager and the client
representatives are now inspecting deliverable for conformance.
- Validation
- Control

3. Project manager is performing variance analysis to understand the reason for scope creep.
- Validation
- Control

4. Project manager is raising a change request for defect repair.

- Validation
- Control

5. Three critical stakeholders conducting voting to decide whether the product is capable enough to
provide the required solution for acceptance.

- Validation
- Control

You might also like