Section: Volume E

Section: Volume E
Explanation:
4.1.1.1 Project Statement of Work Page 67
The project statement of work (SOW) is a narrative description of products, services, or results to be delivered by a project. For internal projects, the project initiator or sponsor provides the statement of work based on business needs, product, or service requirements. For external projects, the statement of work can be received from the customer as part of a bid document, (e.g., a request for proposal, request for information, or request for bid) or as part of a contract. The SOW references the following:
Business need. An organization’s business need may be based on a market demand, technological

advance, legal requirement, government regulation, or environmental consideration. Typically, the business need and the cost-benefit analysis are contained in the business case to justify the project.
Product scope description. The product scope description documents the characteristics of the product,

service, or results that the project will be undertaken to create. The description should also document the relationship between the products, services, or results being created and the business need that the project will address.
Strategic plan. The strategic plan documents the organization’s strategic vision, goals, and objectives and

may contain a high-level mission statement. All projects should be aligned with their organization’s strategic plan. Strategic plan alignment ensures that each project contributes to the overall objectives of the organization.

Explanation/Reference:
Explanation:
6.3.2.2 Dependency Determination
Dependencies may be characterized by the following attributes: mandatory or discretionary, internal or external, as described below. Dependency has four attributes, but two can be applicable at the same time in following ways: mandatory external dependencies, mandatory internal dependencies, discretionary external dependencies, or discretionary internal dependencies.
Mandatory dependencies. Mandatory dependencies are those that are legally or contractually required

or inherent in the nature of the work. Mandatory dependencies often involve physical limitations, such as on a construction project, where it is impossible to erect the superstructure until after the foundation has been built, or on an electronics project, where a prototype has to be built before it can be tested.
Mandatory dependencies are also sometimes referred to as hard logic or hard dependencies. Technical dependencies may not be mandatory. The project team determines which dependencies are mandatory during the process of sequencing the activities. Mandatory dependencies should not be confused with assigning schedule constraints in the scheduling tool.
Discretionary dependencies. Discretionary dependencies are sometimes referred to as preferred logic,

preferential logic, or soft logic. Discretionary dependencies are established based on knowledge of best practices within a particular application area or some unusual aspect of the project where a specific sequence is desired, even though there may be other acceptable sequences. Discretionary dependencies should be fully documented since they can create arbitrary total float values and can limit later scheduling options. When fast tracking techniques are employed, these discretionary dependencies should be reviewed and considered for modifcation or removal. The project team determines which dependencies are discretionary during the process of sequencing the activities.
External dependencies. External dependencies involve a relationship between project activities and

non-project activities. These dependencies are usually outside the project team’s control. For example, the testing activity in a software project may be dependent on the delivery of hardware from an external source, or governmental environmental hearings may need to be held before site preparation can begin on a construction project. The project management team determines which dependencies are external during the process of sequencing the activities.
Internal dependencies. Internal dependencies involve a precedence relationship between project

activities and are generally inside the project team’s control. For example, if the team cannot test a machine until they assemble it, this is an internal mandatory dependency. The project management team determines which dependencies are internal during the process of sequencing the activities.
Process: 6.3 Sequence Activities
Definition: The process of identifying and documenting relationships among the project activities.
Key Benefit: The key benefit of this process is that it defines the logical sequence of work to obtain the greatest efficiency given all project constraints.
Inputs
1. Schedule management plan
2. Activity list
3. Activity attributes
4. Milestone list
5. Project scope statement
6. Enterprise environmental factors
7. Organizational process assets
Tools & Techniques
1. Precedence diagramming method (PDM)
2. Dependency determination
3. Leads and lags
Outputs
1. Project schedule network diagrams
2. Project documents updates

Explanation/Reference:
Explanation:
7. Project Cost Management
7.1 Plan Cost Management
7.2 Estimate Costs
7.3 Determine Budget
7.4 Control Costs

Explanation/Reference:
Explanation:
Monitoring and Controlling Process Group
4.4 Monitor and Control Project Work
4.5 Perform Integrated Change Control
5.5 Validate Scope
5.6 Control Scope
6.7 Control Schedule
7.4 Control Costs
8.3 Control Quality
10.3 Control Communications
11.6 Control Risks
12.3 Control Procurements
13.4 Control Stakeholder Engagement

Section: Volume C
Explanation:
Process: 11.3 Perform Qualitative Risk Analysis
Definition: The process of prioritizing risks for further analysis or action by assessing and combining their probability of occurrence and impact.
Key Benefit: The key benefit of this process is that it enables project managers to reduce the level of uncertainty and to focus on high-priority risks.
Inputs
1. Risk management plan
2. Scope baseline
3. Risk register
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Risk probability and impact assessment
2. Probability and impact matrix
3. Risk data quality assessment
4. Risk categorization
5. Risk urgency assessment
6. Expert judgment
Outputs
1. Project documents updates

Section: Volume D
Explanation:
There are five general techniques for resolving conflict. As each one has its place and use, these are not given in any particular order:
Withdraw/Avoid. Retreating from an actual or potential conflict situation; postponing the issue to be better

prepared or to be resolved by others.
Smooth/Accommodate. Emphasizing areas of agreement rather than areas of difference; conceding one’s

position to the needs of others to maintain harmony and relationships.
Compromise/Reconcile. Searching for solutions that bring some degree of satisfaction to all parties in order

to temporarily or partially resolve the conflict.
Force/Direct. Pushing one’s viewpoint at the expense of others; offering only win-lose solutions, usually

enforced through a power position to resolve an emergency.
Collaborate/Problem Solve. Incorporating multiple viewpoints and insights from differing perspectives;

requires a cooperative attitude and open dialogue that typically leads to consensus and commitment.

Section: Volume E
Explanation
Explanation/Reference: https://www.memrise.com/course/352178/pmbok-5-project-management-exam-study/27/

Section: Volume B

Section: Volume C

Explanation/Reference:
Reference: http://www.free-management-ebooks.com/faqpm/scope-06.htm

Section: Volume E
Explanation/Reference: https://www.theprojectgroup.com/blog/en/why-a-pmo-is-important/