I85PREP
⌘ K
APMG Agile Change Agent study materials
APMG Agile Change Agent study resources

APMG Agile Change Agent practice questions

One question at a time. Build your APMG Agile Change Agent understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Roadmap

In Agile Change Management, the roadmap is best described as which type of artefact?

  1. A financial forecast of the cost of the change programme
  2. A detailed Gantt chart fixing every task and resource to a calendar date
  3. A register of risks with owners and mitigation actions
  4. A visual summary of the change journey showing key milestones and outcomes over time Correct answer.

Explanation

The roadmap communicates the overall change journey and the sequence of outcomes and milestones at a high level. It is deliberately visual and outcome-focused rather than a task-level schedule. Detailed schedules and risk registers are separate artefacts.

Question 2Roadmap

Why does an Agile Change roadmap emphasise outcomes rather than deliverables?

  1. Because deliverables cannot be estimated in agile working
  2. Because outcomes are always approved by the finance function
  3. Because deliverables are only relevant to IT projects
  4. Because outcomes describe the benefits and behaviours the organisation wants to achieve Correct answer.

Explanation

Outcome focus keeps attention on the change in behaviour and benefits the organisation seeks, allowing flexibility in how those are delivered. Deliverables are the means, not the end. This lets plans adapt as understanding grows.

Question 3Roadmap

A change team is building its first roadmap. Which element should appear at the top level of the roadmap?

  1. The supplier contract payment schedule
  2. Individual team members' daily tasks
  3. The sequence of change milestones and expected benefits Correct answer.
  4. The detailed test scripts for each release

Explanation

A roadmap shows the sequence of milestones and the benefits expected at each stage. It operates at a level above task detail. Daily tasks, test scripts and payment schedules belong in delivery plans.

Question 4Roadmap

What is the main benefit of keeping the roadmap visible to stakeholders throughout the change?

  1. It helps people understand where they are in the journey and what comes next Correct answer.
  2. It locks the scope so no changes can be made
  3. It removes the need for any other communication
  4. It guarantees the change will finish on time

Explanation

A visible roadmap gives stakeholders a shared sense of direction, progress and upcoming steps. It supports engagement and reduces uncertainty. It does not replace other communication or fix scope.

Question 5Roadmap

Which statement best captures how an Agile Change roadmap differs from a traditional fixed project plan?

  1. It is created once by the sponsor and never revisited
  2. It is reviewed and adapted as learning emerges during the change Correct answer.
  3. It lists every activity with fixed start and end dates
  4. It is updated only at project closure

Explanation

An agile roadmap is a living artefact, reviewed and refined as new information and learning emerge. This supports responsiveness to change. Traditional plans tend to be more fixed and activity-detailed.

Question 6Roadmap

What role does the roadmap play in aligning a change with organisational strategy?

  1. It records only operational tasks
  2. It sets the annual budget
  3. It shows how change milestones contribute to strategic goals Correct answer.
  4. It replaces the strategic plan

Explanation

The roadmap connects change activity to strategic intent by showing how milestones deliver against goals. This helps maintain sponsorship and prioritisation. It does not replace strategy or budgets.

Question 7Roadmap

Which of the following is a typical horizon used when structuring an Agile Change roadmap?

  1. Per minute
  2. Quarterly Correct answer.
  3. Daily
  4. Hourly

Explanation

Roadmaps typically use horizons such as quarters or phases, which give enough perspective to show the change journey without over-committing to detail. Very short intervals are too granular for roadmap level.

Question 8Roadmap

What does a milestone on an Agile Change roadmap represent?

  1. A line item in the procurement plan
  2. A software defect to be fixed
  3. A single team member's holiday
  4. A significant point of progress or decision in the change journey Correct answer.

Explanation

Milestones mark significant progress points or decision gates that help track the change journey. They are meaningful checkpoints rather than administrative details.

Question 9Roadmap

A programme manager wants the roadmap to show dependencies between workstreams. What is the most appropriate way to represent this?

  1. Show linking arrows or connection points between related milestones Correct answer.
  2. Remove the dependency information to keep the roadmap simple
  3. Replace the roadmap with a task list
  4. Add a separate appendix listing every dependency in text

