AgilePM-Practitioner Sample Questions Answers

The most constructive and collaborative action the Web Content Manager should take is:

D. Discuss the issue with the Web Developer and decide what action is required to change this detail.

Direct communication and collaboration between the Web Content Manager and the Web Developer are essential in Agile environments to promptly address misunderstandings or mistakes. Discussing the issue openly allows for a quick resolution and ensures that the final product aligns with the project's requirements. This approach fosters a positive working relationship, encourages shared responsibility for the project's success, and avoids unnecessary delays or conflicts.

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.

In the context of the DSDM lifecycle, the Investigation stage of a Timebox is crucial for understanding and defining the work to be done, which often necessitates close collaboration with business representatives such as the Business Ambassador. This role is integral in ensuring that the project's outputs align with business needs and priorities. Planning the Investigation stage around the Business Ambassador's availability facilitates this essential engagement, making it a suitable application of the DSDM lifecycle. This approach ensures that the project benefits from the Business Ambassador's insights and guidance during critical early phases, contributing to a stronger alignment between project deliverables and business requirements.

References:The Agile Project Management (AgilePM®) framework, which incorporates DSDM principles, emphasizes the importance of collaboration between the project team and business stakeholders throughout the project lifecycle. The involvement of the Business Ambassador during the Investigation stage is particularly valuable for clarifying requirements, setting priorities, and ensuring that the project remains focused on delivering business value, in line with Agile and DSDM practices.

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.

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.

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.

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.

For each line, here is the appropriate option from A to E that applies:

All internal works to be assigned to Timber Tigers throughout the project should be consolidated into one Structured Timebox.

E. False (Assertion) False (Reason)

Rationale: It is not practical or in line with Agile principles to consolidate all internal works into one Structured Timebox, as the work will likely need to be spread over multiple Timeboxes. Additionally, the Investigation step involves agreeing on how to meet the requirements of the Timebox, not necessarily consolidating all work into one.

Acceptance criteria for the front rooms to be developed in Timebox A should be described in detail and agreed during the Timebox Kick-Off

B. True (Assertion) True (Reason) BUT the reason does not explain the assertion

Rationale: While it is true that acceptance criteria should be agreed upon during the Timebox Kick-Off, the reason given is incorrect because the aim of the Investigation step is not necessarily to complete as much development work as possible but to plan and understand the work that will be carried out.

It is appropriate that both the Evolutionary Development phase and Deployment phase are shown in the first Project Increment.

A. True (Assertion) True (Reason) AND the reason explains the assertion

Rationale: Each Timebox should indeed include both Evolutionary Development and a Deployment phase. This assertion and reason correctly align with the concept of Timeboxing in Agile.

It is appropriate that the outputs of Timebox C are scheduled for deployment at the end of the first Project Increment.

A. True (Assertion) True (Reason) AND the reason explains the assertion

Rationale: The typical Timebox Plan does provide a schedule of high-level activities for the imminent Project Increment, which would include planning for deployment.

It is appropriate that Earth Excavations create a detailed plan of activities they will complete during Timebox C.

C. True (Assertion) False (Reason)

Rationale: While it is true that Earth Excavations should create a detailed plan for their activities in Timebox C, the reason is incorrect as the Solution Development Team is not solely responsible for planning all work details within a Timebox. This task would typically be a collaborative effort involving all relevant parties.

A. Provision of a secondary exit from the upstairs of the building will ensure compliance with national fire safety regulations.

Rationale:

Compliance with national fire safety regulations is non-negotiable and would be a legal requirement for the operation of the hotel. Therefore, any features required to meet these regulations would automatically be classified as "Must Have" due to their mandatory nature for safety and legal operation.

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.

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.

The two actions that the Workshop Facilitator should take when preparing for the workshop are:

•A. Ask the Software Developer to provide an estimate of how much storage space would be required to hold photos and videos. This will provide a factual basis for the discussion about the system’s content and its storage requirements.

•B. Invite the Marketing Director to create a summary of the content they believe the system should hold and why. This will ensure that the Marketing Director’s perspective and requirements are clearly understood by all participants in the workshop.

Please note that while the IT Operations Manager, Software Developer, and the Facilitator themselves (options C, D, and E) could contribute valuable input to the workshop, these actions are not necessarily part of the Facilitator’s role in preparing for the workshop. The Facilitator’s role is to guide the discussion, not to assign ownership of the workshop, prepare the agenda, or form opinions on the content.

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.

Here are the appropriate options for each assertion and reason combination:

The Marketing Director, in the role of Business Visionary, is empowered to overrule cost restrictions advised by the Chief Accountant, who is appointed as Business Ambassador.

C. True (Assertion) False (Reason)

Rationale: While the Business Visionary may have the authority to make strategic decisions that could overrule cost restrictions, the reason given relates to project-level roles directing the project, not to the authority to overrule cost-related advice.

The Procurement Manager is an appropriate representative of the end user of the solution.

B. True (Assertion) True (Reason) BUT the reason does not explain the assertion

Rationale: The Procurement Manager, as part of the operational team, could represent the end user. However, the reason given talks about the empowerment of the Business Ambassador, which does not directly explain why the Procurement Manager is a representative of the end user.

The other specialist gardening team members from Earth Excavations would be suitable as Solution Developers, assigned alongside the Head Landscape Gardener.

A. True (Assertion) True (Reason) AND the reason explains the assertion

Rationale: Specialist gardening team members would be suitable as Solution Developers, providing support to the Lead Developer, which is a common practice in Agile teams.

The 'Hoy for Hoy Hall' Action Group members should be assigned as Business Ambassadors.

D. False (Assertion) True (Reason)

Rationale: While the Business Ambassador should ensure that business needs are analyzed, the 'Hoy for Hoy Hall' Action Group members being assigned as Business Ambassadors is not necessarily true as they are external stakeholders and not necessarily equipped to represent the business internally on a project.

The Project Manager should plan the communication needed between the Marketing Director, in the role of Business Visionary, and the 'Hoy for Hoy Hall' Action Group.

A. True (Assertion) True (Reason) AND the reason explains the assertion

Rationale: The Project Manager typically has the responsibility to plan and manage communication between the project team and external stakeholders, and the Business Visionary's role includes promoting the business vision to interested parties, which includes the 'Hoy for Hoy Hall' Action Group.