CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. APMG-International
  5. AgilePM-Practitioner

Free AgilePM-Practitioner Exam Braindumps (page: 3)

Page 2 of 21
PDF with 134 Questions
View Related Case Study

Which 2 statements describe the appropriate application of Agile Project Management when developing the Prioritised Requirements List during Feasibility?

  1. Details of which areas will require seeding in order to become lawn, and which are to become planted borders, should be captured.
  2. The re-laying of the driveway and a landscaping solution should be listed as Must Have requirements.
  3. The scope of the project should be agreed before moving into the Foundations phase.
  4. The responsibility for setting the priority of each of the requirements identified should be assigned to the Project Manager.
  5. Regulatory obligations associated with the redevelopment of Hoy Hall should be recorded as Must Have requirements.

Answer(s): B,E

Explanation:

In the context of Agile Project Management when developing the Prioritised Requirements List during Feasibility, the two statements that align with Agile principles are:
B) The re-laying of the driveway and a landscaping solution should be listed as Must Have requirements.
E) Regulatory obligations associated with the redevelopment of Hoy Hall should be recorded as Must Have requirements.
Here's the rationale:
B: In Agile, requirements are often categorized by priority such as "Must Have", "Should Have", "Could Have", and "Won't Have for now" (the MoSCoW method). The re-laying of the driveway and a landscaping solution are essential for the project's success and thus should be classified as "Must Have".
E: Regulatory requirements are non-negotiable constraints that the project must adhere to. These should always be prioritized in the requirements list to ensure compliance and to avoid legal issues, making them "Must Have" items as well.



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.






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

AgilePM-Practitioner Discussions & Posts