Explanation

Dependencies are best shown visually by linking related milestones, which keeps the roadmap readable while conveying sequencing. This supports coordination without overloading the artefact.

Question 10Roadmap

During a roadmap review, the team discovers a key benefit cannot be realised until a later phase. What is the best response?

  1. Add more tasks to the current phase without changing milestones
  2. Cancel the change immediately
  3. Keep the original sequence and ignore the finding
  4. Move the affected milestone and re-sequence the roadmap accordingly Correct answer.

Explanation

The roadmap should be re-sequenced to reflect new understanding so that milestones align with realistic benefit realisation. This is the essence of adaptive planning. Ignoring the finding or cancelling without analysis is not proportionate.

Question 11Roadmap

A stakeholder asks how the roadmap will be kept current. Which practice best answers this?

  1. Only update the roadmap when the change is complete
  2. Freeze the roadmap at the start of the change
  3. Review the roadmap at regular intervals and after significant learning events Correct answer.
  4. Delegate all roadmap updates to the finance team

Explanation

Regular reviews and updates after significant events keep the roadmap relevant and trusted. This reflects the iterative nature of agile change. Freezing or deferring updates reduces its usefulness.

Question 12Roadmap

Which combination best describes the relationship between the roadmap and the change plan?

  1. The plan replaces the roadmap once work starts
  2. The roadmap is the detailed plan and the plan is the summary
  3. The roadmap gives the high-level journey and the plan details the activities to deliver it Correct answer.
  4. They are identical documents with different titles

Explanation

The roadmap provides the high-level view, while the change plan details the activities needed to progress along it. They are complementary at different levels of detail.

Question 13Roadmap

A change lead wants the roadmap to communicate the pace of change to stakeholders. Which feature most directly supports this?

  1. Spacing of milestones across the timeline to show intensity Correct answer.
  2. Colour-coding each team member's role
  3. Listing all risks in the roadmap header
  4. Including the full budget breakdown

Explanation

The spacing and clustering of milestones across the timeline visually convey how intense the pace of change will be at different points. This helps stakeholders prepare. Role colours, risks and budgets serve different purposes.

Question 14Roadmap

Which of the following best explains why an Agile Change roadmap should be co-created with stakeholders?

  1. To reduce the number of milestones to zero
  2. To avoid the need for a sponsor
  3. To prevent any future changes to the roadmap
  4. To ensure the roadmap reflects diverse perspectives and gains commitment Correct answer.

Explanation

Co-creation brings in diverse perspectives, improves the quality of the roadmap and builds ownership and commitment. It does not remove the need for a sponsor or prevent future change.

Question 15Roadmap

A team is unsure whether a planned activity belongs on the roadmap or in the detailed plan. What test should they apply?

  1. Is it owned by the sponsor?
  2. Does it represent a significant outcome or milestone in the journey? Correct answer.
  3. Does it take more than one hour?
  4. Is it recorded in the risk log?

Explanation

Roadmap content is defined by significance to the change journey, such as outcomes and milestones. Detailed activities belong in the plan. Duration, ownership or risk-log presence are not the deciding criteria.

Question 16Roadmap

How should a roadmap handle uncertainty about future phases?

  1. Specify every future task in full detail now
  2. State that no change will occur after phase one
  3. Show future phases at a high level with less detail, refining as certainty increases Correct answer.
  4. Omit future phases entirely

Explanation

Agile roadmaps use a rolling-wave approach, showing later phases at a lower level of detail and refining them as certainty grows. This balances direction with flexibility.

Question 17Roadmap

Which outcome best indicates that a roadmap is fulfilling its communication purpose?

  1. The roadmap has not changed since inception
  2. The roadmap contains the maximum possible number of tasks
  3. The roadmap is only accessible to the programme board
  4. Stakeholders can describe the change journey and their part in it Correct answer.

Explanation

Effective communication means stakeholders understand the journey and their role within it. Volume of tasks, rigidity or restricted access do not indicate good communication.

