Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. APMG-International
  5. AgilePM-Practitioner

APMG-International AgilePM-Practitioner Exam Questions
Agile Project Management (AgilePM) Practitioner (Page 3 )

Updated On: 15-Feb-2026
Page 3 of 28
PDF with 134 Questions
View Related Case Study

HOTSPOT (Drag and Drop is not supported)

Using the Project Scenario answer the following question about the technical quality of the solution to be delivered. An assessment of the maintenance requirement for the new reservation system was made during Feasibility.

Column 1 describes a list of different types of hotel reservation systems considered. Column 2 lists the three DSDM maintainability objectives. For each description in Column 1, select from Column 2 the maintainability objective it would support.

Each selection from Column 2 can be used once, more than once or not at all.

Column 1:

1. Off-the-shelf software with ready-to-use templates that will need to be customised to fully meet Hoy Hall requirements, after deployment.

2. Developing a fully functioning in-house system, developed and hosted by Architecture Angels IT Operations team.

3. All-in-one web-based reservation and accommodation management system built to Hoy Hall's specification.

4. All bookings for Hoy Hall to be scheduled by one of the other two hotels within the group, until a suitable system can be implemented at the site.

5. A spreadsheet is used to capture customer details manually. Data will then be exported into a fully functional system at a later date.

Column 2

Maintainability is a required attribute of the initial delivered solution

Deliver first, re-engineer later

Short-term, tactical solution

  1. See Explanation section for answer.

Answer(s): A

Explanation:

For each of the descriptions in Column 1, the maintainability objective from Column 2 that each would support is as follows:
Off-the-shelf software with ready-to-use templates that will need to be customised to fully meet Hoy

Hall requirements, after deployment.
A: Maintainability is a required attribute of the initial delivered solution Rationale: Customizing off-the-shelf software indicates a need for the solution to be maintainable from the onset to allow for these adjustments.
Developing a fully functioning in-house system, developed and hosted by Architecture Angels IT Operations team.
A: Maintainability is a required attribute of the initial delivered solution Rationale: In-house developed systems need to be maintainable to facilitate future changes and enhancements by the team that created them.
All-in-one web-based reservation and accommodation management system built to Hoy Hall's specification.
A: Maintainability is a required attribute of the initial delivered solution Rationale: A system built to specific requirements will require the ability to maintain and adjust the system as needs evolve, making maintainability a key initial attribute. All bookings for Hoy Hall to be scheduled by one of the other two hotels within the group, until a suitable system can be implemented at the site.
C: Short-term, tactical solution
Rationale: This is clearly a temporary measure until a proper system is in place, indicative of a tactical solution to address immediate needs.
A spreadsheet is used to capture customer details manually. Data will then be exported into a fully functional system at a later date.
C: Short-term, tactical solution
Rationale: Using a spreadsheet is a stop-gap solution to manage information in the short term, emphasizing the tactical nature rather than long-term maintainability. Option B is not selected for any of the descriptions as none of them imply an approach of delivering first with the intention to re-engineer later. They all suggest a need for immediate maintainability or a short-term fix, not a re-engineering approach.



View Related Case Study

Answer the following questions about the acceptance criteria within the project.

Decide whether the approach to setting and using acceptance criteria has been applied appropriately and select the response that supports your decision.

When specifying high-level prioritised requirements during Foundations, the Business Visionary has suggested that acceptance criteria for the requirement to "temporarily weatherproof the roof" should NOT be set until Solution Development Timebox A.

Is this an appropriate approach to setting high-level acceptance criteria?

  1. Yes, because the Local Planning Authority Officer will set the acceptance criteria.
  2. Yes, because acceptance criteria are NOT set before the Timeboxed work is started.
  3. No, because by the end of Foundations the quality expectations and overall acceptance criteria for at least the first increment should have been set, and high-level acceptance criteria set for later increments.
  4. No, because a Review Session should have been scheduled during Feasibility to enable the Solution Development Team to validate their understanding of the Local Planning Authority Officer's expectations.

Answer(s): C

Explanation:

C: No, because by the end of Foundations the quality expectations and overall acceptance criteria for at least the first increment should have been set, and high-level acceptance criteria set for later increments.
Rationale:
In Agile Project Management, it's important to establish high-level acceptance criteria early in the project to guide development and ensure that the solution meets the business needs and quality expectations. The Foundations phase is when the project's scope, objectives, and methods are defined, including the acceptance criteria for the first increment and at a high level for subsequent increments. This ensures that everyone has a clear understanding of what "done" looks like before development begins, reducing the risk of misalignment and rework.



View Related Case Study

