[2026年09月05日] 最新版を今すぐ試そうCAPM日本語練習テスト問題解答 [Q163-Q179]

According to the PMBOKGuide (6th Edition), a Project Management Office (PMO) is an organizational structure that standardizes the project-related governance processes and facilitates the sharing of resources, methodologies, tools, and techniques.
The responsibilities of a PMO can range from providing project management support functions to actually being responsible for the direct management of one or more projects. There are three primary types of PMO structures:
* Supportive: Provide a consultative role to projects by supplying templates, best practices, training, and access to information and lessons learned from other projects. This type of PMO serves as a project repository and has a low level of control.
* Controlling: Provide support and require compliance through various means. Compliance may involve adopting project management frameworks or methodologies, using specific templates, forms, and tools, or conformance to governance. This type of PMO has a moderate level of control.
* Directive: Take control of the projects by directly managing the projects. Project managers are assigned by and report to the PMO. This type of PMO has a high level of control.
Analysis of Distractors:
* A (Project Management Information System – PMIS): This refers to the tools and techniques used to gather, integrate, and disseminate the outputs of project management processes. It is a set of software
/automated tools (like scheduling software or a document repository), not an organizational structure.
* B (Project Management System): This is the aggregation of the processes, tools, techniques, methodologies, and resources used to manage a project. It is the ” how-to ” framework rather than the ” who ” (the organizational entity).
* D (Project Management Knowledge Area): This is a technical term for a group of processes related to a specific topic in project management (e.g., Scope, Cost, Risk). It is a classification of knowledge, not a structural body within a company.

According to the PMBOKGuide, the Plan Stakeholder Engagement process is the process of developing approaches to involve project stakeholders based on their needs, expectations, interests, and potential impact on the project. To identify the correct set of an Input, a Technique, and an Output (ITO), we look at the standard process framework:
* Input: Project Management Plan: Specifically, the resource management plan, communications management plan, and risk management plan are vital inputs that provide the context for how stakeholders should be engaged.
* Technique: Data Gathering: Techniques such as benchmarking are used to gather information. Other techniques in this process include Data Analysis (stakeholder analysis), Data Representation (stakeholder engagement assessment matrix), and Meetings.
* Output: Stakeholder Engagement Plan: This is the primary output of the process. It identifies the management strategies and actions necessary to effectively engage stakeholders in project decision- making and execution.
Why other options are incorrect:
* Option B: Business documents and Meetings are valid inputs/techniques, but the Stakeholder Register is an input to this process (created during Identify Stakeholders), not an output.
* Option C: While all three are part of the process (OPA is an input, Data Gathering a technique, and Project Document Updates an output), Option A is the more ” complete ” representation as it includes the Stakeholder Engagement Plan, which is the definitive key output of the process.
* Option D: Change requests are typically an output of the monitoring and controlling phase (Monitor Stakeholder Engagement), not the initial planning phase. In the planning phase, the primary goal is the creation of the plan itself.

According to the PMBOKGuide, 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 PMBOKGuide 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.

According to the PMBOKGuide, the Plan Stakeholder Engagement process (referred to as Plan Stakeholder Management in earlier editions) is the process of developing approaches to involve project stakeholders based on their needs, expectations, interests, and potential impact on the project.
* Stakeholder Register: This is a critical Project Document and a primary input to this process. It provides the list of all identified stakeholders along with their classification, interests, and influence levels. You cannot plan how to manage or engage stakeholders without first having the list of who they are and what their requirements are, which is exactly what the register provides.
* Logical Flow: The process of Identify Stakeholders produces the Stakeholder Register as an output.
That register then flows directly into Plan Stakeholder Engagement as an input so that the project manager can create a tailored engagement strategy.
Why the other options are incorrect:
* A. The project charter: While the project charter is an input to the Identify Stakeholders process (because it lists high-level stakeholders and sponsors), it is typically not the primary input for the detailed Planning of stakeholder engagement. The register is more specific and refined.
* B. The stakeholder analysis: This is a Tool and Technique used within the processes (both Identify Stakeholders and Plan Stakeholder Engagement) to gather and evaluate information. It is the action of analyzing, not a standalone input document.
* C. A communication management plan: This is usually an output developed alongside or after the stakeholder engagement plan. While the two are closely linked, the Stakeholder Engagement Plan defines the ” why ” and ” who ” of engagement, while the Communications Management Plan defines the ” how, ” ” when, ” and ” what. “

