Quiz for Project Scope Management

Expert judgement, product analysis, alternative identification and facilitated workshops are the tools that determined to use for define scope process. [1 - 5.2 Define Scope: Tools and Techniques]

Project charter and stakeholder register are two documents are required for effectively collect requirements. The initial requirements and business case may not include enough information; some initial requirements or wishes may not be confirmed by project charter. The project stakeholders register will help to identify the right sources for the project or product requirements and their details. [1 - 5.1.1 Collect Requirements: Input]

After a scope is defined if must be formally approved before work starts. Other choices to be done before final approval of the project scope. [1 - 5 Project Scope Management]

High level project description, specifications of the product and requirements for project approval from project charter are used in the define scope process. [1 - 5.2.1.1 Define Scope: Inputs and 4.1.3.1 Project Charter]

Requirements documentation is one of the outputs of collect project requirements process. [1 - 5.1 Collect Requirements]

Plurality is one of the acceptable alternatives to reach a consensus within largest block even if majority within all group was not reached while using group decision making techniques. [1 - 5.1.2 Collect Requirements: Tool and Techniques]

High level project requirements and high level description of product should be provided in project charter; so this document is needed for collect requirements process. [1 - 5.1.1 Collect Requirements: Input]

Time, cost, risk, quality, and customer satisfaction may be effected by change in project scope. These areas of project management should be evaluated against change. [1 - 5 Project Scope Management]

Create work breakdown structure needs to be created. [1 - 5.3 Create WBS]

Requirements documentation, traceability matrix, requirements management plan are the deliverables of collect requirements process. [1 - 5.1.3 Collect Requirements: Outputs]

Decomposition is the tool for creating WBS. [1 - 5.3 Create WBS]

Analysis information in project charter [1 - 4.1.3.1] and stakeholder register [1 - 10.1.3.1] is the right answer. [1 - 5.1 Collect Requirements]

Product requirements are more technical and include business specifications of the project deliverable, while project requirements are focused on the way of how to managing project. [1 - 5.1 Collect Requirements]

Deliverables need to be validated during Perform Quality Control Inspection process.

Collect requirements problems need to be sold as soon as arise. Unsolved requirements problems may cause expensive changes or even cancellation of project on its later stages. [1 - 5. Collect Requirements]

Verify scope process should be done at the end of each phase or when acceptance of an intermediate deliverable is required. [1 - 5.4 Verify Scope]

All choices are right, but not limited to the listed here; so, WBS dictionary includes detailed description of the work package. [1 - 5.3.3 Create WBS: Outputs]

Control scope ensures all corrective and preventive actions have been process through perform integrated change control process. [1 - 5.5 Control Scope]

Project scope management includes following processes collect requirements, define scope, create WBS, verify scope, control scope. [1 - 5 Project Scope Management]

Stakeholder register and project charter should include all the require information to start collecting requirements. Other choices may also help; however, the question is about the minimum input to the process of collect requirements. [1 - 5.1.1 Collect Requirements: Input]

The question asks about a situation when all acceptable methods have been used, and only management can resolve a dispute. [1 - 5. Collect Requirements]

Work breakdown structure should be created with active participation of a project team using various communication and group decision making methods, like meeting, focus group, etc.

WBS breaks to requirements to smaller easier manageable pieces. [1 - 5.1 Collect Requirements]

Assumptions, constrains, and risks need to be maintained during define scope process. Newly discovered artifacts need to be added. [1 - 5.2 Define Scope]

The stakeholders requirements must be quantitative and measurable to be referenced in project and product scope and referenced against project deliverables. [1 - 5.1 Collect Requirements]

This is on of the major constrain of project scope - execute the only work described in project scope. In other words no other work but listed in project scope needs to be done. [1 - 5 Project Scope Management]

Focus group of subject matter experts helps to address specific knowledge areas as issues on the project, including but limited to requirements, technical or business, issues, etc. [1 - 5.1.2 Collect Requirements: Tool and Techniques]

Realistically estimated, described in details, delivered quickly, and are ready to be outsourced without additional information should be included in WBS. This means that WBS dictionary has been also developed for each work package. [1 - 5.3 Create WBS]