Answer the following questions about the acceptance criteria within the project.

Decide whether the approach to setting and using acceptance criteria has been applied appropriately and select the response that supports your decision.

At the beginning of Solution Development Timebox A, the Timebox is being planned in detail. Although Foundations was conducted at a high level, the Prioritised Requirements List was baselined. Now the Solution Development Team is setting detailed acceptance criteria against each requirement.

Is this an appropriate approach to setting detailed acceptance criteria?

  1. Yes, because acceptance criteria can only be understood at a high level during Foundations and will always need further investigation.
  2. Yes, because the Solution Development Team members will be setting acceptance criteria for the first time during Solution Development Timebox A.
  3. No, because the Solution Development Team should NOT be involved in setting acceptance criteria.
  4. No, because acceptance criteria should be set in detail against each requirement during Foundations.

Answer(s): A

Explanation:

A: Yes, because acceptance criteria can only be understood at a high level during Foundations and will always need further investigation.
Rationale:
In Agile Project Management, while the Foundations phase does involve setting high-level expectations and a prioritized requirements list, the detailed acceptance criteria are often refined during the actual Solution Development iterations or timeboxes. This is because, as the work progresses, the team's understanding of the product grows, and they are better equipped to define detailed acceptance criteria that align closely with the customer's needs and the project's evolving context. It's a collaborative and iterative process, allowing for greater precision in defining what will make a particular feature or requirement acceptable.



View Related Case Study

Answer the following questions about the acceptance criteria within the project.

Decide whether the approach to setting and using acceptance criteria has been applied appropriately and select the response that supports your decision.

During Solution Development Timebox A, a new Health and Safety requirement arises: the front door is required to have wheelchair access. This is a legal requirement and is a Must Have before any staff or general public access can be allowed. The Solution Development Team will work with the Local Planning Authority Officer, the specialist who identified the requirement, to identify further acceptance criteria for Solution Development Timebox A.

Is this an appropriate action related to acceptance criteria?

  1. Yes, because the new requirement needs to be understood, built and delivered in this Timebox.
  2. Yes, because the Local Planning Authority Officer owns the justification for the new requirement.
  3. No, because this new requirement would NOT be included in the original Prioritised Requirements List and therefore does NOT need acceptance criteria to be defined.
  4. No, because the Business Visionary is responsible for defining acceptance criteria.

Answer(s): A

Explanation:

A: Yes, because the new requirement needs to be understood, built and delivered in this Timebox.
Rationale:
Agile Project Management is adaptable to changes, even late in the development process. The introduction of a new Health and Safety requirement, such as wheelchair access, which is a legal and must-have requirement, needs to be incorporated into the project as soon as it is identified. Working with the Local Planning Authority Officer to define acceptance criteria ensures that the requirement is clearly understood and that the solution developed meets the necessary legal standards. This approach ensures that the team can immediately address the new requirement and integrate it into the current work cycle, aligning with Agile's principle of welcoming changing requirements, even late in development, for the customer's competitive advantage.



View Related Case Study

Answer the following questions about the acceptance criteria within the project.

Decide whether the approach to setting and using acceptance criteria has been applied appropriately and select the response that supports your decision.

The requirement to 'install a heat reclamation system' shows as a Should Have in the Prioritised Requirements List. During Investigation in Solution Development Timebox B, the Project Manager advised the team NOT to set detailed acceptance criteria for this requirement until later in the Timebox, since the requirement may have to be dropped and the work would be wasted.

Is this an appropriate action related to acceptance criteria?

  1. Yes, because only Must Have requirements should be fully understood.
  2. Yes, because the acceptance criteria might need to be changed during the Solution Development Timebox.
  3. No, because it is necessary to understand the full detail of all the work for completion in the Solution Development Timebox during Investigation.
  4. No, because it indicates that the Solution Development Team has NO intention of delivering the Should Have requirements.

Answer(s): B

Explanation:

B: Yes, because the acceptance criteria might need to be changed during the Solution Development

Timebox.
Rationale:
In Agile Project Management, flexibility is key. It is important to prioritize work based on the value it provides and the necessity of the requirement. "Should Have" requirements are important but not critical, and they can be subject to change as the project progresses and as more information becomes available. Deferring the detailed setting of acceptance criteria for a "Should Have" requirement that might be dropped is a practical approach to managing workload and focusing efforts on the most critical aspects of the project first. This approach is in line with Agile's principle of responding to change over following a fixed plan.






Post your Comments and Discuss APMG-International AgilePM-Practitioner exam dumps with other Community members:

Join the AgilePM-Practitioner Discussion