According to the PMBOKGuide (Project Management Body of Knowledge), specifically within the Project Integration Management knowledge area and the Develop Project Charter process:
* Project Charter (Option C): This is the document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. Per PMI standards, a standard Project Charter includes high-level information such as the project purpose or justification, measurable project objectives, success criteria, a summary milestone schedule, and a summary budget. It also identifies the high-level risks and the assigned project manager.
* Work Breakdown Structure (WBS) (Option A): This is a hierarchical decomposition of the total scope of work. It focuses on deliverables and work packages, not on project justification, budgets, or milestone schedules.
* Requirements Document (Option B): This document describes how individual requirements meet the business need for the project. While it includes measurable criteria for the product, it does not contain the project ‘ s financial authorization or the milestone schedule.
* Project Management Plan (Option D): This is a comprehensive document that describes how the project will be executed, monitored, and controlled. While it incorporates high-level information from the charter, the charter is the specific, formal starting document where these summary-level components are first established and authorized.
In the PMI framework, the Project Charter serves as a bridge between the organization ‘ s strategic objectives and the project ‘ s tactical execution. By documenting the summary budget and milestone schedule at this early stage, the sponsor set the boundaries within which the Project Manager must plan the detailed project activities.

Dynamic Systems Development Method (DSDM) is an Agile framework that operates on the principle that ” nothing is built perfectly the first time ” and focuses on frequent delivery of business value. In DSDM, time and cost are fixed, while the scope is variable.
* Why Choice D is correct: In DSDM, work is organized into Timeboxes (similar to Sprints in Scrum).
One of the core principles of DSDM is ” Never Compromise Quality. ” When a new high-priority feature arrives, the practitioner follows the formal change process within the Agile framework:
* MoSCoW Prioritization: New requirements are added to the prioritized requirements list (Backlog) and categorized using MoSCoW (Must have, Should have, Could have, Won ‘ t have this time).
* Timeboxing: DSDM does not allow for ” mid-timebox ” disruptions that compromise the current commitments. Instead, the new feature is evaluated and prioritized for the next work period (Timebox). This maintains the team ‘ s focus and ensures that the current timebox ‘ s ” Must Haves ” are delivered as promised.
* Analysis of other options:
* A (Parallel work package): This creates multitasking and resource contention, which DSDM aims to avoid. It compromises the focus of the current timebox.
* B (Shorten the current period): Timeboxes in DSDM are fixed. Shortening them disrupts the cadence and usually results in incomplete or low-quality deliverables for the current cycle.
* C (Complete it immediately): This is ” reactive ” management. It bypasses the prioritization process and ignores the impact on existing work. In DSDM, the Business Visionary or Business Ambassador must first agree on the priority relative to other items.
Key Concept: DSDM relies on Empowered Teams and Iterative Development. By placing the request in the requirements list for the next period (Choice D), the practitioner respects the DSDM philosophy of ” fixing ” the time and quality while allowing the scope to be re-prioritized based on evolving business needs.

According to the PMBOKGuide (Project Management Body of Knowledge) and the PMI Lexicon of Project Management Terms, it is crucial to distinguish between ” Appetite ” and ” Tolerance, ” as they are often confused in practice:
* Risk Tolerance: This is specifically defined as the specified range of acceptable results or the degree, amount, or volume of risk that an organization or individual is willing to withstand. It represents a measurable threshold. For example, a project might have a budget tolerance of plus or minus 10%. If the risk threatens to exceed that 10%, it is beyond the organization ‘ s tolerance.
* Risk Appetite (Option B): This is the degree of uncertainty an organization or individual is willing to accept in anticipation of a reward. It is a more general, high-level guiding principle or ” hunger ” for risk rather than a specific measurable volume of withstandable risk.
* Risk Analysis (Option A): This is the process of examining identified risks to estimate the probability and impact. It is a step in the Risk Management process, not a measurement of the capacity to withstand risk.
* Risk Response (Option D): This refers to the specific actions or strategies (such as Avoid, Transfer, Mitigate, or Accept) taken to address risks once they have been analyzed.
In the context of the Standard for Risk Management in Portfolios, Programs, and Projects, ” Tolerance ” acts as the measurable boundary for ” Appetite. ” Because the question specifically asks for the ” degree, amount, or volume ” that can be withstood, Tolerance is the most precise and verified term.

