AgilePM-Practitioner Exam Dumps - APMG-International AgilePM Questions and Answers

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.

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.

In applying Agile Project Management to the creation of an Outline Business Case in support of the Feasibility Assessment, the following two statements are most appropriate:

B. Enough description of the required refurbishment work should be provided to enable the Architecture Angels' Finance Director to decide whether the project should proceed.

Agile approaches favor providing just enough detail to make informed decisions without going into unnecessary depth at early stages. This allows for flexibility and adaptation as more information becomes available.

C. During Feasibility, potential beneficiaries of the project should be involved when the Outline Business Case for the refurbishment is created.

Agile methodologies emphasize stakeholder engagement and user involvement early and throughout the project. This ensures that the project delivers value and meets the needs of those it is intended to benefit.

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.

The two statements that explain why the Contract Architect would be an appropriate Technical Coordinator are:

B. Has good leadership skills. D. Has a good, technical understanding of the work of the other professionals engaged in the project.

Rationale:

•B: Good leadership skills are essential for a Technical Coordinator, as they must lead the technical aspects of the project, manage the work of other professionals, and ensure that all technical activities are aligned with the project goals.

•D: A deep technical understanding of the work of other professionals involved in the project is crucial for a Technical Coordinator. This knowledge allows them to effectively coordinate various technical disciplines and ensure that the technical solutions meet the project's needs.

Being an external consultant (A) or an authority on local planning applications (E) might be beneficial but do not inherently qualify someone for the role of Technical Coordinator. Previous experience with the company (C) can be helpful but is not a defining reason for suitability in the Technical Coordinator role within an Agile team.

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.

C. The Business Visionary, Business Sponsor and Solution Development Team should reassess the Prioritised Requirements List and its priorities.

Rationale:

In Agile Project Management, priorities are often reassessed and reprioritized based on new information or changes in the project's context. The need for a secondary exit due to compliance with fire safety regulations would necessitate such a reassessment. The Business Visionary and Business Sponsor, who provide the vision and funding for the project, together with the Solution Development Team, who are responsible for implementing solutions, should collaboratively review the Prioritised Requirements List to reflect this new priority. This change must be agreed upon by these key stakeholders to ensure that it aligns with the business needs and project goals.