Business Environment practice questions

Answer: A) A program

• AA program is a group of related projects (and sometimes operations) coordinated to realize benefits not achievable by managing them individually.
• BA portfolio is a collection of projects, programs, and operations grouped to meet strategic objectives — not necessarily related to each other.
• CA phase is a stage within a single project's lifecycle.
• DA work package is the lowest level of a single project's WBS.

Answer: A) Use the PMO's standards and support as organizational process assets and governance, tailoring their application to the project's needs

• AA supportive/controlling PMO provides methodology, tooling, and oversight; the PM leverages these assets and adapts them appropriately rather than reinventing or resisting them.
• BDismissing governance creates inconsistency and audit/compliance risk; concerns about overhead should be raised, not unilaterally overridden.
• COver-delegating routine decisions defeats the PM role; the PMO sets standards, the PM runs the project.
• DThe PMO supports and governs; delivery accountability stays with the project manager.

Answer: A) The decision log, which records each decision with its rationale, the alternatives considered, the approver and the date

A decision log keeps the rationale, alternatives, approver and date for key decisions. That makes it the audit trail for explaining past choices, which change logs, issue logs and status reports are not designed to provide.

• ACorrect. A decision log is designed to keep a traceable record of what was decided, why, by whom and when. That gives auditors the audit trail of key decision points that governance requires.
• BIncorrect. The change log tracks requested changes to approved baselines. These were original planning decisions, not changes to a baseline, so their rationale would not be recorded there.
• CIncorrect. The issue log tracks problems and how they were resolved. It is not built to capture the alternatives and rationale behind planning decisions such as rollout strategy or platform selection.
• DIncorrect. Status reports describe performance over time. They might mention that a decision was made, but they do not reliably record the alternatives considered, the rationale or the approver.

Answer: A) To give decision makers the economic justification needed to decide whether the investment is worthwhile

A business case gives the economic justification decision makers use to decide whether to fund a project. Authorization, benefits ownership and measurement, and detailed scope belong to the charter, the benefits management plan, and the scope statement.

• ACorrect. A business case sets out the business need and the justification for spending resources, so decision makers can approve or reject the investment. Later it serves as a baseline for comparing planned benefits with actual ones.
• BIncorrect. Formal authorization and the project manager's authority come from the project charter. The charter may draw on the business case, but the business case justifies the investment rather than authorizing the project.
• CIncorrect. Benefit ownership, measurement, and sustainment are defined in the benefits management plan, which builds on the business case.
• DIncorrect. Detailed scope, deliverables, and acceptance criteria are set out during planning in the project scope statement. The business case comes earlier and stays at the level of business justification.

Answer: A) Inform the sponsor and request a reassessment of the business case

When a key business case assumption no longer holds, the project manager should take it to the sponsor so the business case can be reassessed through governance. Logging it as a risk, changing scope or crashing the schedule all skip that check.

• AA key assumption behind the project's justification has turned out to be false. The business case should be reviewed so the sponsor and governance can decide whether to continue, change direction or stop the project.
• BThe competitor's launch has already happened, so it is not an uncertain future event. Logging it as a risk and carrying on with the plan does not deal with the fact that the project's justification may no longer hold.
• CProposing scope changes jumps to a solution before anyone has confirmed the project is still worth doing. The business case needs to be reviewed before deciding what to change.
• DCrashing adds cost and assumes the current product is still worth delivering. That decision belongs to the sponsor after the business case has been reassessed, not to the project manager acting alone.

Answer: A) Document each obligation as a requirement and trace it in the requirements traceability matrix through to verification

Regulatory obligations should be treated as requirements and traced from their source through deliverables to verification, usually with a requirements traceability matrix. This keeps any of them from being missed and provides evidence of compliance.

• ATreating each regulatory obligation as a requirement puts it into scope. Tracing it from source to deliverable to verification makes gaps visible and gives evidence of compliance for auditors and regulators.
• BNon-compliance can create risks, but a mandatory regulation is a certain obligation, not an uncertain event. Listing it only as a risk does not make it part of scope or show that it was verified.
• CThe assumption log records conditions believed to be true and constraints. It does not tie each obligation to a deliverable or record how compliance was verified.
• DThe issue log tracks current problems that need to be resolved. Regulatory obligations are requirements to be designed in and verified, not issues waiting to be resolved.

Answer: A) Build the regulatory requirements into acceptance criteria and verify them at each iteration review or phase gate

Compliance is best measured during delivery by turning regulatory requirements into acceptance criteria and verifying them at regular reviews or gates. Self-attestation, risk-register tracking, and occasional spot checks do not verify deliverables objectively.

• ACorrect. Turning regulatory requirements into acceptance criteria gives an objective test for every deliverable. Checking them at each review or gate measures compliance repeatedly during delivery, so gaps are found while they are still cheap to fix.
• BIncorrect. Training is useful, but verbal self-attestation is not objective verification of deliverables. Non-compliant work can still pass unnoticed.
• CIncorrect. Regulations are mandatory requirements, not uncertain events. Reviewing risk entries does not check whether the deliverables actually meet the requirements.
• DIncorrect. Ad hoc spot checks happen during execution, but they are neither systematic nor repeatable. Coverage depends on someone else's availability, so gaps can be missed.

Answer: A) Supportive

• ASupportive PMOs provide resources and guidance with low control.
• BControlling PMOs require compliance with frameworks.
• CDirective PMOs directly manage projects.
• DThat isn't a standard PMO type.

Answer: B) Work with the sponsor to update the business case and reassess whether the expected benefits still justify continued investment

When a key business case assumption turns out to be wrong, the project manager should work with the sponsor to update the business case and reassess whether the project is still viable. Simply continuing, or making scope changes on their own, is not appropriate.

• ABeing on schedule and on budget does not mean the project still makes business sense. The assumption behind the expected benefits has failed, so it needs action now, not just a lessons-learned entry.
• BThe business case is a living document. It should be revised when key assumptions change so the sponsor and governance can decide whether to continue, change direction, or stop the project.
• CThis jumps to a fix before anyone has reassessed whether the project is still viable. Whether to continue, rescope, or stop is a sponsor/governance decision made after the business case is updated.
• DThe assumption has already turned out to be wrong, so it is no longer an uncertain risk. Waiting until after closure means investment decisions keep resting on outdated information.

Answer: A) Work with compliance experts to analyze the impact on scope, schedule, cost, and risk, then submit a change request

When an external regulation changes mid-project, the project manager should analyze its impact, with subject matter experts where needed, and handle the required updates through integrated change control. Acting before approval, escalating without analysis, and waiting passively are all wrong.

• AA new regulation is an external business-environment change. The project manager should assess its impact, using compliance or legal experts, and send any needed changes through integrated change control so they are reviewed, approved, and communicated together with the rest of the plan.
• BCompliance can't be ignored, but changing a deliverable before the change is analyzed and approved bypasses integrated change control. It can create unassessed effects on cost, schedule, and other deliverables.
• CThe sponsor may need to be involved, but escalating with no impact information gives them nothing to decide on. The project manager should first find out how the regulation affects the project.
• DThe regulation is already in effect, so it is a current requirement, not an uncertain future event. Waiting passively delays the analysis the project manager is responsible for starting.