AgilePM-Practitioner Practice Questions

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.

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

A.  

C.  

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.

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.

The two items that the Workshop Facilitator should be provided with when preparing for the workshop are:

•

B.  

•

C.  

Please note that while hints and tips on how to influence and persuade others (option A), empowerment to discuss any wider project issues that may arise during the workshop (option D), and a step-by-step guide to running an effective workshop (option E) could be helpful, they are not as crucial as understanding the decision-making process and the background to the disagreement for this specific workshop.