Pass the APMG-International AgilePM AgilePM-Practitioner Questions and answers with ExamsMirror

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 Agile Project Management, it ' s important to involve key stakeholders and to ensure that there ' s a collaborative approach to project decisions. Considering the Agile principles and the given scenario, the appropriate application of Agile to the Feasibility Assessment would likely involve the following statements:

B. The Architecture Angels ' Finance Director should approve the final Business Case as part of the Feasibility Assessment. In Agile, it ' s crucial to ensure that the business aspect of any project aligns with the financial feasibility. The Finance Director ' s approval would be significant in validating the economic viability of the project.

D. The different options should be presented to the ' Hoy for Hoy Hall ' Action Group for their feedback before the chosen outline solution is finalised. Agile encourages stakeholder engagement and iterative feedback. Presenting options to the action group aligns with the Agile value of customer collaboration over contract negotiation, allowing for community input that could be vital due to the building ' s heritage status and the community ' s interest.

A. Yes, because this will allow the Solution Development Team to focus on the quality of the Solution Development Timebox ' s deliverable as a whole, in order to keep focus on the business need.

Rationale:

Setting acceptance criteria for the overall deliverables of a timebox is a key practice in Agile to ensure that the work meets the business objectives and quality expectations. It helps the Solution Development Team to understand what is required for the deliverables to be considered complete and acceptable. This aligns with the Agile principle of delivering quality and maintaining a constant pace of development. It also ensures that all team members are aligned on the goals and can focus on delivering value in line with business needs.

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 actions that the Workshop Facilitator should take if the team cannot agree on the system content are:

C. Facilitate the creation of a list of actions to be carried out after the workshop, to resolve the issue. This will ensure that the disagreement does not stall the project and that there is a clear plan for how to move forward.

E. Prepare a report describing the outcome of the workshop. This will provide a record of the discussion and any decisions made, which can be useful for future reference and for keeping stakeholders informed.

Please note that while presenting their own interpretation of what the system should include (option A) or presenting the group with a predefined specification of what should be included (option B) might seem like potential solutions, these actions could bias the discussion and may not lead to a solution that meets all stakeholders’ needs. Agreeing to disagree and closing the workshop (option D) could leave the issue unresolved, which could cause problems later in the project. The facilitator’s role is to guide the discussion and help the team reach a consensus, not to impose their own views or prematurely end the discussion.

The Facilitator should invite the following two individuals to participate in the Workshop:

D. IT Operations Manager (Solution Development Team) E. Marketing Director (Business Visionary)

The rationale for this selection is that the disagreement is between the Marketing Director, who wants the reservation system to have professional photos and video tours (which impacts how the system will be used by potential customers and affects marketing strategy), and the IT Operations Manager, who is concerned with the system ' s technical limitations and maintenance. Both of these individuals are key to resolving the issue at hand, as they represent the conflicting requirements that need to be reconciled for the project to move forward.

The Senior Management Team, which includes the roles of the Sales, Marketing, and Finance Directors, and the Chief Executive, is typically responsible for steering the project and making decisions that reflect the overall scope and objectives of the project. They would be the appropriate body to approve changes in the project scope as represented in the Prioritised Requirements List, especially for a requirement that has legal and safety implications, such as a secondary fire exit. This team would ensure that such a change aligns with the strategic goals and compliance requirements of the project.