Question 18Roadmap

A sponsor wants to add a new regulatory milestone to the roadmap mid-programme. What should the change lead do first?

  1. Add it to the detailed plan only and leave the roadmap unchanged
  2. Reject the request because roadmaps cannot change
  3. Assess the impact on sequencing, dependencies and benefits before updating the roadmap Correct answer.
  4. Remove an existing milestone to make room without analysis

Explanation

New requirements should be assessed for impact on sequence, dependencies and benefits before the roadmap is updated. This preserves coherence. Rejecting outright or making unanalysed swaps undermines the roadmap.

Question 19Roadmap

Which element helps a roadmap show the intended benefits of each phase?

  1. A benefits statement linked to each milestone or phase Correct answer.
  2. A list of team meeting dates
  3. A copy of the organisation chart
  4. A log of customer complaints

Explanation

Linking benefits statements to phases or milestones makes the value of each stage explicit. This supports decision-making and stakeholder buy-in. Meeting dates, org charts and complaint logs serve other purposes.

Question 20Roadmap

A change lead notices the roadmap has become cluttered with operational detail. What is the best corrective action?

  1. Delete the roadmap and start again
  2. Add more colour to distinguish the detail
  3. Convert the roadmap into a spreadsheet of tasks
  4. Move operational detail into the supporting plan and keep the roadmap at outcome level Correct answer.

Explanation

The roadmap should stay at outcome and milestone level, with operational detail held in supporting plans. This restores clarity and purpose. Adding colour or converting to a task list does not fix the underlying issue.

Question 21Roadmap

In what way does the roadmap support decision-making about when to engage particular stakeholder groups?

  1. By showing when relevant milestones occur so engagement can be timed accordingly Correct answer.
  2. By listing every stakeholder's phone number
  3. By setting the salary bands for the change team
  4. By recording the outcome of past meetings

Explanation

Milestone timing on the roadmap indicates when different stakeholder groups will be affected, allowing engagement to be planned and timed effectively. Contact details, meeting minutes and pay bands are unrelated.

Question 22Roadmap

A roadmap shows a benefit milestone in phase two, but the enabling capability is only delivered in phase three. What does this most likely indicate?

  1. The roadmap is well sequenced
  2. The benefit should be removed from the roadmap
  3. The capability should be ignored
  4. There is a sequencing inconsistency that requires review Correct answer.

Explanation

A benefit cannot be realised before its enabling capability is in place, so this ordering signals a sequencing inconsistency to investigate. Reviewing and re-sequencing restores coherence. Removing the benefit or ignoring the capability avoids the issue.

Question 23Roadmap

Which approach best balances the need for a stable roadmap with the need for flexibility?

  1. Fix all milestones at the outset and permit no deviation
  2. Maintain stable outcome-level milestones while allowing lower-level detail to flex Correct answer.
  3. Change the roadmap randomly each week
  4. Abandon milestones entirely

Explanation

Keeping outcome-level milestones stable provides direction, while flexibility at lower levels allows adaptation to learning. This balance is central to agile roadmapping. Random change or abandoning milestones removes useful structure.

Question 24Roadmap

A stakeholder argues the roadmap should include a full risk register so everything is in one place. What is the strongest reason to keep them separate?

  1. Each artefact serves a distinct purpose and combining them reduces the roadmap's clarity Correct answer.
  2. Risk registers are confidential and cannot be shared
  3. Risk registers are only used after closure
  4. Roadmaps must never reference risk

Explanation

Artefacts work best when each serves its purpose clearly; merging a detailed risk register into the roadmap would obscure the journey view. Risks can still be referenced at a high level. Confidentiality, prohibition and timing are not valid general reasons.

Question 25Roadmap

How does the roadmap most effectively demonstrate the 'why' of the change to senior leaders?

  1. By linking the change journey to strategic drivers and expected benefits Correct answer.
  2. By listing the delivery team's qualifications
  3. By showing the number of meetings planned
  4. By detailing the software architecture

Explanation

