AgilePM-Foundation Exam Dumps - APMG-International AgilePM Questions and Answers

Referent Power: This form of power is derived from the personal qualities of the leader, such as charisma, integrity, or ability to inspire, making them a role model for others. AgilePM values leaders who lead by influence rather than authority.

Other Options:

Legitimate: Based on a formal position or title.

Reward: Tied to the ability to offer incentives.

Coercive: Involves using fear or threats, which is not ideal in Agile environments.

Key AgilePM Concepts Referenced:

Leadership Styles: AgilePM Handbook, Chapter 4, Section 4.5.

Small Incremental/Iterative Releases: Delivering change in smaller increments allows for immediate feedback and adaptation, embodying the concept of 'Minimum Viable Change Practice.'

Other Options:

A: Big Bang involves a single, large-scale rollout, unsuitable for iterative practices.

B: Phased rollouts involve sequential implementation but may not emphasize iteration.

C: Voluntary Adoption doesn’t inherently align with iterative releases.

Key AgilePM Concepts Referenced:

Iterative Delivery Strategies: AgilePM Handbook, Chapter 3, Section 3.7.

Scrum supplies the core framework (roles, events, artifacts) for empirically building products, but it is intentionally lightweight. AgilePM (based on DSDM) complements Scrum by offering a well-tested pool of practices, tools, and techniques that strengthen day-to-day delivery and governance without altering Scrum’s essence. Typical enhancements include MoSCoW prioritization to manage variable scope, timeboxing to protect cadence, facilitated workshops and modeling to accelerate shared understanding, and explicit roles for business involvement to improve decision flow. AgilePM also provides guidance on project-level controls—such as business cases, incremental release planning, and benefits focus—that sit outside Scrum’s product-delivery scope. For a Scrum Master, this combination is valuable: Scrum remains the engine of iterative delivery, while AgilePM offers practical methods to refine backlog refinement, clarify acceptance criteria, manage dependencies, and support predictable delivery against time and cost constraints. Thus, the pairing gives Scrum Masters a richer toolkit to coach teams, align stakeholders, and handle real-world project contexts where governance, prioritization, and incremental release structures are needed—precisely what option B describes.

The DSDM philosophy emphasizes that the best business value emerges when projects are aligned to clear business goals, deliver frequently, and involve the collaboration of motivated and empowered people1. The eight principles of DSDM support this philosophy and are brought to life by guiding the team in the attitude it must take and the mindset it must adopt to deliver consistently while remaining flexible1. These principles are supported by process, people, products, and practices, which enable organizations to deliver best value business solutions collaboratively1.

The Solution Architecture Definition is an evolutionary product that provides a high-level design framework for the solution2. It is intended to cover both business and technical aspects of the solution to a level of detail that makes the scope of the solution clear but does not constrain evolutionary development2. This ensures that the solution architecture supports the business direction and the solution under development will be fit for its intended purpose3