Interviews, forums, workshops, decision making techniques, surveys, observations, prototypes are used as tools and techniques in collect requirements process. [1 - 5.1 Collect Requirements]

While going through iterations the results of WBS and WBS dictionary can influence the project scope statement as new scope elements can be discovered during this process. [1 - 5 Project Scope Management]

Scope management process measures the scope performance and corrects it when needed. [1 - 5.1 Collect Requirements]

Perform quality control process to validate deliverable against scope means verify scope - that what needs to be done prior meeting with customer to obtain deliverable acceptance. [1 - 5.4 Verify Scope]

Competing requirements need to negotiate back to stakeholders. Project team and project manager need to analyze the influence of competitive requirements, and offer options, like adjust the requirements, change priorities, implement in later releases, initiate a separate project, or drop at all. [1 - 5. Collect Requirements]

All choices are right. [1 - 5.2.3 Define Scope: Outputs]

Control Scope process also integrates with other control processes to managing actual changes. [1 - 5.5 Control Scope]

Work breakdown structure has top-down descending decomposition. [1 - 5.3 Create WBS]

WBS and WBS dictionary, scope baseline, project document update are the output of create work breakdown structure and work breakdown structure dictionary. [1 - 5.3 Create WBS]

Interviewing stakeholders is one of collect requirements techniques that delivers requirements documentation. [1 - 5.1.2 Collect Requirements: Tool and Techniques]

Project Scope Management is a set of processes to ensure that the project includes all and only the required work, for successful completion of the project. [1 - 5 Project Scope Management]

Detailed description of the work to be done is provided in WBS dictionary.

All choices are right; questionnaires and surveys, observations, and prototypes are useful in collecting and finalizing the requirements. [1 - 5.1.2.4 Collect Requirements: Tools and Techniques. Group Creativity Techniques.]

Delhi technique is used with a selected group of experts, who provide their feedback on distributed questionnaires through the rounds until a consensus is reached. The facilitator keeps expert's feedback anonymously. [1 - 5.1.2 Collect Requirements: Tool and Techniques]

Project provided additional result not planned in project scope. [1 - 5 Project Scope Management]

Clarify product requirements and determine project requirements. The received set of requirements is probably related to the product rather than project. So project requirements need to be determined. [1 - 5.1 Collect Requirements]

Inspection is the tool that used for Verify Scope process. [1 - 5.4 Verify Scope]

Change in project scope that does not fit within project charter should be be accepted.

Verify scope is process that formalizes acceptance of the completed project deliverable. [1 - 5.4 Verify Scope]

Only approved change request may allow change in project scope statement. [1 - 5 Project Scope Management]

Project charter, requirements documentation, organizational process assets are the input to the process of defining of project scope. [1 - 5.2 Define Scope]

Collecting requirements is the process of defining and managing customer expectations. [1 - 5.1 Collect Requirements]

Project scope management defines and controls what should be included and what should not in the project. [1 - 5 Project Scope Management]

Work packages estimated on higher level. [1 - 5.3 Create WBS]

Realistically estimated, described in details, delivered quickly, and are ready to be outsourced without additional information should be included in WBS. This means that WBS dictionary has been also developed for each work package. [1 - 5.3 Create WBS]

Project scope contains detailed description of the project and product. [1 - 5.2 Define Scope]

Requirements are the foundation to create WBS and WBS process. [1 - 5.1 Collect Requirements]

Defining and documenting stakeholders requirements that meet project objectives is the right answer. Here the play of words brings different meaning to project manager's work. [1 - 5.1 Collect Requirements]

Develop project management plan and management plan baselines that are realistic is the process of creation project scope management plan, along with other management plans. [1 - 5 Project Scope Management]

Nominal group technique is used to enhanced brainstorming by adding voting process to rank the most useful ideas for further brainstorming or for prioritization of requirements. [1 - 5.1.2.4 Collect Requirements: Tools and Techniques. Group Creativity Techniques.]

All choices are right. Scope baseline is the part of project management plan to be used for verifying what has been done to comply with scope and requirements, while requirements documentation may be needed to verify the details. Traceability matrix will refer to the sources of requirement and relations to other requirements, and cope management plan to confirm the agreed list of deliverables. [1 - 5.4 Verify Scope]

