PMI Updated CAPM Exam Questions and Answers by kendrick

According to the PMBOK® Guide, Enterprise Environmental Factors (EEFs) refer to conditions, not under the control of the project team, that influence, constrain, or direct the project. These can be internal or external to the organization.

The PMI standards classify Infrastructure as a primary Internal EEF. Internal EEFs arise from the organization itself and include:

Infrastructure: This includes existing facilities, equipment, organizational telecommunications channels, information technology hardware, availability, and capacity. For example, the quality of a company ' s server network directly impacts a software project ' s development speed.

Organizational Culture, Structure, and Governance: Vision, mission, values, beliefs, cultural norms, and hierarchy.

Geographic Distribution of Facilities and Resources: Factory locations, virtual teams, and shared systems.

Resource Availability: Physical and team resource constraints.

Employee Capability: Existing human resources ' expertise, skills, and specialized knowledge.

Analysis of other options:

Cultural influences (Option A): While culture is an EEF, the PMBOK® Guide specifically lists " Organizational Culture " as the internal factor. " Cultural influences " is often used in a broader context that can imply external societal cultures, making " Infrastructure " a more definitive internal technical EEF in PMI terminology.

Physical environmental elements (Option B): These are considered External EEFs. They include working conditions, weather, and constraints imposed by the physical geography of the project location.

Commercial databases (Option C): These are considered External EEFs. They include benchmarking results, standardized cost estimating data, and industry risk study information provided by third parties.

Per PMI standards, understanding the internal Infrastructure is vital during the planning phase to ensure the project management plan is realistic regarding the tools and facilities available to the team.

In alignment with the PMBOK® Guide and PMI’s standards for Quality Management, a Flowchart (also referred to as process mapping) is the primary graphical tool used to display the sequence of steps and the branching possibilities that exist within a process.

Definition: A flowchart shows the activities, decision points, branching loops, parallel paths, and the overall order of processing by mapping an operational procedure from start to finish.

Application in Project Management:

Plan Quality Management: Used to identify where quality issues might occur or where to incorporate quality checks.

Manage Quality: Helps the team understand and estimate the " Cost of Quality " for a process by analyzing the steps involved.

Process Improvement: Provides a baseline to identify bottlenecks or redundant steps that do not add value to the project.

Comparison with Other Options:

Control Charts (A): Used to determine if a process is stable or has predictable performance over time.

Bar Charts (B): (e.g., Gantt charts) are primarily used for scheduling and showing the duration of activities.

Pareto Diagrams (D): Histograms used to identify the " vital few " sources of problems (the 80/20 rule).

According to the PMBOK® Guide, specifically within the Project Cost Management knowledge area, Funding Limit Reconciliation is a key tool and technique of the Determine Budget process.

Definition: Funding limit reconciliation is the process of comparing the planned expenditure of project funds against any limits on the commitment of funds for the project.

The Constraint: Organizations often have limits on the disbursement of funds at specific intervals (e.g., quarterly or annually). This can create a " funding gap " if the project ' s planned expenditures exceed the available cash flow at a given time.

The Reconciling Action: If a variance is found between the funding limits and the planned expenditures, the project manager may need to reschedule work to level out the rate of expenditures. This is often achieved by placing imposed date constraints for work packages or milestones into the project schedule to ensure the spend remains within the authorized funding limits.

Comparison with other options:

A. Estimate Costs: This process focuses on developing an approximation of the monetary resources needed to complete project activities. Its tools include Analogous, Parametric, and Bottom-up estimating.

B. Control Costs: This process monitors the status of the project to update costs and manage changes to the cost baseline. Its primary tools include Earned Value Analysis (EVA) and To-Complete Performance Index (TCPI).

C. Plan Cost Management: This is the initial planning process that establishes the policies and procedures for managing costs. It primarily uses Expert Judgment, Data Analysis, and Meetings.

According to the PMBOK® Guide and the Agile Practice Guide, project life cycles are defined by how they handle requirements, activities, and the delivery of the product.

Iterative Life Cycle (Choice C): In an iterative life cycle, the project scope is generally determined early, but time and cost estimates are routinely modified as the project team’s understanding of the product increases. The deliverable is developed through a series of repeated cycles (iterations) that successively add functionality or refine the product. Crucially, the full deliverable is only completed and considered finished after the final iteration. Each iteration improves the quality or detail of the single deliverable until it meets the final requirements.

Incremental Life Cycle (Choice A): Unlike iterative, an incremental life cycle delivers a functional portion of the product at the end of each iteration. The deliverable is produced through a series of iterations that each add a complete, usable " increment " to the previous ones.

Predictive Life Cycle (Choice B): Also known as " Waterfall, " this life cycle is characterized by a linear approach where the scope, time, and cost are determined in the early phases of the life cycle. It does not typically use a series of iterations to produce the deliverable.

Adaptive Life Cycle (Choice D): This is a combination of iterative and incremental (Agile). It uses iterations to refine the product but also delivers functional increments frequently (usually every 2-4 weeks).

The key distinction for an Iterative approach is that the goal is the correctness of the solution through refinement of a single deliverable, whereas an Incremental approach focuses on speed of delivery by providing small, working pieces of the deliverable over time.