APMG-International AgilePM-Practitioner Agile Project Management (AgilePM) Practitioner Exam Exam Practice Test

Based on the Agile Project Management roles and the responsibilities outlined for each individual in the XAN Insurance Company Web Project scenario, the following selections can be made:

Manager of Web & Digital Media - will oversee and report progress on the delivery of the overall system.Selection: H. Project ManagerExplanation: The Manager of Web & Digital Media's role of overseeing and reporting on the project's progress aligns with the responsibilities of a Project Manager in an Agile setting, who is responsible for ensuring that the project meets its objectives and is delivered on time.

Finance Director - has budgetary control and will release finance for the project subject to expected benefits.Selection: A. Business SponsorExplanation: The Finance Director's control over the budget and the decision to release funds based on the expected benefits align with the role of a Business Sponsor, who is typically responsible for the project's budget and ensuring that it delivers value to the business.

Sales Manager - will formulate design options for new business processes that do not adversely affect business as usual.Selection: B. Business AnalystExplanation: The Sales Manager's responsibility for formulating design options for new business processes mirrors the role of a Business Analyst in Agile Project Management, who works to understand the business needs, assess the impact of changes, and ensure the solution meets business requirements.

Operations Manager - oversees the design and integrity of the technical aspects of the solution.Selection: F. Technical CoordinatorExplanation: The Operations Manager's focus on the technical design and integrity of the solution corresponds to the role of a Technical Coordinator in Agile projects, who ensures that the technical aspects of the project align with the business needs and technical standards.

To effectively implement the new Must Have requirement for financial transaction functionality on the coffee shop insurance product website, the Project Manager should focus on actions that align with their role in planning, execution, and team coordination. The following actions are most appropriate for the Project Manager:

Selected Actions for the Project Manager:

B. Add the tasks required to develop the new financial transaction functionality to the Delivery Plan.

C. Update the Delivery Plan to show the new financial transaction functionality as a deliverable.

B. Integrating the tasks necessary for developing the new functionality into the Delivery Plan is crucial. This ensures that all project activities are accounted for and scheduled, which helps in managing the project's timeline and resources effectively.

C. Reflecting the new financial transaction functionality as a deliverable in the Delivery Plan is important for clarity and focus. It signifies the inclusion of this functionality as a critical component of the project's scope, guiding the team's efforts and priorities.

Why Other Actions Are Less Suitable:

A. While ensuring adherence to documented standards is important, it is typically a collaborative effort involving the Technical Coordinator and Solution Development team, in addition to the Project Manager, to ensure technical compliance.

D. Sourcing and hiring specific expertise, such as a web developer skilled in online financial transactions, is indeed part of the Project Manager's responsibilities. However, the actions related to the Delivery Plan (options B and C) are more directly aligned with the immediate steps for implementing a new requirement in the project's scope.

E. Consolidating and circulating an agenda for the workshop is a logistical task that the Project Manager might oversee or delegate. However, the actions related to planning and updating the Delivery Plan are more critical to the successful implementation of the new requirement.

Dividing the work into smaller, well-defined component parts is a strategic approach when dealing with fixed-price contracts within an Agile framework. This method allows for greater flexibility and adaptability, as each component can be specified in detail, making it clear what the external web developer is responsible for delivering. This approach aligns with Agile principles by enabling incremental development and delivery, allowing for adjustments and refinements to be made as the project progresses and more information becomes available.

References:

In Agile Project Management, particularly when incorporating external resources or contractors, breaking down the project into smaller, manageable parts is a common practice. This not only facilitates better control and tracking of progress but also ensures that the project remains adaptable, with the capacity to respond to changes in requirements or priorities. This approach is in line with Agile methodologies that emphasize iterative development, customer collaboration, and responding to change over following a fixed plan.

In the context of Agile Project Management, it is crucial to have clear commitments regarding team members' availability to ensure that project planning and execution can be as accurate and effective as possible. By securing a formal agreement on the hours the marketing assistants can dedicate to the project each week, the Project Manager can better plan tasks and allocate resources, thereby optimizing the team's capacity and ensuring that project timelines and deliverables are realistic and achievable.

