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

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.

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.

The initial action to deal with the lack of provision of a fire escape from the upstairs of the building in Timebox B should be:

•C. The Architect, in the role of Technical Co-ordinator, should escalate the issue to Architecture Angels’ Senior Management Team.

This is because the lack of a fire escape is a significant safety concern that could have legal and regulatory implications. It’s important that the Senior Management Team is aware of this issue so they can make informed decisions about how to address it. The Architect, in the role of Technical Co-ordinator, is well-positioned to understand the technical implications of this issue and communicate them to the Senior Management Team.

While revising the Timebox Plans (option A) or commencing understanding and delivering the new requirement (option B) could be part of the solution, these actions should be taken after the issue has been escalated and discussed with the Senior Management Team. Escalating the issue to the Marketing Director (option D) may not be the most effective course of action, as this is primarily a technical and safety issue, not a marketing one.

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

A. Paper-based drawings are to be used for each option being considered for the building and gardens.

C. The Architecture Angels' Marketing Director can request a SAD to illustrate the achievability of complex elements of the solution.

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.

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.

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.

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.

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.

For the XAN Insurance Company Web Project, the Development Approach Definition document should outline the methodologies, tools, and techniques to be used during the development process of the project. It focuses on how the project will be executed in terms of technical and management practices.

Selected Statements for the Development Approach Definition:

C. An easy to use web development tool called 'WebMatrix' is to be used to develop and maintain the website extension.

E. Accessibility and performance of the new online quotation area is to be tested using a tool called Sitebeam.

C. This statement directly specifies a tool (WebMatrix) that will be used for web development and maintenance in the project. It is a clear choice regarding the technical approach and infrastructure, making it suitable for inclusion in the Development Approach Definition.

E. Mentioning Sitebeam as a tool for testing accessibility and performance outlines specific methods for ensuring quality and usability in the development process. It provides actionable information on how testing will be conducted, fitting the criteria for the Development Approach Definition.

Why Other Statements Are Excluded:

A. Introducing an awards or bonus scheme to create competition among sales assistants pertains more to internal sales team management and motivation strategies rather than the technical or methodological approach to developing the project.

B. Comparing traditional telephone sales with online sales is related to the project's performance measurement and post-implementation review, not the development approach or methodology used during the project.

D. The request from the Finance Director for a detailed cost report is related to project financial management and monitoring. While important, it does not detail the technical or methodological approach to developing the project's deliverables.

The most effective action the Project Manager should take to ensure effective communication throughout the Web project at Xan Insurance Company is:

A. Identify those individuals with power and influence over the project and what information they require.

In any project, especially within an Agile framework, understanding the stakeholders' landscape is crucial for effective communication management. Identifying key individuals with power and influence over the project helps tailor communication strategies to ensure that critical information is shared appropriately, decisions are facilitated efficiently, and stakeholder engagement is maintained. While the company's culture of informal communication can be advantageous for day-to-day interactions, structured communication is essential for project governance, risk management, and decision-making processes. This approach allows the Project Manager to ensure that all stakeholders are kept informed according to their needs and the project's requirements, balancing the informal communication culture with the need for formal communication where necessary.

The most effective action the Project Manager can suggest to ensure the most effective collaboration of the Solution Development Team is:

C. Relocate these employees to a new project area, with a number of desks where the Solution Development Team can sit together.

Co-locating team members in a shared space is a well-established practice in Agile environments to enhance communication, collaboration, and team dynamics. By having the Solution Development Team sit together, the Project Manager can facilitate more efficient face-to-face interactions, quick resolution of issues, and a better sense of team unity. This approach leverages the benefits of immediate communication and collaborative problem-solving, which are key in Agile project management. Even though the team members are currently in the same office, their separation into different ends of the office could hinder spontaneous communication and collaboration. Creating a dedicated project area for the team can significantly improve their ability to work together effectively.

