5.0 Project Scope Management Flashcards
What type of projects use an approved version of the project scope statement, work breakdown structure (WBS), and its associated WBS dictionary as the scope baseline for the project?
a. Hybrid projects
b. Projects with adaptive life cycles
c. Predictive projects
d. Projects with waterfall life cycles
c. Predictive projects
In predictive projects, the scope baseline for the project is the approved version of the project scope statement, work breakdown structure (WBS), and its associated WBS dictionary. A baseline can be changed only through formal change control procedures and is used as a basis for comparison while performing Validate Scope and Control Scope processes as well as other controlling processes.
See Section 4 Key concepts for Project Scope Management
Requirement-related activities are the responsibility of which role within the Project scope Management Knowledge area?
a. Business owner
b. Project specialist
c. Business analyst
d. Project sponsor
c. Business analyst
When a business analyst is assigned to a project, requirement-related activities are the responsibility of that role.
See Section 5 Trends and Emerging Practices in Project Scope Management
Completion of the product scope is measured against which of the following?
a. Product deliverables
b. Product cost
c. Product life cycle
d. Product requirements
d. Product requirements
Completion of the project scope is measured against the project management plan, while completion of the product scope is measured against the product requirements. The term “requirement” is defined as a condition or capability that is required to be present in a product, service, or result to satisfy an agreement or other formally imposed specification.
See Section 5 Key Concepts for the Project Scope Management
Agile scope planning is especially useful when:
a. Scope is well understood at the beginning.
b. Quality requirements are not stable.
c. Solution requirements are emerging all the time.
d. Business requirements are not stable.
d. Business requirements are not stable.
Many environments with emerging requirements find that there is often a gap between the real business requirements and the business requirements that were originally stated. Therefore, agile methods purposefully build and review prototypes and release versions in order to refine the requirements. As a result, scope is defined and redefined throughout the project.
See Section 5 Considerations for Agile/Adaptive Environments
Which statement describes agile/adaptive environments?
a. Equal time is spent trying to define and agree on scope while establishing ongoing discovery.
b. No time is spent defining the scope; all efforts are spent on establishing ongoing discovery.
c. Less time is spent trying to establish a process for ongoing discovery, and more time defining and agreeing on scope.
d. Less time is spent trying to define and agree on scope, and more time is spent establishing the process for its ongoing discovery.
d. Less time is spent trying to define and agree on scope, and more time is spent establishing the process for its ongoing discovery.
In projects with evolving requirements, high risk, or significant uncertainty, the scope is often not understood at the beginning of the project or it evolves during the project. Agile methods deliberately spend less time trying to define and agree on scope in the early stage of the project and spend more time establishing the process for its ongoing discovery and refinement.
See Section 5 Considerations for Agile/Adaptive Environments
What is the difference between product scope and project scope?
PRODUCT SCOPE defines the features and functions of a product, service, or result
A REQUIREMENT is a condition or capability that should be present in a product, service or result to satisfy its specifications.
PROJECT SCOPE defines the work performed to deliver a product, service, or result with the specified features and functions.
- PROJECT SCOPE is dependent on product scope. If you don’t have a clear understanding of the product scope you can’t define the scope of the project.
- To create the product scope, you should understand the product’s requirements.
- To complete the project scope, compare it to the product scope and the project management plan.
What is the role of the Business analyst within the Project Scope Management process?
When a business analyst is assigned to a project, that person is responsible for defining, managing, and controlling requirements activities.
What is your role as a Project manager within the Project Scope Management process?
You are responsible for ensuring that requirements-related work is accounted for in the project management plan and requirements- related activities deliver value and are performed on time and within budget.
In predictive projects, the scope baseline for the project is the approved version of which document?
a. Project scope statement
b. Requirements documentation
c. Planning Package
d. Project scope description
a. Project scope statement
In predictive projects, the scope baseline for the project is the approved version of the project scope statement, work breakdown structure (WBS), and its associated WBS dictionary.
See Section 5 Project Scope Management, Key Concepts
Within the Project Scope Management Knowledge Area, Who is responsible for ensuring that requirements-related work is accounted for in the project management plan and that requirements-related activities are performed on time and within budget and deliver value?
a. Project Sponsor
b. Project Manager
c. Business Analyst
d. Project Specialist
b. Project Manager
The project manager is responsible for ensuring that requirements-related work is accounted for in the project management plan and that requirements-related activities are performed on time and within budget and deliver value.
See Section 5 Trends and Emerging Practices in Project Scope Management.
Which of the following is a tailoring consideration for Project Scope Management?
a. Project dimensions
b. Stability of requirements
c. Knowledge management
d. On-demand scheduling
b. Stability of requirements
Because each project is unique, you will need to tailor the way Project Scope Management processes are applied. Consideration for tailoring include but are not limited to: stability of requirements. are there areas of the project with unstable requirements? Do unstable requirements necessitate the use of lean, agile, or other adaptive techniques until they are stable and well defined?
See Section 5 Tailoring Considerations.
The process of formalizing acceptance of the completed project is which project management process associated with the Project Scope Management Knowledge Area?
a. Define Scope
b. Control Scope
c. Plan Scope Management
d. Validate Scope
d. Validate Scope
Validate Scope is the process of formalizing acceptance of the completed project deliverables. The key benefit of this process is that it brings objectivity to the acceptance process and increases the probability of final product, service, or result acceptance by validating each deliverable. This process is performed periodically throughout the project as needed.
See Section 5.5 Validate Scope
Project management includes which of the following?
a. Processes required to ensure that the product meets all the scope requirements to complete the project.
b. Processes required to ensure that the project includes all the work required–and only the work–required to complete the project successfully
c. Processes required to ensure that the project work is manageable to complete the project without error.
d. Processes required to ensure that the project is on schedule and under budget to complete the project.
b. Processes required to ensure that the project includes all the work required–and only the work–required to complete the project successfully.
Project Scope Management includes the processes required to ensure that the project includes all the work required–and only the work required–to complete the project successfully. Managing the project scope is primarily concerned with defining and controlling what is and is not included in the project.
See Section 5 Project Scope Management