Project scope statement, requirements documentation and organizational process assets is the right answer. [1 - 5.3 Create WBS]

Requirements documentation is one of the outputs of collect project requirements process. [1 - 5.1 Collect Requirements]

Descending hierarchical approach driven by project deliverables drives the work breakdown structure. [1 - 5.3 Create WBS]

Gathering and managing project and product requirements is the right answer. The other selections are not significant keys in the work and can be replaced, while requirements are the base of the project and their quality is the most influential. [1 - 5.1 Collect Requirements]

Project charter is the document that describes projects objectives to be used for balancing the requirements. In other words, the project team must assessing stakeholders' requirements and ensure the demands are in balance with project objectives. Any lack of balancing requirements may increase risks, lead to expensive changes, and unsteadiness of scope, schedule, cost, quality, risk, and customer satisfaction. It is a part of project manager's responsibility to balance stakeholders' interests with specific project objectives. Project manager must to ensure professional cooperation of stakeholders with project team. [1 - 1. Introduction (page 7); 2.3 Stakeholders; 5. Collect Requirements]

Define scope is following after the requirements are finalized and confirmed. [1 - 5.2 Define Scope]

Defining different approaches to execute and perform the project work is the right choice for to achieving effective result. A variety of general methods can be applied, such as focus groups, workshops, brainstorming, pair wise comparison, literal thinking. [1 - 5.2 Define Scope: Tools and Techniques]

Diving the project work and its deliverables to smaller more manageable components. [1 - 5.3 Create WBS]

Proceed through iterations during planning process group and update all project document while new information become available. [1 - 5.2. Define Scope]

Verify scope, control scope are two processes from monitoring and controlling process group that used in scope management process. [1 - 5 Project Scope Management]

Only those deliverables approved for the project take place in WBS. [1 - 5.3 Create WBS]

Project scope elaborates during planning process group. This process may continue through a number of iterations. [1 - 5.2 Define Scope]

Project management plan, requirements documentation, requirements traceability matrix and validated deliverables are inputs to Verify Scope process. [1 - 5.4 Verify Scope]

Project team with sponsor of customer are reviewing completeness of project deliverables and obtaining formal ensuring their satisfactory was reached. [1 - 5.4 Verify Scope]

Numbering items in WBS helps identifying the item and its level of decomposition.

Project management plan and scope baseline are the documents to be present during meeting with customer while discussing acceptance of the deliverable. [1 - 5.4 Verify Scope]

Integrate scope management processes with other knowledge areas. [1 - 5 Project Scope Management]

Verify Scope process is used for verification of deliverable completeness in preparation for acceptance meting or request for acceptance. [1 - 5.4 Verify Scope]

Deliverables are complete using the Direct and Manage Project Execution processes, which are included to all execution, monitoring and controlling, and closing project groups.

Requirements traceability matrix is one of the outputs of collect project requirements process. [1 - 5.1 Collect Requirements]

Requirements must be collected from all stakeholders included but limited to all stakeholders, sponsors, customers, users, management, etc. [1 - 5 Project Scope Management]

Delhi technique is used with a selected group of experts, who provide their feedback on distributed questionnaires through the rounds until a consensus is reached. The facilitator keeps expert's feedback anonymously. [1 - 5.1.2 Collect Requirements: Tool and Techniques]

Analyzing before acting is the rule what any project manger should follow. Fixing a cause of the problem may eliminate new problems and issues. [1 - 5. Collect Requirements]

Change in project scope that does not fit within project charter should be be accepted. [1 - 5 Project Scope Management]

Project manager's authority level is determined in project charter. However, since the project manager is responsible for project success, it should be his or her decision whether accept of reject specific requirements, while negotiation with stakeholders can be a remedy before a decision is made. [1 - 5. Collect Requirements]

Verify Scope eases preparation for acceptance of a deliverable. The output of Verify Scope process are actually accepted deliverables and/or change requests, along with update of project documentation, indicating completion or required change. [1 - 5.4 Verify Scope]

Effective communications is one of the most useful project management knowledge areas while collecting requirements. [1 - 5. Collect Requirements]

All choices are right, the requirements need to be balanced, finalized, and confirmed with all stakeholders. [1 - 5. Collect Requirements]

