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

Agile Practitioner

For each line, here is the appropriate option from A to E that applies:

The rooms and facilities must be deployed into live use at the end of each Timebox.

D. False (Assertion) True (Reason)

Rationale: While Evolutionary Development and Deployment can be combined in a timebox, it is not necessary that the rooms and facilities must be deployed into live use at the end of each timebox. Deployment into live use typically occurs after several timeboxes when the product is ready for release.

The tasks associated with each Solution Development Timebox should be included in the Delivery Plan.

A. True (Assertion) True (Reason)

Rationale: The Delivery Plan should outline the schedule of timeboxes and include the high-level activities planned for the upcoming project increment, which encompasses the tasks for each Solution Development Timebox.

The development approach should have been agreed during Foundations.

A. True (Assertion) True (Reason)

Rationale: The development approach is indeed something that should be agreed upon during the Foundations phase, as the Development Approach Definition sets the stage for how Evolutionary Development will proceed.

The resources from Timber Tigers and Earth Excavations should have been engaged before the start of Evolutionary Development.

C. True (Assertion) False (Reason)

Rationale: It is true that resources should be engaged before Evolutionary Development starts to ensure commitment and resource availability. However, the commitment is typically based on the detailed planning and agreements made during Foundations, not solely on pre-agreed resource levels at the project level.

A final Deployment phase should be held after Timebox C has completed.

E. False (Assertion) False (Reason)

Rationale: Deployment phases are usually not a one-time, final phase but occur incrementally as part of the timeboxed development. Additionally, the assessment of whether the expected benefits have been achieved is part of the benefits realization process and not necessarily the sole reason to have a final Deployment phase post-Timebox C.

For each line, here is the appropriate option from A to E that applies:

All internal works to be assigned to Timber Tigers throughout the project should be consolidated into one Structured Timebox.

E. False (Assertion) False (Reason)

Rationale: It is not practical or in line with Agile principles to consolidate all internal works into one Structured Timebox, as the work will likely need to be spread over multiple Timeboxes. Additionally, the Investigation step involves agreeing on how to meet the requirements of the Timebox, not necessarily consolidating all work into one.

Acceptance criteria for the front rooms to be developed in Timebox A should be described in detail and agreed during the Timebox Kick-Off

B. True (Assertion) True (Reason) BUT the reason does not explain the assertion

Rationale: While it is true that acceptance criteria should be agreed upon during the Timebox Kick-Off, the reason given is incorrect because the aim of the Investigation step is not necessarily to complete as much development work as possible but to plan and understand the work that will be carried out.

It is appropriate that both the Evolutionary Development phase and Deployment phase are shown in the first Project Increment.

A. True (Assertion) True (Reason) AND the reason explains the assertion

Rationale: Each Timebox should indeed include both Evolutionary Development and a Deployment phase. This assertion and reason correctly align with the concept of Timeboxing in Agile.

It is appropriate that the outputs of Timebox C are scheduled for deployment at the end of the first Project Increment.

A. True (Assertion) True (Reason) AND the reason explains the assertion

Rationale: The typical Timebox Plan does provide a schedule of high-level activities for the imminent Project Increment, which would include planning for deployment.

It is appropriate that Earth Excavations create a detailed plan of activities they will complete during Timebox C.

C. True (Assertion) False (Reason)

Rationale: While it is true that Earth Excavations should create a detailed plan for their activities in Timebox C, the reason is incorrect as the Solution Development Team is not solely responsible for planning all work details within a Timebox. This task would typically be a collaborative effort involving all relevant parties.

The initial action to deal with the lack of provision of a fire escape from the upstairs of the building in Timebox B should be:

• C. The Architect, in the role of Technical Co-ordinator, should escalate the issue to Architecture Angels’ Senior Management Team.

This is because the lack of a fire escape is a significant safety concern that could have legal and regulatory implications. It’s important that the Senior Management Team is aware of this issue so they can make informed decisions about how to address it. The Architect, in the role of Technical Co-ordinator, is well-positioned to understand the technical implications of this issue and communicate them to the Senior Management Team.

While revising the Timebox Plans (option A) or commencing understanding and delivering the new requirement (option B) could be part of the solution, these actions should be taken after the issue has been escalated and discussed with the Senior Management Team. Escalating the issue to the Marketing Director (option D) may not be the most effective course of action, as this is primarily a technical and safety issue, not a marketing one.

The correct answer is A .

If the Developers have estimated work using Planning Poker and story points , the right next step is to use a planning approach that helps Hira understand how much work the teams can realistically complete in a Sprint. This supports forecasting the likely number of Sprints required.

Why A is correct:

It keeps estimation in the same agile framework.

It uses the team’s practical delivery capability to forecast Sprint outcomes.

It avoids false precision while still giving Hira a useful basis for planning.

Why the other options are incorrect:

B is incorrect because converting story points directly into person-days undermines the purpose of relative estimation and can create misleading precision.

C is incorrect because assigning average time allocations to every item is too mechanical and not how AgilePM typically uses story-point-based estimation.

D is incorrect because Planning Poker is already an appropriate technique. There is no need to discard it simply because Hira needs a forecast.

So the best answer is A .

The correct answers are C and E .

AgilePM estimation should be:

collaborative,

proportionate,

realistic,

and open to refinement.

Why C is correct

“Allow flexibility and accept uncertainty in estimates that may be refined later.”

This is central to AgilePM. Estimates are expected to evolve as understanding improves. Early estimates are not fixed promises; they are informed forecasts based on current knowledge.

Why E is correct

“Use team-based estimation techniques as collective knowledge will improve accuracy.”

This also aligns strongly with AgilePM. Estimation benefits from the combined knowledge of the team because different people understand different aspects of the work, risks, and dependencies.

