QUESTIONS AND
ANSWERS GRADED A+
2025-2026
[General PM] Nature of Project - ANS-Temporary, creative unique outputs, and drive
changes
[General PM] Project Charter - ANS-Authorizes the PM, sets stakeholder expectations,
and prevents constant changes
[General PM] Charter signatory - ANS-Signed by the sponsor or senior management
with funding authority
[General PM] Project management plan - ANS-Includes plans and baselines
[General PM] Planning lifecycles - ANS-Plan for the project lifecycle (phases) and
development lifecycle (e.g., waterfall, agile)
[General PM] Project phases - ANS-(each phase starts with the initiating process,
including reviewing and updating the project charter); initiating - planning - executing -
controlling - closing
[General PM] Multiple sponsors - ANS-increases communication needs and time in
Configuration Management due to competing needs
,[General PM] Management strategy - ANS-A carefully developed overall approach to
leading an organization; if the team needs constant pushing to get things done, there
is no strategy
[General PM] Reporting structure - ANS-Different reporting lines in various
organizational structures (e.g., matrix, functional, projectized)
[General PM] Type of PMO: Controlling - ANS-Mandates compliance
[General PM] Type of PMO: Supportive - ANS-Provides templates and best practices
[General PM] Type of PMO: Directive - ANS-High degree of oversight
[Scope Management] Scope baseline - ANS-Developed by project team with stakeholder
input
[Scope Management] Precise scope statement - ANS-Must be detailed and accurate
[Scope Management] Constraints - ANS-Listed in the scope statement, assumptions log,
or constraints log
[Scope Management] Scope reviews - ANS-Preliminary and final reviews
[Scope Management] Customer approval - ANS-Approved product scope, not project
scope
[Scope Management] Quality control vs scope validation - ANS-Quality control for
correctness, validate scope for acceptance
[Scope Management] Scope changes - ANS-Explained to the customer for informed
decisions
, [Scope Management] WBS Development - ANS-Work Breakdown Structure - created by
the team, used for stakeholder communication
[Scope Management] WBS benefits - ANS-Ensures team buy-in, prevents scope issues,
key tool to manage scope
[Scope Management] Context diagram - ANS-Visual tool for collecting requirements
[Scope Management] Code of accounts - ANS-Unique WBS IDs
[Scope Management] Control Accounts - ANS-Higher-level than planning and work
packages, defined in scheduling
[Scope Management] Estimating cost issues - ANS-Due to lack of scope definition
[Scope Management] Validate scope - ANS-Done in monitoring and controlling phase
(technical acceptance)
[Scope Management] Scope statement parts - ANS-Description, deliverables,
assumptions/constraints, acceptance criteria, exclusions
[Schedule Management] Estimate activity durations - ANS-Use WBS and RBS at detailed
levels
[Schedule Management] Activity attributes - ANS-include task details (who, where,
predecessor/successor links, duration, float) but not costs
[Schedule Management] Milestones - ANS-Set in a project charter and defined during
activity planning; have zero duration
[Schedule Management] Precedence diagramming method (PDM) - ANS-Maps out tasks
in order for execution