Explanation/Reference:
Explanation:
Process: 5.1 Plan Scope Management
Definition: The process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled.
Key Benefit: The key benefit of this process is that it provides guidance and direction on how scope will be managed throughout the project.
Inputs
1. Project management plan
2. Project charter
3. Enterprise environmental factors
4. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Meetings
Outputs
1. Scope management plan
2. Requirements management plan

Explanation/Reference:
Explanation:
9.2.2.4 Virtual Teams
The use of virtual teams creates new possibilities when acquiring project team members. Virtual teams can be defined as groups of people with a shared goal who fulfill their roles with little or no time spent meeting face to face. The availability of communication technology such as e-mail, audio conferencing, social media, web-based meetings and video conferencing has made virtual teams feasible. The virtual team model makes it possible to:
Form teams of people from the same organization who live in widespread geographic areas;

Add special expertise to a project team even though the expert is not in the same geographic area;

Incorporate employees who work from home offices;

Form teams of people who work different shifts, hours, or days;

Include people with mobility limitations or disabilities; and

Move forward with projects that would have been ignored due to travel expenses.

There are some disadvantages related to virtual teams, such as possibility for misunderstandings, feeling of isolation, difficulties in sharing knowledge and experience between team members, and cost of appropriate technology. Communication planning becomes increasingly important in a virtual team environment. Additional time may be needed to set clear expectations, facilitate communications, develop protocols for resolving conflict, include people in decision making, understand cultural differences, and share credit in successes.

Section: Volume E
Explanation:
12.1.3.2 Procurement Statement of Work
The statement of work (SOW) for each procurement is developed from the project scope baseline and defines only that portion of the project scope that is to be included within the related contract. The procurement SOW describes the procurement item in sufficient detail to allow prospective sellers to determine if they are capable of providing the products, services, or results. Sufficient detail can vary based on the nature of the item, the needs of the buyer, or the expected contract form. Information included in a SOW can include specifications, quantity desired, quality levels, performance data, period of performance, work location, and other requirements.
The procurement SOW is written to be clear, complete, and concise. It includes a description of any collateral services required, such as performance reporting or post-project operational support for the procured item. In some application areas, there are specific content and format requirements for a procurement SOW. Each individual procurement item requires a SOW; however, multiple products or services can be grouped as one procurement item within a single SOW.
The procurement SOW can be revised and refined as required as it moves through the procurement process until incorporated into a signed agreement.