Collect requirements, define scope, create WBS and WBS dictionary are the planning process used in scope management process. [1 - 5 Project Scope Management]

WBS does not show dependencies. Other choices are not related to the matter of specified here question. [1 - 5.3 Create WBS]

All choices are right. All subject matter documentation, processes, templates and historical information can be valuable while defining project scope. [1 - 5.2.1.3 Define Scope: Input. Organizational Process Assets]

WBS may become a perfect tool in communications with stakeholders while working on the requirements and project scope statement.

If stakeholders requirements are not in balance with project objectives, the project team and project manager need to analyze the influence of the requirements, and offer options, like adjust the requirements, change priorities, implement in later releases, initiate a separate project, or drop. [1 - 5. Collect Requirements]

Requirements documentation needs to be updated when WBS is completed. Other choices are outputs of the processes that come next. [1 - 5.3.3 Create WBS: Outputs]

Project scope statement and project document update are output of define scope process.

All choices are right. For the sake of receiving appropriate professional expert judgement all listed but no limited to sources can help. [1 - 5.2 Define Scope: Tools and Techniques]

Uncontrolled changes some people call Creep. [1 - 5.5 Control Scope]

Project Scope Statement is created planning process group.

Monitoring the project status, its scope and managing changes to the scope baseline. [1 - 5.5 Control Scope]

All the listed but not limited to answers are right. [1 - 5.3 Create WBS]

The level of decomposition should provide enough information that project team could reach project objectives. [1 - 5.3 Create WBS]

Scope baseline includes all project scope statement, work breakdown structure and work breakdown structure dictionary. [1 - 5.3.3 Create WBS: Outputs]

Requirements management plan is one of the outputs of collect project requirements process. [1 - 5.1 Collect Requirements]

Mind mapping is an effective tool for creating a view of consolidated ideas generated through brainstorming. [1 - 5.1.2 Collect Requirements: Tool and Techniques]

WBS helps to identifying influence of change in scope, activities or work packages and entire project. [1 - 5.3 Create WBS]

Work breakdown structure is a graphical presentation of the project activities. [1 - 5.3 Create WBS]

Create WBS, with means divide project work and project deliverables to smaller more manageable components. [1 - 5.3 Create WBS]

Project management plan and scope baseline are the documents to be present during meeting with customer while discussing acceptance of the deliverable. [1 - 5.4 Verify Scope]

The work breakdown is structure is built as top-down sequence from the first line with largest pieces, following by smaller components in each next level. [1 - 5.3 Create WBS]

Verify scope concerns acceptance of the deliverables rather than their correctness and specified quality. Control quality usually performed before verify scope process but in some cases can be done in parallel. [1 - 5.4 Verify Scope]

Verify Scope process produces acceptance of the intermediate deliverables of the project. [1 - 5.4 Verify Scope]

All choices in together provide input into Control Scope process. [1 - 5.5 Control Scope]

Project needs to address both interests of all stakeholders and the project. [1 - 5. Collect Requirements]

Scope management process verifies that the work planned in project scope has been completed. [1 - 5.1 Collect Requirements]

Measuring, examining, and verifying to find if work and deliverables have met the requirements, and other acceptance criteria is done by inspection of project work deliverables while verifying scope. [1 - 5.4 Verify Scope]

Stakeholder register, requirements documentation, and requirements traceability matrix must be updated so other team members and stakeholders would use project scope statement in other planning processes. [1 - 5.2.3 Define Scope: Outputs]

Project manager and project team need to determine the level of details required for documenting requirements, which may be different for different requirements. All answers are right, while reaching the project objective if the primary target.

Description of major project deliverables, assumptions, and constrains that are documented during project initiation. [1 - 5.2 Define Scope]

All choices but not limited to the listed are right depending on application area and type of deliverable, whether a product, process, service or other. [1 - 5.2 Define Scope: Tools and Techniques]

All choices are actually right, while they are summarized as assumptions and constrains. [1 - 5.2 Define Scope]

Affinity diagram helps to group already collected requirements by similarity and document new ones. This technique also simplifies identifying additional scope or risks. [1 - 5.1.2 Collect Requirements: Tool and Techniques]