For the XAN Insurance Company Web Project and considering the Agile Project Management approach, particularly the Dynamic Systems Development Method (DSDM) framework which emphasizes business value and active user involvement, the Business Case should justify the project in terms of cost, benefit, and risk.

Selected Statements for the Business Case:

D. The Sales Manager has calculated that the new coffee shop insurance product will increase revenues by 10% each week.

E. Market research shows that the number of coffee shop patrons taking legal action against retailers has increased by 200% over the past two years.

D. This statement provides a clear financial projection for the benefits of the project, which is a critical component of a Business Case. It quantifies the expected revenue increase, offering a tangible benefit to justify the project investment.

E. This statement outlines a market trend that necessitates the project, highlighting the increased demand for insurance due to rising legal actions against coffee shops. It underscores the relevance and timeliness of the project, adding to the justification for undertaking the project.

Why Other Statements Are Excluded:

A. While high-level functional and non-functional requirements are essential for project planning, they typically belong in project requirements documentation or the Project Brief, rather than the Business Case.

B. This statement provides market insight but does not directly justify the project from a cost-benefit-risk perspective. The relevance of selling Fairtrade products and alcohol to the insurance product project is tangential.

C. The request for a report on past sales provides background information but does not in itself justify the project investment. It might be used to inform the Business Case but is not a direct component of it.

To lead the Solution Development Team effectively during the first Structured Timebox, the Project Manager should:

C. Attend the Daily Stand-up and discuss any problems at the end.

Attending the Daily Stand-up meetings allows the Project Manager to stay informed about the team's progress, challenges, and any blockers they might be facing. It offers an opportunity for the Project Manager to provide support, guidance, and decision-making where necessary, without disrupting the team's autonomy and self-organization. This approach encourages open communication, quick resolution of issues, and maintains the Agile principle of collaboration and continuous improvement. Discussing problems at the end of the meeting ensures that any issues are addressed promptly, keeping the Timebox on track.

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.

For the XAN Insurance Company Web Project, the plan for Post-Project activities should include actions and measures that will be undertaken after the project's deliverables have been implemented to ensure sustained benefits, monitor performance, and facilitate continuous improvement.

Selected Statements for the Plan for Post-Project Activities:

D. A report showing the number of application forms completed online through the website for coffee shop insurance policies will be produced weekly.

E. Once the new system has been deployed, the time it takes to process sales online will be compared with the time it takes to process new policies sold through telephone sales.

D. Producing a weekly report on the number of application forms completed online is a clear post-project activity. It provides ongoing monitoring of the project's impact and the effectiveness of the online system in attracting coffee shop insurance policies.

E. Comparing the processing times of online sales to telephone sales after the new system's deployment is an essential post-project activity. It evaluates the efficiency and effectiveness of the new online system, offering insights into improvements and adjustments that may be needed.

Why Other Statements Are Excluded:

A. Creating a company-wide email to show the number of policies sold by each sales assistant weekly is more related to internal sales performance monitoring and motivation rather than a specific post-project activity tied to the project's objectives.

B. Circulating a copy of the revised sales procedure before product deployment is a preparation step for the transition to the new system, rather than a post-project activity.

C. The Project Manager attending Daily Stand-up meetings is part of the ongoing project management and team coordination activities during the project, not a post-project activity.

The most effective action the Project Manager should take to resolve the 'them and us' culture between the Sales Department and the Operations Department is:

B. Brief the team and the Business Visionary on the use of an Agile Project Management approach and the requirement to collaborate.

Addressing the cultural divide requires fostering an environment of collaboration and mutual respect. By educating all team members and the Business Visionary about Agile Project Management principles, which emphasize teamwork, collaboration, and collective ownership of project outcomes, the Project Manager can help shift the team's mindset towards a more unified approach. This briefing should highlight the value of diverse perspectives and the importance of working together towards common goals, thus addressing the underlying issues contributing to the 'them and us' culture. Encouraging open communication and collaboration as fundamental components of the Agile approach can help break down barriers and build a more cohesive team.