Pearson AgilePM-Practitioner New Attempt

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.

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.