Senior leaders are persuaded by the connection between the change and strategic drivers and benefits. This gives the roadmap its persuasive power at executive level. Operational or technical detail does not convey the 'why'.

Question 26Roadmap

Which of the following best describes the primary purpose of an Agile Change roadmap?

  1. To provide a visual summary of the change journey over time, showing key phases, milestones and intended outcomes Correct answer.
  2. To document every task and activity required to deliver the change in detail
  3. To replace the need for a detailed project plan
  4. To assign individual responsibilities for each change activity

Explanation

An Agile Change roadmap communicates the overall change journey at a high level, highlighting phases, milestones and outcomes to align stakeholders. It is not a detailed task list, nor does it replace a project plan or assign individual responsibilities.

Question 27Roadmap

In an Agile Change roadmap, what is typically shown along the horizontal axis?

  1. Time, often divided into phases or increments Correct answer.
  2. The budget breakdown
  3. The organisational structure
  4. The list of stakeholders

Explanation

The horizontal axis of a roadmap usually represents time, allowing the sequence of phases or increments to be visualised. Organisational structure, budget and stakeholders are not typically plotted along this axis.

Question 28Roadmap

Which of the following is a key benefit of using a roadmap in Agile Change?

  1. It provides a single, accessible view that helps align stakeholders and guide decisions Correct answer.
  2. It eliminates the need for regular stakeholder communication
  3. It guarantees that the change will be delivered on time and within budget
  4. It replaces the need for a business case

Explanation

A roadmap offers a shared visual reference that supports alignment and informed decision-making. It does not guarantee delivery outcomes, remove the need for communication, or replace the business case.

Question 29Roadmap

When creating an Agile Change roadmap, what is the recommended first step?

  1. Assign roles and responsibilities to team members
  2. Define the detailed tasks for the first phase
  3. Allocate the budget for each phase
  4. Identify the vision and intended outcomes of the change Correct answer.

Explanation

Starting with the vision and outcomes ensures the roadmap is anchored in the purpose of the change. Detailed tasks, budget allocation and role assignment come later and should align with that vision.

Question 30Roadmap

Which of the following best describes how a roadmap should be used during change delivery?

  1. As a fixed document that is locked at the start and never changed
  2. As a detailed schedule that is updated daily
  3. As a one-off communication tool used only at kick-off
  4. As a living artefact that is reviewed and updated regularly Correct answer.

Explanation

An Agile Change roadmap is a living artefact, reviewed and adapted as learning emerges. It is not fixed, nor is it a one-off or daily schedule.

Question 31Roadmap

What does the 'why' of the change refer to in the context of a roadmap?

  1. The resources required to deliver the change
  2. The risks associated with the change
  3. The sequence of activities to be performed
  4. The reasons and benefits that justify the change Correct answer.

Explanation

The 'why' articulates the purpose and intended benefits of the change, which the roadmap should clearly communicate. Activities, resources and risks are important but are not the 'why'.

Question 32Roadmap

Which of the following is a common pitfall when creating an Agile Change roadmap?

  1. Keeping the roadmap at a high level
  2. Aligning the roadmap with organisational strategy
  3. Reviewing the roadmap regularly with stakeholders
  4. Including too much detail, making it hard to see the big picture Correct answer.

Explanation

A roadmap should provide a high-level view; excessive detail obscures the overall journey. High-level focus, regular review and strategic alignment are all recommended practices.

Question 33Roadmap

What is the relationship between the roadmap and the change vision?

  1. The roadmap and vision are unrelated concepts
  2. The roadmap replaces the need for a vision statement
  3. The roadmap should visually represent and reinforce the change vision Correct answer.
  4. The vision is derived from the roadmap after it is created

Explanation

The roadmap translates the vision into a visual journey, helping stakeholders see how the vision will be realised over time. It does not replace the vision, nor is the vision derived from the roadmap.

Question 34Roadmap

A change lead is presenting the roadmap to a group of senior executives. What should be the primary focus of the presentation?

  1. The detailed tasks scheduled for the next two weeks
  2. The individual performance targets of team members
  3. The strategic outcomes and benefits expected from the change Correct answer.
  4. The technical specifications of the solution

