Free APMG-International AgilePM-Practitioner Practice Exam with Questions & Answers

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.

The two statements that explain why the Architecture Angels’ Marketing Director would be an appropriate Business Visionary are:

•B. Is fully committed to changing the company’s strategic direction to include hotel renovation. This shows that the Marketing Director is aligned with the project’s goals and is invested in its success.

•E. Has a passion for old buildings and can see the potential for business opportunity. This passion and vision are key characteristics of a Business Visionary, who is responsible for guiding the project towards delivering value for the business.

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.

In the context of Agile Project Management when developing the Solution Architecture Definition (SAD), the two statements that are appropriate are:

A. Paper-based drawings are to be used for each option being considered for the building and gardens.

C. The Architecture Angels' Marketing Director can request a SAD to illustrate the achievability of complex elements of the solution.

Here's the rationale:

•A: Agile methodologies support the use of simple and understandable tools that can quickly convey ideas and be easily changed. Paper-based drawings align with this by providing a flexible and adaptable way to represent different options, which can be rapidly modified in response to feedback.

•C: It is important for the Marketing Director, who understands the market and customer needs, to request clarification on complex elements to ensure that the proposed solutions are feasible and aligned with customer expectations. This contributes to creating a solution that is viable both technically and from a business perspective.

Advise how the legislation on the transfer of data will affect the requirements and the system.

E. Business Analyst

Agree the changes needed to the corporate technical architecture with the Architecture Angels IT support team.

D. Technical Coordinator

Ensure the information security vulnerability is communicated to the AA Head Office IT Director.

A. Project Manager

Evaluate the impact of proposed security controls on the business and decide on the most suitable solution.

B. Business Sponsor

Reprioritise the requirements on the Prioritised Requirements List associated with the security issue.

C. Business Visionary

Rationale:

A Business Analyst typically has the expertise to understand and communicate how data transfer legislation impacts system requirements.

The Technical Coordinator is usually responsible for technical decisions, including those that impact the technical architecture, and would work closely with the IT support team to agree on changes.

The Project Manager should ensure that key information, such as security vulnerabilities, is communicated to senior management, in this case, the IT Director.

The Business Sponsor, who is ultimately responsible for the project from a business perspective, would evaluate the impact of security measures on the business.

The Business Visionary is often tasked with understanding the strategic view of the project requirements and would be suited to reprioritize requirements, especially those with significant implications like security issues.

C. Independent Testing

A. Collaborative Testing

B. Repeatable Testing

D. Prioritised Testing

D. Prioritised Testing

Short Comprehensive Explanation:

Independent Testing is appropriate when someone from a different department (Finance) with no involvement in the development process conducts the testing to ensure an objective view.

Collaborative Testing involves various stakeholders, in this case, the Sales Manager and the solution tester, working together to review and test a prototype, promoting early feedback and shared understanding.

Repeatable Testing is used for security testing where predefined test scripts (provided by the bank) are applied to ensure the system meets specific security standards and can be repeated as needed.

Prioritised Testing is essential when the project's stability and core functionality, such as the website's capacity to handle new features, must be confirmed before other tests are conducted to ensure the most critical aspects are addressed first.

Again, Prioritised Testing is used to ensure that the essential requirements (Must Haves and Should Haves) are tested and validated before moving on to less critical ones (Could Haves), aligning with prioritization in Agile methodologies.

References:The Agile Project Management (AgilePM®) framework and principles, as detailed in the AgilePM® Practitioner documents and learning resources, guide the application of these testing concepts within an Agile project environment. These resources emphasize the importance of iterative development, stakeholder collaboration, and prioritization of work to ensure project success and alignment with business needs. Specific references to testing approaches and their application within Agile projects can be found in the official AgilePM® handbook and practitioner-level training materials available through APMG International and affiliated training providers.