According to the PMBOKGuide (Project Management Body of Knowledge), specifically the section on The Planning Process Group, the nature of project planning is iterative and ongoing; however, it must have a defined boundary for the transition to execution.
* Ends (Option A): The PMBOKGuide states that while the Planning Process Group involves developing the project management plan and project documents used to carry out the project, the organizational procedures (specifically the project life cycle defined by the organization) dictate when the project planning ends. This is typically marked by a ” Phase Gate, ” ” Kill Point, ” or a formal ” Management Review ” where the plan is baselined and authorization is given to move into the Executing Process Group.
* Begins (Option B): Project planning begins after the project has been formally authorized in the Initiating Process Group (e.g., after the Project Charter is signed). While organizational procedures influence this, the primary driver for ” beginning ” is the output of the Initiating processes.
* Delays (Option C) and Deviates (Option D): These are conditions that occur during the Monitoring and Controlling Process Group. While organizational procedures might dictate how to handle a delay or a deviation (via Change Control), they do not ” dictate ” when these negative occurrences happen.
In the PMI framework, the concept of Progressive Elaboration means that planning is never truly ” finished ” until the project is over. However, for the purpose of governance and control, organizational procedures establish the formal cutoff point where the initial planning phase ends and the execution of the baselined plan starts.

According to the PMBOKGuide, Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
* Prototypes: This is a specific tool and technique used to obtain early feedback on requirements by providing a working model of the expected product before actually building it. It supports the concept of progressive elaboration because it allows stakeholders to ” test drive ” an idea, which helps them identify requirements they might not have thought of otherwise.
* Benefits of Prototyping: It reduces the risk of scope creep and rework by uncovering misunderstandings early in the project life cycle. Common forms include small-scale models, 2D and 3D mock-ups, and interactive digital wireframes.
* Other Tools in this Process: Other standard techniques include interviews, focus groups, facilitated workshops, group creativity techniques (like brainstorming or Delphi), and observations.
Analysis of Other Options:
* B. expert judgment: While expert judgment is a common tool across almost all project management processes, it is technically listed as a tool for Plan Scope Management, not specifically as a primary tool for the Collect Requirements process in standard PMI process charts (though experts are often consulted within techniques like interviews).
* C. alternatives identification: This is a tool and technique used in the Define Scope process. It is used to generate different approaches to execute and perform the work of the project.
* D. product analysis: This is also a tool and technique for the Define Scope process. It involves translating high-level product descriptions into tangible deliverables (e.g., value engineering or systems engineering).

According to the PMBOKGuide, specifically within the Develop Team process (part of Project Resource Management), the primary goal is to improve interpersonal skills, technical competencies, and the overall team environment to enhance project performance.
* Objectives of Develop Team: The process focuses on creating a high-performance culture. Key objectives include:
* Improving knowledge and skills of team members to increase their ability to complete project deliverables.
* Improving feelings of trust and agreement among team members to raise morale, lower conflict, and increase teamwork.
* Creating a dynamic, cohesive, and collaborative team culture to (1) improve individual and team productivity, (2) encourage cross-training and mentoring, and (3) build a sense of shared responsibility.
* Team Building: This is a key tool and technique. It consists of activities that help internal and external stakeholders work together. Building trust and cohesiveness is a direct outcome of effective team- building activities and recognized as a core objective of the process.
* Success Indicators: When this process is successful, the team experiences decreased turnover, improved communication, and a ” synergy ” where the collective output of the team is greater than the sum of individual efforts.
Comparison with other options:
* B. Ground rules for interaction: Ground rules are a tool and technique (specifically part of the Team Charter) used to achieve team development, but they are not the ultimate objective of the process itself.
* C. Enhanced resource availability: This is generally a concern of the Acquire Resources process.
Developing the team focuses on the quality and interaction of the resources you already have, not increasing the quantity or availability of new ones.
* D. Functional managers becoming more involved: While functional managers may be involved in resource discussions, their increased involvement is not a stated objective of Developing the Project Team. In fact, in a strong matrix or project-oriented organization, the goal is often for the Project Manager to have more influence over the team ‘ s development.