Explanation

Senior executives are most interested in the strategic outcomes and benefits that justify the investment. Detailed tasks, individual targets and technical specifications are less relevant at this level.

Question 35Roadmap

A team is developing a roadmap for a large-scale change. How should they handle the later phases of the roadmap?

  1. Omit them entirely to avoid overcommitting
  2. Delegate them to a separate team to plan independently
  3. Plan them in as much detail as the first phase
  4. Outline them at a high level, with more detail added as they approach Correct answer.

Explanation

Agile roadmaps use rolling-wave planning: later phases are outlined at a high level and elaborated as certainty increases. Planning all phases in equal detail upfront is counter to agile principles.

Question 36Roadmap

What is the most effective way to show the sequence of change activities on a roadmap?

  1. Use a Gantt chart with dependencies
  2. Arrange activities along a timeline from left to right Correct answer.
  3. Use a pie chart to show proportions
  4. List activities in a numbered table

Explanation

A timeline running from left to right is the conventional and intuitive way to show sequence on a roadmap. Gantt charts, tables and pie charts serve different purposes and are less effective for a high-level roadmap.

Question 37Roadmap

A change lead wants to ensure the roadmap remains relevant throughout the change. What should they do?

  1. Delegate roadmap maintenance to the project management office
  2. Lock the roadmap at the start to provide stability
  3. Review and update the roadmap at regular intervals and at key milestones Correct answer.
  4. Only update the roadmap when a major failure occurs

Explanation

Regular reviews and updates at milestones keep the roadmap aligned with emerging realities. Locking it or updating only on failure undermines its usefulness as a living tool.

Question 38Roadmap

Which of the following best describes how the roadmap supports stakeholder engagement?

  1. It identifies which stakeholders are responsible for each task
  2. It records stakeholder contact details
  3. It highlights when stakeholder groups will be affected and need to be engaged Correct answer.
  4. It replaces the stakeholder engagement plan

Explanation

The roadmap shows the timing of changes and impacts, helping to plan when to engage specific stakeholder groups. It does not assign task responsibility, store contact details, or replace the engagement plan.

Question 39Roadmap

A roadmap shows a major change milestone in three months. What should the change lead do to prepare stakeholders?

  1. Wait until one week before the milestone to communicate
  2. Only inform senior management and let them cascade
  3. Assume stakeholders will notice the change when it happens
  4. Begin engaging and preparing stakeholders well in advance of the milestone Correct answer.

Explanation

Advance engagement gives stakeholders time to prepare and reduces resistance. Late or minimal communication increases the risk of disruption.

Question 40Roadmap

What is the recommended approach for incorporating dependencies between workstreams on a roadmap?

  1. List them in a separate spreadsheet
  2. Only show dependencies that are at risk
  3. Show them as simple arrows or links between related items Correct answer.
  4. Ignore them to keep the roadmap simple

Explanation

Simple visual links or arrows can indicate dependencies without cluttering the roadmap. Separate lists or ignoring them reduces the roadmap's usefulness.

Question 41Roadmap

A change lead is concerned that the roadmap is too complex for stakeholders to understand. What should they do?

  1. Use technical jargon to convey expertise
  2. Simplify the roadmap by focusing on key phases, milestones and outcomes Correct answer.
  3. Add more detail to ensure completeness
  4. Replace the roadmap with a detailed project plan

Explanation

Simplifying to key elements improves clarity and stakeholder understanding. Adding detail or jargon obscures the message, and replacing with a detailed plan defeats the roadmap's purpose.

Question 42Roadmap

How can a roadmap best demonstrate the benefits of the change to stakeholders?

  1. By showing benefit milestones and linking them to phases Correct answer.
  2. By including a cost breakdown
  3. By listing all features to be delivered
  4. By showing the number of people involved

Explanation

Benefit milestones linked to phases show when value will be realised, which is compelling for stakeholders. Feature lists, cost breakdowns and headcounts do not directly convey benefits.

Question 43Roadmap

