AgilePM Foundation Online Practice Questions

Explanation:
In Agile Project Management, product development is primarily concerned with the evolving solution/product―its outcomes, user value, and the means to achieve those outcomes through iterative delivery. Guidance emphasizes shaping features, quality attributes, and acceptance criteria so each increment is fit for purpose. While product work certainly happens in timeboxes, the explicit stewardship of time-based drivers (milestones, budgets, governance checkpoints, wider stakeholder scheduling) sits mainly in project management. AgilePM distinguishes the project context (business case, governance, roadmap, release planning) from the product-focused work (defining and building valuable increments). Hence statement 2 accurately reflects the heart of product development: “focus on what the product is… and how to achieve that.” Statement 1 maps more closely to project-level planning and coordination responsibilities that ensure the environment, cadence, and constraints enable delivery. Agile practice uses timeboxing and MoSCoW prioritization to protect time/cost/quality, but these mechanisms belong to project/delivery management rather than defining the essence of product development. Therefore, only statement 2 is true.

Explanation:
Statement 1: Correct. Rich communication channels, such as face-to-face conversations or video calls, are necessary for active engagement as they allow for two-way interaction and emotional connection.
Statement 2: Correct. Leaner channels, like emails or memos, are appropriate when the message is straightforward and unlikely to be misinterpreted.
Key AgilePM Concepts Referenced:
Effective Communication Channels: AgilePM Handbook, Chapter 4, Section 4.3.

Explanation:
Dissatisfaction with the Status Quo: The change formula includes dissatisfaction as a key driver for change. Without sufficient dissatisfaction, the motivation to change is diminished.
Other Options:
B, C, and D: These factors, while important, are not explicitly part of the Beckhard and Harris change formula.
Key AgilePM Concepts Referenced:
Change Formula Framework: AgilePM Handbook, Chapter 6, Section 6.5.

Explanation:
Agile Project Management places a premium on collaboration―the act of different roles (business, product, and technical) working together toward a shared goal. While communication is the exchange of information, collaboration goes further: it is joint problem-solving and decision-making that aligns perspectives to deliver value. AgilePM/DSDM principles explicitly promote active business involvement and empowered teams, creating an environment where collaboration is the default for refining requirements, planning increments, resolving trade-offs, and assuring quality. Ceremonies such as backlog refinement, Sprint Planning, daily coordination, and reviews exist to reinforce collaborative behavior, shorten feedback loops, and surface constraints early. Scrum itself (option C) is a framework that enables collaboration, but the definition given―“working together towards a shared goal”―is the definition of collaboration, not the framework or governance mechanisms. Governance (option D) concerns oversight and control structures rather than the cooperative behaviors that produce outcomes. Consequently, the statement most accurately and directly defines Collaboration.