Which of the following statements, about the behavior of effective change managers as agile practitioners, are true?
They should take a single framework and apply it persistently.
They should remain resilient, flexible, and willing to learn.
Answer : B
Statement 1: Incorrect. Agile is rooted in adaptability and tailoring practices to fit the specific needs of a project. Taking a single framework and applying it persistently reflects rigidity, which contradicts the Agile principles of flexibility and continuous improvement. AgilePM advocates selecting and combining frameworks (e.g., Scrum, Kanban) based on the project environment rather than sticking to one rigidly.
Statement 2: Correct. Resilience, flexibility, and a willingness to learn are central to Agile practitioners. They must adapt to challenges and new information to ensure continuous delivery of value. This aligns with Agile values of embracing change over following strict plans and the AgilePM philosophy of iterative improvement.
Key AgilePM Concepts Referenced:
Flexibility over Rigidity: AgilePM Handbook, Chapter 1, Section 1.4 ('The Agile Mindset').
Iterative Development and Learning: Chapter 3, Section 3.5 (Iterative Principles).
Which of the following statements about the MoSCoW rules for the ratio of prioritized Requirements are true?
The minimum Usable Subset must not exceed 60% of the total number of requirement
It is recommended that around 20% of available effort should be allocated to Could requirements.
Answer : B
AgilePM's MoSCoW guidance sets effort-based guardrails, not simple counts of requirements. A common rule of thumb is: Must Haves ~60% of available effort, Should Haves ~20%, and Could Haves ~20%, with Won't Haves excluded from the current delivery timeframe. This ensures sufficient contingency (mainly in Coulds) to absorb change while protecting time, cost, and quality. Statement 2 aligns with that guidance: allocating around 20% of the available effort to Could requirements provides the ''give'' needed inside timeboxes and releases. Statement 1 is misstated: it refers to the number of requirements and equates the Minimum Usable Subset with a percentage of items; AgilePM speaks in terms of effort, not item count. Hence, only statement 2 is true.
Identify the missing words in the following statement.
In projects, especially when using non-agile methods, governance often seems to focus on [ ? ].
Answer : D
Comprehensive and Detailed 150 to 300 words Explanation From Exact Extract of Agile Project Management (paraphrased):
Agile principles highlight a contrast with traditional governance, which frequently centers on adherence to a predetermined plan. The Agile Manifesto instead values responding to change over following a plan. AgilePM operationalizes this by fixing time and cost, protecting quality, and flexing scope using MoSCoW prioritization. Planning remains essential, but it is lightweight, iterative, and continuously refined through empirical feedback from delivered increments. Governance, therefore, is reframed around evidence of value and outcomes rather than strict conformance to upfront schedules and documents. The statement points to the non-agile tendency to prioritize following a plan, which AgilePM deliberately rebalances with timeboxing, frequent review, and collaborative decision-making that allows teams to incorporate learning and change while keeping projects on track. Hence, the missing words are ''Following a plan.''
If two separate development teams are required to work on the same project, how will this be managed?
Answer : A
Comprehensive and Detailed 150--300 words Explanation (paraphrased from Scrum & AgilePM practice):
When multiple teams build a single product within one project, effective backlog ownership and value alignment are critical. Scrum practice---and AgilePM when combined with Scrum---supports one Product Owner for the product, even when several teams deliver increments in parallel. A single Product Owner preserves a single ordered Product Backlog, unified priorities, and consistent acceptance criteria, minimizing conflicts and dependency churn. Each team may have its own Scrum Master to optimize facilitation and impediment removal locally, but the essential management mechanism for cross-team coherence is shared product ownership (one Product Owner) paired with lightweight cross-team planning and frequent integration. Splitting into two separate projects (with separate roles) for one product typically fragments value flow and complicates governance. Likewise, mandating different Business Visionaries per team dilutes accountability for the product outcome. Hence, the preferred and most effective approach is that both teams share the same Product Owner to maintain a single value and prioritization voice.
Which definition describes 'transition' in Bridges' model of human transitions?
Answer : B
Emotional Process: Transition, as per Bridges' model, refers to the psychological adjustment individuals go through when adapting to change. It's not about the change itself but how people internally process the transition.
Other Options:
A and D: These relate to the external processes of implementing change.
C: This overlaps with transition but is incomplete as a definition.
Key AgilePM Concepts Referenced:
Bridges' Transition Model: AgilePM Handbook, Chapter 6, Section 6.3.
How are the business roles critical to the success of a DSDM project?
Answer : A
Business roles are critical in a DSDM project as they guide the evolution of the solution at a detailed level6. They provide day-to-day business direction and ensure that the solution being developed aligns with the business needs and objectives.
Which should always be the first step in the Continuous Change Management Cycle?
Answer : C
Discovery: The Continuous Change Management Cycle starts with understanding the current situation, challenges, and opportunities. Discovery ensures that subsequent steps are informed and targeted.
Other Options:
A: Ideas come after discovery.
B: Prioritization occurs after potential solutions are identified.
D: Action follows the planning and prioritization phases.
Key AgilePM Concepts Referenced:
Continuous Change Management Cycle: AgilePM Handbook, Chapter 6, Section 6.6.