What role does the roadmap play in agile change planning?

  1. It replaces the need for sprint planning
  2. It offers a flexible planning tool that can adapt to change Correct answer.
  3. It provides a fixed schedule that must be adhered to
  4. It is used only for retrospective analysis

Explanation

The roadmap is a flexible planning aid that supports adaptation as the change progresses. It is not fixed, does not replace sprint planning, and is used proactively, not just retrospectively.

Question 44Roadmap

A change lead wants to use the roadmap to manage expectations about what will be delivered and when. Which approach is most effective?

  1. Show phased delivery with clear milestones and outcomes for each phase Correct answer.
  2. Show a single big-bang delivery at the end
  3. Avoid showing dates to prevent commitment
  4. Show only the final delivery date

Explanation

Phased delivery with clear milestones and outcomes helps stakeholders understand incremental value and manage expectations. A single final date or no dates at all provides less transparency.

Question 45Roadmap

Which of the following best describes the level of detail appropriate for an Agile Change roadmap?

  1. As detailed as a project schedule
  2. High-level, focusing on phases, milestones and outcomes Correct answer.
  3. Only a list of high-level goals without any timeline
  4. Detailed enough to assign tasks to individuals

Explanation

An Agile Change roadmap should be high-level, emphasising phases, milestones and outcomes to provide a clear overview. It should not descend to task-level detail or omit the timeline entirely.

Question 46Roadmap

A change lead is reviewing the roadmap and notices that a key stakeholder group is not represented in any phase. What should they do?

  1. Wait until the group raises concerns
  2. Review the change impact and update the roadmap to include engagement with that group Correct answer.
  3. Proceed as planned since the group may not be affected
  4. Remove the group from the stakeholder register

Explanation

The roadmap should reflect all stakeholder groups affected by the change. Reviewing impact and updating the roadmap ensures no group is overlooked, which reduces risk of resistance.

Question 47Roadmap

What is the most appropriate way to handle a situation where the roadmap shows a dependency on an external supplier that may not deliver on time?

  1. Remove the dependency from the roadmap to avoid concern
  2. Highlight the dependency on the roadmap and develop a contingency plan Correct answer.
  3. Assume the supplier will deliver and proceed
  4. Ignore the dependency as it is outside the team's control

Explanation

Highlighting the dependency and planning contingency demonstrates proactive risk management. Ignoring, removing or assuming delivery are all risky and may lead to failure.

Question 48Roadmap

A change lead is using the roadmap to communicate with a diverse group of stakeholders, some of whom are remote and some in-person. What is the best approach to ensure the roadmap is effective?

  1. Provide a digital, accessible version that can be shared and viewed by all Correct answer.
  2. Only present the roadmap in face-to-face meetings
  3. Keep the roadmap confidential to the leadership team
  4. Use a large printed poster in the office only

Explanation

A digital, accessible version ensures all stakeholders can view the roadmap regardless of location. Relying solely on physical posters or face-to-face meetings excludes remote stakeholders, and restricting access undermines transparency.

Question 49Roadmap

How should a change lead use the roadmap to support decision-making about resource allocation?

  1. By showing the timing and duration of activities to anticipate resource needs Correct answer.
  2. By avoiding resource information to keep the roadmap simple
  3. By listing all team members and their availability
  4. By including a detailed budget forecast

Explanation

The roadmap's timeline of activities helps anticipate when resources will be needed, supporting allocation decisions. Detailed availability, budget forecasts and omitting resource information are less effective for this purpose.

Question 50Roadmap

A change lead is faced with a situation where the roadmap shows a key milestone that is now unachievable due to unforeseen circumstances. What is the best course of action?

  1. Re-plan the milestone, communicate the change to stakeholders, and update the roadmap Correct answer.
  2. Blame the team for the delay
  3. Keep the milestone as planned to avoid admitting failure
  4. Remove the milestone from the roadmap without communication

Explanation

Transparent re-planning and communication maintain trust and allow stakeholders to adjust. Keeping an unachievable milestone, removing it silently, or blaming others damages credibility.