Why the other options are incorrect

A is too detailed and heavy for the likely stage and context.

B is wrong because Planning Poker supports relative/team-based estimation, but not “precise” early certainty.

D is contrary to agile estimation. Estimates are not meant to be fixed and artificially precise.

So the best answers are C, E .

The correct answer is C .

In AgilePM, VUCA-based risks are those driven by external volatility, uncertainty, complexity, or ambiguity in the environment. New legislation is a classic example of this because it originates outside the project and can force reprioritization, redesign, resource shifts, and rapid adaptation.

In this scenario, the new food hygiene laws are:

external to the project ,

time-bound , since they take effect in six months,

and capable of creating unplanned work , such as kitchen remodeling and resource diversion.

That makes this a VUCA-based risk , not an approach-based one.

Why C is correct:

The key reason is that the trigger is new legislation , which is an environmental change outside the project team’s control. AgilePM recognizes that such external changes can emerge during delivery and require the project to remain adaptable.

The possible impact here includes:

reassessing scope,

reassigning Infrastructure Team capacity,

reviewing compliance obligations,

and potentially adjusting delivery priorities.

That is exactly the kind of situation where AgilePM’s flexibility is valuable.

Why the other options are incorrect:

A. Approach-based, because past Project Increment planning failed to account for regulatory change, causing lack of contingency and resource risks.

This is not the best answer because the scenario does not say the team negligently ignored a known requirement. The key issue is the emergence of new laws , which is primarily an external uncertainty rather than a failure of method.

B. Approach-based, because Sukra Aroon should have tracked evolving legislation from the start to mitigate the risk.

This is also not the best answer. Even though compliance awareness is important, the fundamental source of the risk is still the external regulatory change , not simply Sukra’s handling of it.

D. VUCA-based, because gaps in internal compliance cause uncertainty in responding to changing regulations.

This is weaker than C because it shifts the cause toward an internal gap. The scenario itself emphasizes the introduction of new food hygiene laws , which is the main source of uncertainty and disruption.

AgilePM perspective:

AgilePM is designed to help teams respond to changing external conditions without losing focus on business value. Regulatory changes often require:

rapid reassessment,

collaborative decision-making,

flexible reprioritization,

and attention to compliance without abandoning the overall project goals.

Since this risk is caused by external legislation , the correct classification is VUCA-based .

Therefore, the best answer is C .

The correct answers are A and E .

In AgilePM, effective risk management depends on shared responsibility, continuous awareness, and proactive behaviour across the whole team. Risk is not something handled only by one role, one document, or one event. It is woven into the way the team works every day.

Why A is correct

“Team members should adopt a collaborative mindset, sharing responsibility for identifying and mitigating risks.”

This aligns strongly with AgilePM. Risks emerge from many areas:

business priorities,

technical feasibility,

compliance,

dependencies,

stakeholder engagement,

and delivery constraints.

Because of that, the best way to manage risk is for the team to work collaboratively and raise concerns early. Different people see different risks:

Mira may see value or prioritization risk,

Sukra may see architecture or integration risk,

Hira may see coordination or dependency risk,

Wanida may see compliance risk,

Developers may see delivery feasibility risks.

AgilePM encourages a culture where risks are surfaced openly and addressed together rather than left to a single person.

Why E is correct

“Risk management should be proactive and part of daily activities, not a separate process.”

This is also a core AgilePM principle. Risk management is most effective when it is:

continuous,

visible,

built into team discussions,

and handled as part of normal delivery activity.

That means risks should be considered during:

planning,

backlog discussions,

reviews,

daily collaboration,

dependency conversations,

and stakeholder feedback.

AgilePM does not treat risk as something only reviewed in occasional formal meetings. The team should be alert to emerging issues and respond before they become major problems.

Why the other options are incorrect

B. Hira should have sole responsibility for managing all risks with clear accountability.

This is incorrect. Hira, as Project Manager, has an important role in coordinating risk management, but AgilePM does not place all risk responsibility on one person. Risk management is shared across business, technical, and delivery roles.

C. Developers should resolve all risks collaboratively and promptly without escalation.

This is incorrect because some risks should be escalated. AgilePM encourages teams to resolve issues at the right level, but not to avoid escalation when broader decisions, sponsorship, governance, or cross-team intervention are needed.

D. Sukra Aroon should handle all technical risks independently to ensure the solution is fit for purpose.

This is incorrect because even technical risks often require collaboration. Sukra contributes architectural leadership, but technical risks may affect priorities, cost, compliance, usability, and business outcomes, so they should not be handled in isolation.

AgilePM perspective

AgilePM supports team behaviour where:

everyone is alert to risk,

risks are discussed early,

people collaborate across roles,

escalation happens when needed,

and risk thinking is part of everyday delivery.

So the two statements that best describe appropriate team behaviour for effective risk management are:

A, E

The correct answers are A and C .

AgilePM does not ignore uncertainty. It manages it openly and practically.

Why A is correct

“Use broad estimation ranges for high-uncertainty work and refine estimates as more information becomes available.”

This fits AgilePM very well because it acknowledges reality: some work is more uncertain than other work. Broad early estimates are often more honest and useful than false precision.

Why C is correct

“Identify key assumptions behind estimates and revisit them regularly as the project evolves.”

This is also strongly aligned. Estimates are shaped by assumptions, and AgilePM expects those assumptions to be made visible and rechecked as learning increases.

Why the other options are incorrect

B is too absolute. AgilePM still expects useful estimation even when uncertainty exists.

D is contrary to agile thinking because fixed early estimates create false certainty.

E is not appropriate because uncertain work should still be considered in planning, even if estimated at a higher level.

So the best answers are A, C .