References:

The Agile Project Management (AgilePM®) framework emphasizes the importance of clear communication, resource planning, and commitment from all team members to ensure project success. Having a formal agreement on availability helps in setting clear expectations and allows for more effective planning and utilization of resources within the constraints of the project, aligning with Agile principles of collaboration, adaptability, and iterative progress.

The activities from Column 1 should be performed in the following steps from Column 2, according to the iterative development process:

Create the data entry screen for entering coffee bar details needed for a quotation.Selection: B. ActionExplanation: Creating the data entry screen is part of the 'Action' step in iterative development, where the actual product or a part of it is being constructed.

Enter numbers into a text-only field to see how the web page behaves.Selection: A. ThoughtExplanation: Testing how the web page behaves by entering data is part of the 'Thought' step, which includes reviewing and evaluating the work done, testing, and reflecting on the outcomes.

Discuss the requirements of the new coffee bar insurance web page and agree which data fields are important.Selection: C. ConversationExplanation: Discussing and agreeing on the requirements is part of the 'Conversation' step, which involves interactions between team members and stakeholders to understand and define what needs to be built.

In the context of Agile Project Management when developing the Prioritised Requirements List during Feasibility, the two statements that align with Agile principles are:

B. The re-laying of the driveway and a landscaping solution should be listed as Must Have requirements.

E. Regulatory obligations associated with the redevelopment of Hoy Hall should be recorded as Must Have requirements.

Here's the rationale:

•B: In Agile, requirements are often categorized by priority such as "Must Have", "Should Have", "Could Have", and "Won't Have for now" (the MoSCoW method). The re-laying of the driveway and a landscaping solution are essential for the project's success and thus should be classified as "Must Have".

•E: Regulatory requirements are non-negotiable constraints that the project must adhere to. These should always be prioritized in the requirements list to ensure compliance and to avoid legal issues, making them "Must Have" items as well.

The two statements that explain why the Architecture Angels' Finance Director would be an appropriate Business Sponsor are:

C. Is the project budget holder. D. Is concerned about preventing the costs of refurbishment from escalating and affecting the operations of the company.

Rationale:

•C: Being the project budget holder, the Finance Director has a clear overview of the financial aspects of the project, which is crucial for the role of Business Sponsor. They are responsible for the financial governance of the project, ensuring that the project remains viable and delivers value for money.

•D: A key responsibility of a Business Sponsor is to safeguard the project from going over budget. The Finance Director's concern for preventing cost escalation is aligned with this responsibility, as they would work to balance the financial constraints with the project objectives.

Options A, B, and E do not directly relate to the role's responsibilities and do not support why the Finance Director would be suitable for the Business Sponsor role in an Agile context.

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.

The two individuals most suitable for the role of Workshop Facilitator would be:

A. Team Leader E. Project Manager

The rationale for choosing these individuals is that both the Team Leader and the Project Manager are likely to have the necessary skills to facilitate a workshop effectively. They are typically trained to manage team dynamics, guide discussions, remain neutral, and drive towards a resolution. The IT Operations Manager and the Marketing Director are parties to the disagreement and thus would not be appropriate as facilitators due to the potential for bias. The Software Developer is likely to be more involved in the technical aspects rather than facilitation.

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.

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.

B. Yes, because the acceptance criteria might need to be changed during the Solution Development Timebox.

Rationale:

In Agile Project Management, flexibility is key. It is important to prioritize work based on the value it provides and the necessity of the requirement. "Should Have" requirements are important but not critical, and they can be subject to change as the project progresses and as more information becomes available. Deferring the detailed setting of acceptance criteria for a "Should Have" requirement that might be dropped is a practical approach to managing workload and focusing efforts on the most critical aspects of the project first. This approach is in line with Agile's principle of responding to change over following a fixed plan.