AgilePM-Practitioner Agile Project Management (AgilePM) Practitioner Exam Questions and Answers

Comprehensive and Detailed Step-by-Step Explanation

Understanding Empathy Mapping

An empathy map is a tool used to understand the feelings, concerns, motivations, and perceptions of individuals or groups impacted by change. It focuses on what stakeholders:

Think and feel: Emotional concerns or motivations.

Hear: Feedback from others.

See: Observations in their environment.

Say and do: Observable actions or behaviors.

Empathy maps help uncover concerns or barriers that might affect engagement or alignment with change initiatives.

Option Analysis (UniCo-Specific)

A. Concerns raised by the Promotions Team Leader about reduced sales

Empathy maps are designed to capture emotional and practical concerns of individuals or teams. In this case, the concerns raised by the staff about sales reductions during seasonal promotions align perfectly with the " Think and Feel " dimension of empathy mapping.

This information helps the Marketing team identify and address emotional or motivational barriers to the change.

Correct.

B. Visual diagram of potential stakeholders with symbolic figures

While visualizing stakeholders on a diagram is a useful exercise, it relates more to stakeholder mapping (e.g., influence-interest grids) than to empathy mapping. This activity does not address the emotional or perceptual aspects that empathy mapping focuses on.

Incorrect.

C. A list of stakeholders made by the Marketing analysts

Creating a list of stakeholders and sharing it in a meeting is another stakeholder analysis activity. However, this process does not delve into the emotions, perceptions, or motivations of the marketing staff, which is the purpose of an empathy map.

Incorrect.

D. Comparing lists of stakeholders during a Brand Team meeting

This activity relates to collaborative stakeholder identification and analysis but does not involve capturing the emotional or perceptual data required for empathy mapping.

Incorrect.

Why A is the Correct Answer (Scenario Alignment)

The Promotions Team Leader’s insights directly reflect the type of emotional and motivational data required for an empathy map. This information can help address staff concerns, ensuring the marketing staff are supported and aligned with the change.

References (UniCo Scenario and AgilePM Alignment):

UniCo Scenario: Marketing staff concerns about sales impact align with emotional mapping needs.

AgilePM Handbook, Chapter 7: Stakeholder Engagement and Empathy Mapping Tools.

Agile Business Consortium – Empathy Map Use for Change Management.

Comprehensive and Detailed Step-by-Step Explanation:

Understanding Stakeholder Segmentation in Agile Project Management

Stakeholders are segmented based on their level of influence, interest, and involvement in the project. The ' primary ' segment consists of stakeholders who are directly impacted by the project’s outcomes or who have the highest influence over its success.

The primary stakeholders often have the power to determine project requirements or outcomes and require significant attention from the project team.

Option Analysis

A. Industry-related professional associations

While their opinions influence industry trends, they are not directly involved in UniCo ' s project or operational terms. They fall under the secondary segment as their influence is indirect and focuses on broader trends rather than specific deliverables.

Incorrect.

B. The Utilities company

The Utilities company is UniCo’s customer, directly dictating specific requirements and operational terms. As such, they hold significant influence and impact on the project’s success. They represent a key stakeholder group in the primary segment, as satisfying their requirements is essential for UniCo’s strategic goals.

Correct.

C. The Operations Director

The Operations Director is an internal stakeholder involved in decision-making and execution. While they play a crucial role, they are part of the project delivery team rather than an external primary stakeholder. Therefore, they do not belong in the ' primary ' segment.

Incorrect.

D. The UniCo investors

Investors are critical for funding and overall company strategy but are not directly involved in defining project requirements or operational terms for this specific initiative. They fall under the key supporting stakeholders rather than the ' primary ' segment.

Incorrect.

Why B is the Correct Answer

The Utilities company directly dictates project requirements and operational terms. Their satisfaction is crucial for the project ' s success and aligns with Agile principles emphasizing delivering value to the customer . This makes them a part of the ' primary ' stakeholder segment.

Comprehensive and Detailed Step-by-Step Explanation

The Applications Manager is already heavily engaged in other responsibilities, which makes it challenging for them to take on additional duties as a change agent. To make their role effective without overburdening them, it is important to redistribute tasks or provide support to alleviate their workload.

1. Why B (Appoint a Junior Team Member with Support) is Correct

Delegation with Oversight: Appointing a junior team member as a change agent allows the Applications Manager to provide strategic guidance while the junior team member handles operational-level responsibilities.

Efficient Use of Time: This approach ensures the Applications Manager’s expertise is still leveraged without compromising their ability to fulfill other critical responsibilities.

Encourages Team Development: By empowering a junior team member, the department builds capacity and fosters a culture of shared responsibility.

Fits Agile Principles: Agile encourages collaboration and distributed leadership, which aligns with assigning a junior member with oversight from the Applications Manager.

2. Analysis of Incorrect Options

Option A (Anonymous Complaints System):

While useful for surfacing concerns, this does not address the Applications Manager ' s workload or their ability to be effective in the change agent role.

Eliminate.

Option C (Train in Time Management):

Time management training is not a practical solution in this context, as it does not reduce the workload or provide additional resources for the Applications Manager.

Eliminate.

Option D (Publish Timetable):

Publishing a timetable may clarify objectives for the team but does not directly address the Applications Manager’s capacity or ability to fulfill the role.

Eliminate.

3. Practical Implications of Selecting Option B

Improves Effectiveness: By providing a support structure (a junior team member), the department ensures that change-related tasks are handled without compromising other responsibilities.

Promotes Collaboration: This solution emphasizes teamwork and accountability, which is critical in change initiatives.

Comprehensive and Detailed Step-by-Step Explanation:

Context from the UniCo Scenario:

The Sales staff feel their working environment is being disrupted due to the integration of Selco staff. The loss of their relaxation area has led to discontent and potential escalation through their Union. Addressing this resistance requires creating opportunities for engagement, collaboration, and exploring alternatives to ensure both parties feel valued in the change process.

Analysis of Each Option:

A. Arrange joint workshops for Sales and Selco staff to develop ideas and comment on layout options.

Why Correct: Joint workshops encourage collaboration and allow both Sales and Selco staff to voice their concerns and contribute to finding a mutually beneficial solution. This action aligns with AgilePM’s focus on building engagement and transparency in managing resistance.

B. Delay information on the impact of the Selco relocation on Sales staff until just before the relocation move occurs.

Why Incorrect: Withholding information undermines transparency, erodes trust, and increases resistance. AgilePM promotes early communication and engagement to prevent escalation of issues.

C. Exert pressure on the Sales management team to make sure any resistance is kept ‘quiet’.

Why Incorrect: Suppressing resistance is counterproductive and creates further mistrust. AgilePM encourages open dialogue to address resistance constructively rather than avoiding or silencing it.

D. Provide a farewell gathering in the relaxation area to enable staff to remember past stories about the area.

Why Incorrect: While this action acknowledges staff sentiment, it does not address the root cause of resistance or provide a tangible solution to the problem. AgilePM emphasizes taking practical steps to remove barriers to acceptance .

E. Organize a Sales discussion group to look at alternative relaxation facilities that could be provided to the Sales staff.

Why Correct: A discussion group allows Sales staff to explore alternative solutions collaboratively. It helps them feel involved and valued in the process, reducing resistance and aligning with AgilePM’s principle of stakeholder engagement .

Why A and E Are Correct:

Workshops (A):

Promote collaboration and shared ownership of the solution, reducing conflict and building trust between Sales and Selco staff.

Discussion Groups (E):

Provide an avenue for Sales staff to voice their concerns and explore practical alternatives, demonstrating that their input is valued.

References to AgilePM Framework:

Stakeholder Engagement and Transparency:

Encouraging open dialogue and shared decision-making reduces resistance. (AgilePM Practitioner Guide, Chapter 8: Stakeholder Engagement)

Collaborative Problem-Solving:

Using workshops and discussion groups aligns with AgilePM’s focus on fostering collaboration and trust during change. (AgilePM Practitioner Guide, Chapter 6: Facilitating Change)

Addressing Resistance:

AgilePM emphasizes understanding the root causes of resistance and actively involving stakeholders in solutions. (AgilePM Practitioner Guide, Chapter 10: Preparing for Change)

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.

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.

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.

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.

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.

Comprehensive and Detailed Step-by-Step Explanation

When inducting change agents into a change programme, it is critical to provide them with the information that will directly support their role in facilitating the specific workstream. The Operational delivery processes workstream is focused on integrating technical systems and processes , making it essential for change agents to understand the new expectations and ways of working that will arise from this integration.

1. Why A (Expected New Ways of Working) is Correct

Relevant to the Workstream: This information is directly related to the changes being implemented, such as process integration, operational alignment, and technical system modifications.

Preparation of Change Agents: Change agents must understand the new ways of working to effectively communicate, advocate for, and facilitate the changes among their teams.

Focus on Operational Changes: Since this workstream involves technical delivery processes, equipping change agents with relevant knowledge ensures they are aligned with the workstream ' s objectives.

2. Analysis of Incorrect Options

Option B (Staff Contact Details):

While useful for logistical purposes, this information is not directly linked to the change programme ' s objectives or the responsibilities of change agents in driving operational changes.

Eliminate.

Option C (Staff Satisfaction Survey Results):

Staff satisfaction data is more relevant for monitoring cultural and engagement-related impacts rather than guiding operational delivery process changes.

It does not provide actionable insights for the change agents in this specific workstream.

Eliminate.

Option D (Portfolio, Programme, and Project Management Office Service Catalogue):

This information is related to overall project management frameworks and tools but does not offer specific guidance for the change agents tasked with facilitating operational delivery changes.

Eliminate.

3. Practical Implications

Equipping Change Agents: Providing detailed insights into expected new ways of working ensures that the change agents can address potential resistance, clarify expectations, and serve as knowledgeable advocates for the change.

Alignment with Strategic Goals: By focusing on the technical delivery processes, the induction program helps ensure that change agents are aligned with UniCo’s broader strategy of integrating Selco and delivering innovative solutions.

Comprehensive and Detailed Step-by-Step Explanation

A Change Agent plays a pivotal role in ensuring the success of a change initiative. Their responsibilities typically include fostering collaboration, addressing resistance, and facilitating the implementation of the change. The IT Support Manager is a suitable choice for this role because of their network across the organization and their ability to connect different leaders and departments.

1. Why B (Bringing Leaders Together) is Correct

The IT Support Manager, through their role, is positioned to work across multiple departments.

They are likely familiar with similar challenges faced by other line leaders due to their experience in supporting IT systems and processes organization-wide.

This ability to act as a connector between leaders makes them well-suited to facilitate collaboration and ensure alignment across the organization during the change initiative.

2. Why C (Strong Network Organization-Wide) is Correct

By supporting staff at all levels of the organization , the IT Support Manager has built a robust network.

This network enables them to influence and communicate effectively with individuals across various teams, which is crucial for overcoming resistance and promoting the change program.

Their established relationships can also help them gather feedback and identify concerns early, making them an effective change agent.

3. Analysis of Incorrect Options

Option A:

Quietly implementing directions without challenging decisions does not align with the proactive and collaborative nature of a change agent’s role. Change agents must actively engage with stakeholders and advocate for the change, rather than passively implementing instructions.

Eliminate.

Option D:

While direct authority can be useful, the change agent’s role is more focused on influence and collaboration across the organization, rather than control over specific teams.

The IT Support Manager’s authority over IT staff is secondary to their ability to work across organizational boundaries.

Eliminate.

Option E:

Wanting to gain experience in change management is not a key qualification for being a change agent. The role requires demonstrated skills in influence, collaboration, and facilitating change rather than a desire to learn.

Eliminate.

4. Practical Implications

A strong network and the ability to connect leaders are critical for fostering alignment during a change program.

The IT Support Manager’s role and experience position them to address cross-departmental challenges and encourage collaboration, making them an ideal choice for the change agent role.

Comprehensive and Detailed Step-by-Step Explanation:

This question focuses on the certainty domain within David Rock’s SCARF framework. Certainty relates to an individual’s need for predictability and clarity in their environment. When staff face ambiguity or potential disruption, addressing concerns quickly and transparently helps restore certainty.

1. Why Certainty is Important

Certainty provides stability and allows individuals to plan and operate without stress caused by ambiguity or unpredictability.

In the context of the office move, Selco staff were concerned about their desk allocations, specifically access to natural light, which introduced uncertainty.

2. Why the Leadership Team’s Actions Address Certainty

By promptly holding a workshop to address the issue, the leadership team acted transparently and showed responsiveness.

Allocating the problematic desks as hot-desks ensures that no one is permanently affected, thus providing a solution that reduces ambiguity and restores a sense of predictability.

This aligns with the SCARF framework’s principle that certainty is rewarded by prompt and open resolution of concerns.

3. Analysis of Each Option

Option A: No, because a change solution needs to be permanent to achieve ‘certainty.’

While permanent solutions can provide certainty, the key here is the prompt and transparent resolution of staff concerns, which addresses the immediate need for certainty. A permanent solution is not always required.

Eliminate.

Option B: No, because the resolution of the issue should be delegated to those affected.

Delegating resolution to staff is not necessary to address certainty. What matters is that the leadership team resolved the issue quickly and transparently.

Eliminate.

Option C: Yes, because loss of ‘certainty’ mostly affects those at lower organizational levels.

While uncertainty can indeed affect individuals at all levels, especially lower levels, the answer does not fully explain why the leadership’s actions are appropriate for addressing certainty.

Eliminate.

Option D: Yes, because ‘certainty’ is rewarded when issues can be resolved promptly and openly.

Correct. Certainty is reinforced when concerns are addressed promptly and in an open manner. The workshop provided transparency and resolved the ambiguity around desk allocations.

Correct Answer.

4. Practical Implications

For change management, addressing concerns quickly and clearly shows responsiveness, which can reduce resistance to change and foster trust.

Resolving ambiguity, as the relocation team did, minimizes the disruption caused by the perceived lack of certainty.

5. Reference to SCARF Framework

Certainty: Certainty is about predictability and reducing ambiguity in the environment. Prompt and transparent actions help restore this domain and motivate individuals.

Comprehensive and Detailed Explanation:

This question refers to Gagné ' s Nine Events of Instruction, a model for designing effective learning activities. One of the steps in this model is to activate learners ' prior knowledge, which serves as a foundation for new learning. Here ' s why C is the best answer:

1. Activating Prior Knowledge in Gagné’s Model:

In Gagné’s Nine Events of Instruction, reminding learners of related knowledge or skills is part of the event “Stimulating recall of prior learning.”

This step is crucial as it helps learners connect what they already know to the new content, making the learning process smoother and more meaningful.

2. Why Option C is Correct:

Reminding learners of related knowledge or skills increases their understanding of what the new learning will enable them to do by providing context and relevance.

It helps bridge the gap between existing knowledge and new concepts, allowing learners to see the practical value and application of the new material.

3. Analysis of Other Options:

Option A: Enables learners to understand how they learn.

While activating prior knowledge might give some insight into learning processes, this is not the primary reason for reminding learners of what they already know.

Option B: Helps learners plan to use immediately what they learn.

Planning for immediate application is a valid outcome of effective learning but not the primary reason for recalling prior knowledge.

Option D: Reduces learners’ concerns about new learning.

While recalling prior knowledge may ease anxiety, this is not the main purpose in Gagné’s model. The focus is on understanding and connecting prior knowledge to new concepts.

4. Practical Example:

If a learner is being introduced to a new software tool, reminding them of their previous experience with similar tools helps them relate to the new content and understand how the new tool will expand their capabilities.

5. Reference to Gagné’s Model:

Event 3: Stimulate Recall of Prior Learning

This step facilitates the integration of prior knowledge with new material, which enhances comprehension and retention.

Comprehensive and Detailed Step-by-Step Explanation

Selecting the most engaged line leaders requires identifying those who are actively participating in or contributing to the change program. The actions taken by the Sales Team Leaders (TLs) reveal their level of involvement, commitment, and influence in the implementation of the change initiative.

1. Why A (Sales Reporting TL) is Correct

Access to confidential figures used to justify the Selco acquisition demonstrates trust and engagement in the program.

This involvement indicates that the Sales Reporting TL is both informed and influential in driving the change initiative forward.

2. Why E (North Region TL) is Correct

By raising concerns about the change approach and seeing their feedback applied, the North Region TL has demonstrated active engagement in the process.

Their concerns and subsequent actions show they are not only participating but also influencing the direction of the change initiative, making them a key contributor.

3. Analysis of Incorrect Options

Option B (Large Systems TL):

Being scheduled to become involved later suggests that they are not currently engaged in the implementation of the program.

Eliminate.

Option C (Finance Systems TL):

Delegating responsibility to a team member indicates a lack of direct engagement in the change program. A key change leader should be actively involved, not represented by others.

Eliminate.

Option D (South Region TL):

Advocating for maintaining a focus on Large Systems indicates resistance to the new direction, which is centered around mobile applications. This lack of alignment with the change goals makes them less suitable as a key change leader.

Eliminate.

4. Practical Implications

Engaged leaders like the Sales Reporting TL (A) and the North Region TL (E) can act as role models and advocates for the change program, ensuring alignment and addressing resistance within their teams.

Their actions demonstrate a balance of participation, influence, and commitment, which is essential for driving the change initiative successfully.

Comprehensive and Detailed Step-by-Step Explanation:

When identifying a statement under the High-level change approach heading, it is essential to focus on strategies or methods that outline how the organization plans to execute the change initiative.

1. Key Elements of a " High-Level Change Approach " :

A high-level change approach provides a broad overview of how the organization intends to implement and guide the change.

It typically involves strategic actions, leadership initiatives, and examples of how similar challenges have been overcome, serving as guiding principles for the change initiative.

2. Option Analysis:

Option A: Existing UniCo staff only have skills in providing the installation of large-scale computer systems.

This statement identifies a current limitation in staff capability. While it is relevant to the context of the change, it does not describe an approach or methodology for driving the change.

Eliminate.

Option B: Fast-track training of the Sales staff means taking a member of staff away from the sales operational work.

This statement highlights a logistical issue related to training but does not reflect an overarching change approach. It focuses on operational impact rather than the strategic method of driving change.

Eliminate.

Option C: The senior management will be asked to share examples of other companies undertaking, and successfully overcoming, similar challenges.

This statement describes a strategic element of the change approach. Leveraging examples from similar challenges provides a learning framework and aligns with the Agile principle of " learning from experience. " It represents a high-level strategy to guide the change process.

Correct Answer.

Option D: All four Change Initiative elements will be required to produce a monthly formal report for the CEO.

This statement outlines a reporting requirement rather than a strategic or high-level approach. While reporting is a necessary part of governance, it does not describe a method for driving change.

Eliminate.

3. Relevance in UniCo’s Scenario:

Sharing examples of other companies ' successes aligns with the need for strategic leadership and provides inspiration for overcoming challenges.

In UniCo’s case, senior management can use these examples to drive cultural acceptance of change and adapt proven strategies to their specific context.

4. Agile Practitioner Documentation References:

Leadership in Change Management: Agile principles emphasize the role of leadership in providing strategic guidance and leveraging external examples to inform decisions.

Continuous Learning: The Agile approach encourages learning from previous experiences and external examples to refine strategies for successful change implementation.

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 Hay-McBer six dimensions of organizational climate provide a framework for analyzing and improving work environments. The six dimensions are:

Clarity: Employees understand their roles, goals, and the direction of the organization.

Responsibility: Employees feel empowered to make decisions and take ownership of their work.

Standards: There is a focus on high-performance expectations.

Rewards: Contributions are recognized and rewarded.

Flexibility: Employees feel that the organization is adaptable and open to new ideas.

Commitment: Employees feel a strong sense of belonging and loyalty to the organization.

1. Joint Meetings to Discuss UniCo’s Strategic Focus (Clarity)

Reason: These meetings aim to communicate the organization’s strategic direction, providing employees with a clear understanding of goals and expectations.

This directly improves clarity , as employees gain insight into the company’s vision and how their roles align with it.

2. Internal Marketing Campaign on New Contract (Rewards)

Reason: Highlighting the success of the new contract through an internal campaign boosts employee pride and morale. This is a form of recognition, aligning with the rewards dimension.

Employees feel their contributions are acknowledged and celebrated, motivating further engagement.

3. Shared Leadership Workshops for Decision-Making (Responsibility)

Reason: Empowering staff by delegating decision-making responsibilities enhances their sense of ownership and accountability.

This supports the responsibility dimension, as it shifts decision-making closer to those executing the work, increasing engagement and confidence.

4. Engaging Staff to Define Service Levels (Flexibility)

Reason: Involving staff in shaping service levels fosters adaptability and innovation. This shows the organization values employee input, improving flexibility by encouraging open-mindedness and collaboration.

Summary of Dimensions Applied

The recommendations align with specific dimensions to address identified gaps in organizational climate, improving overall engagement and performance:

Clarity: Joint meetings to communicate strategy.

Rewards: Internal campaigns celebrating achievements.

Responsibility: Delegating decision-making through leadership workshops.

Flexibility: Involving staff in defining processes.

To implement the new Must Have requirement for the coffee shop insurance product website with financial transaction functionality, the Business Visionary should focus on actions that align with their role in guiding the project ' s vision and ensuring it meets business needs. The following actions are most appropriate for the Business Visionary:

Selected Actions for the Business Visionary:

A. Send a company-wide communication to explain the implications of the business change to all interested parties.

D. Ensure the marketing and sales teams are working together to deliver the most effective outcome.

A. As a Business Visionary, communicating the implications of significant business changes, such as the introduction of a new financial transaction functionality, is crucial. This helps in aligning all parts of the organization with the project ' s objectives and the strategic direction, ensuring everyone understands the change and its benefits.

D. The Business Visionary plays a key role in ensuring that different departments, such as marketing and sales, collaborate effectively to support the project ' s objectives. By ensuring these teams work together, the Business Visionary helps in maximizing the project ' s impact and effectiveness in meeting business goals.

Why Other Actions Are Less Suitable:

B. Assessing the impact of new requirements on the Business Case is important, but it ' s typically a responsibility shared with the Business Sponsor, who has a more direct role in managing the project ' s financial and strategic alignment.

C. Sourcing and hiring technical expertise is generally a task for the Project Manager or technical leads. The Business Visionary ' s role is more focused on strategic oversight rather than operational tasks.

E. Organizing and managing workshop details, such as circulating an agenda, might be supported by the Business Visionary, but it ' s often a task handled by the Project Manager or a designated coordinator to ensure efficient planning and execution of project activities.

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 Manager Explanation : 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 Sponsor Explanation : 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 Analyst Explanation : 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 Coordinator Explanation : 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.

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.

To implement the new Must Have requirement for financial transaction functionality on the coffee shop insurance product website, the Technical Coordinator should focus on actions that align with their role in overseeing the technical aspects of the project. The following actions are most appropriate for the Technical Coordinator:

Selected Actions for the Technical Coordinator:

A. Ensure that the latest version of the website design in the Solution Architecture Definition is provided to all members of the Solution Development Team.

E. Check for any documented standards which need to be applied to the development of online financial transaction functionality.

A. It ' s crucial for the Technical Coordinator to ensure that the Solution Development Team has access to the most current website design specifications, especially when new functionalities are being added. This ensures consistency and alignment with the overall solution architecture, facilitating effective and efficient development.

E. The Technical Coordinator is responsible for ensuring that all technical aspects of the project adhere to relevant standards, including those related to online financial transactions. This involves identifying, understanding, and applying any necessary regulatory, security, and technical standards to the development process, ensuring compliance and functionality.

Why Other Actions Are Less Suitable:

B. Assessing the impact on the original Business Case is typically the responsibility of the Business Sponsor or Project Manager, as it involves financial and strategic considerations beyond the Technical Coordinator ' s primary focus.

C. Adding tasks to the Timebox Plan is generally a responsibility shared between the Project Manager and the Solution Development Team, with the Technical Coordinator providing input on technical feasibility and requirements.

D. Consolidating and circulating an agenda for the workshop is an important logistical task but may not directly fall under the Technical Coordinator ' s responsibilities. This task is often handled by the Project Manager or a designated administrative role.

To implement the new Must Have requirement for the coffee shop insurance product website, which includes financial transaction functionality, the Business Sponsor should take the following actions:

Selected Actions for the Business Sponsor:

B. Check the viability of the project, following the inclusion of the new Must Have requirement.

E. Assess the impact of the new Must Have requirement on the original Business Case.

B. Evaluating the project ' s viability after adding a significant new requirement is crucial. This involves analyzing whether the project can still meet its objectives within the given constraints, such as time, budget, and resources, especially when the new requirement could potentially add complexity and cost.

E. Understanding how the new requirement affects the original Business Case is essential. This involves reassessing the project ' s expected benefits, costs, and risks in light of the new functionality. It ensures that the project remains aligned with business objectives and continues to offer a viable return on investment.

Why Other Actions Are Less Suitable:

A. While ensuring adherence to relevant standards is important, it is more of a task for the technical team or a specific role such as the Technical Coordinator, rather than the primary responsibility of the Business Sponsor.

C. Sourcing and hiring specific technical expertise, such as a web developer with experience in online financial transactions, is generally a responsibility delegated to the Project Manager or relevant technical leads, not the Business Sponsor directly.

D. While communicating business changes to all interested parties is important, the specific action of explaining the implications of the business change company-wide is more likely to be a collaborative effort involving several roles, including the Business Change Manager, rather than solely the Business Sponsor ' s responsibility.

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.

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.

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.

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.

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.

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 stakehold ers, and the Business Visionary ' s role includes promoting the business vision to interested parties, which includes the ' Hoy for Hoy Hall ' Action Group.

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.

The correct answers are B and C .

During the Foundations phase in AgilePM, the goal is not to fully specify everything in exhaustive detail. Instead, the aim is to establish enough shared understanding, scope, priorities, feasibility, and estimating confidence so the project can proceed sensibly.

Why B is correct

“Host a stakeholder workshop to prioritize integrating the Spa into the resort experience.”

This is strongly aligned with AgilePM because Foundations emphasizes:

collaboration,

shared understanding,

business engagement,

and early prioritization.

A stakeholder workshop helps clarify what matters most, align the increment with the business vision, and ensure the work is focused on delivering value.

Why C is correct

“Develop high-level estimates of effort and cost for Spa facilities and IT systems.”

This also aligns well with AgilePM. In Foundations, estimates should be:

useful,

proportionate,

and appropriate to the current level of knowledge.

High-level estimates are exactly what AgilePM expects at this stage. They help planning and viability assessment without pretending to offer premature precision.

Why the other options are not the best answers

A is incorrect because it pushes toward a fixed, fully analyzed specification, which is not AgilePM’s approach.

D may be useful in a general sense, but it is not as directly aligned with defining and estimating work as B and C.

E is too detailed for Foundations. Work should be defined enough to begin sensibly, but not fully elaborated into detailed design-ready form across everything.

So the best answers are B, C .

The correct answer is D .

The question asks for an artifact that can provide an auditable record of compliance requirements throughout the increment . The best fit is the Solution Architecture Definition , because it captures the solution-level decisions, constraints, and technical considerations needed to ensure the product remains compliant.

Why D is correct:

Compliance requirements often affect architecture, design constraints, and technical decisions.

The Solution Architecture Definition is the most suitable place to maintain that traceable record.

It supports evidence, consistency, and solution-level control across the increment.

Why the other options are weaker:

A is more about governance structure and responsibilities than the compliance requirements themselves.

B is retrospective and too late to serve as the ongoing auditable record.

C records what was reviewed and delivered in Sprints, but it is not the primary artifact for maintaining the compliance requirements baseline.

So the appropriate AgilePM response is D .

The correct answer is A .

In AgilePM, stakeholder engagement is a core success factor. When an important business stakeholder such as Lee Tan , acting as a Business Advisor , is disengaged from review events and then complains about lack of visibility, the right response is not to bypass the problem with more reporting or to escalate immediately into command-and-control behavior. The AgilePM approach is to re-engage the stakeholder through communication, education, and collaboration .

That is why meeting with Lee to explain the value of Sprint Reviews and planning his engagement is the best answer.

Sprint Reviews, or their AgilePM equivalent collaborative review points, are not merely “project meetings.” They are key opportunities to:

inspect progress,

review delivered value,

gather feedback,

align stakeholders,

validate evolving needs,

and improve the solution based on real input.

Lee’s absence means he has missed the primary forum where transparency, feedback, and shared understanding are built. If he now feels unaware, the issue is not that Agile ceremonies failed him; it is that he has not been effectively engaged in them. Hira should therefore address the root cause by helping him understand their purpose and agreeing a practical way for him to participate.

Why A is correct:

This option reflects AgilePM because it:

promotes active stakeholder involvement ,

uses collaboration rather than authority ,

addresses misunderstanding through communication and coaching ,

treats engagement as a shared responsibility,

and supports better ongoing participation instead of just compensating for disengagement.

It is also pragmatic. Hira can explore why Lee sees the reviews as a waste of time, clarify what decisions or insights he can gain from attending, and tailor his involvement so it is meaningful and efficient. That is consistent with agile leadership: remove barriers, improve understanding, and increase effective collaboration.

Why the other options are incorrect:

B. Provide Lee with Sprint summaries to keep him informed without wasting his time.

This is weaker because it accepts disengagement instead of improving it. Written summaries may help supplement communication, but AgilePM does not favor passive reporting as a substitute for active collaboration when stakeholder participation is important. Lee’s role as Business Advisor means his input is valuable, not just his awareness.

C. Ask Sarah to require Lee ' s attendance at all Sprint Reviews.

This is not the best AgilePM response because it relies on authority and escalation rather than facilitation and engagement. AgilePM encourages commitment and collaboration, not forced participation as the first solution. Compelled attendance may create compliance, but not meaningful contribution.

D. Schedule briefings with Lee before each Sprint using Project Planning insights.

This is also not the best answer because it shifts communication into a more one-way briefing model and focuses before the Sprint rather than on review of actual outcomes. The main issue is Lee’s lack of participation in the review and feedback loop. Pre-Sprint briefings do not replace the value of seeing increments, discussing results, and shaping next steps.

AgilePM perspective:

AgilePM places strong emphasis on:

continuous and active business involvement ,

collaborative reviews ,

transparency of progress ,

frequent feedback ,

and empowered, informed stakeholders .

A Business Advisor is expected to contribute specialist business insight. If that role disengages, the Project Manager should work to restore useful participation, not simply route around it with more documents or top-down enforcement.

In this case, Lee’s complaint about awareness is actually a sign that he needs better engagement with the agile process. Hira should respond by helping him understand that Sprint Reviews are valuable business touchpoints where he can see progress, influence direction, and remain informed in real time.

Therefore, from an AgilePM standpoint, A is the best answer because it reflects facilitative leadership, stakeholder engagement, and the agile principle of improving collaboration rather than replacing it with reports or mandates.

During the Foundations phase, Brinda Vyas organized a workshop that Hira facilitated. It was

attended by Sukra Aroon, Mira, Lee Tan, and Developers from the two Delivery Teams. The goal

was to define and align on what would be available for guests at the end of Project Increment 4.

The best answer is B because agile leadership is fundamentally about enabling collaboration, building shared understanding, empowering teams, and aligning people around a common vision rather than relying only on top-down instruction or documentation .

In this scenario, Hira is trying to achieve two things at the same time:

Preserve the benefits of agile leadership , which include empowerment, collaboration, engagement, and adaptability.

Ensure the Project Increment remains aligned with project objectives , especially Brinda’s vision for the Eco-spa experience.

Organizing workshops with Brinda, the Delivery Teams, and stakeholders to co-create a shared vision is the strongest AgilePM action because it creates alignment at the source. It ensures that the people building the solution understand not only what they are delivering, but also why they are delivering it. This is central to agile leadership, which is less about command-and-control and more about facilitating clarity, ownership, and commitment.

Why B is correct in AgilePM terms:

It promotes shared understanding across business and delivery roles.

It supports active stakeholder engagement , which is a major AgilePM theme.

It strengthens team ownership by involving the people doing the work in shaping the direction.

It helps align delivery with the business vision and project objectives.

It reduces misunderstanding and rework because expectations are discussed collaboratively early on.

It reflects the AgilePM idea that leadership should create the conditions for success through communication, facilitation, and empowerment.

In this case, the Eco-spa initiative includes sustainability, wellness services, local traditions, infrastructure, operations, and guest experience. Because the work is broad and multidimensional, alignment cannot be achieved effectively by planning alone or by handing tasks down in isolation. A shared vision workshop is the most powerful way to connect strategy, stakeholder expectations, and delivery execution.

Why the other options are less suitable:

A. Create a Delivery Plan outlining high-level activities for an aligned Eco-spa solution.

This is useful, but it is not the best answer. A Delivery Plan helps structure work, but by itself it is more of a planning artifact than an agile leadership action. It may support alignment, but it does not fully capture the collaborative and facilitative nature of agile leadership. Agile leadership is about engaging people around purpose, not just documenting activities.

C. Delegate to Team Leaders the task of defining deliverables that align with Brinda ' s vision.

This is weaker because it introduces a more hierarchical and fragmented approach. AgilePM encourages collaboration between business and delivery roles, not simply passing responsibility down to team leaders. Also, alignment with the vision should be developed collectively, not interpreted separately by a few individuals who may create gaps in understanding.

D. Collaborate with Brinda and Sukra to define actionable Product Backlog items.

This is a strong agile practice and is useful operationally, but it is still not the best answer. Product Backlog refinement helps translate vision into work items, but it happens after or alongside shared understanding. If Hira wants to balance agile leadership with alignment to objectives, she should first create broad agreement and common understanding among stakeholders and teams. Backlog items are more tactical; the workshop in option B is more strategic and leadership-oriented.

AgilePM perspective:

AgilePM emphasizes:

business engagement and stakeholder collaboration

empowered teams

clear business vision

iterative development supported by continuous communication

A leader in AgilePM does not merely instruct teams what to do. Instead, the leader facilitates an environment where the business vision is clearly understood, stakeholders are engaged, and teams can make informed decisions while staying aligned with the desired outcomes.

Since Brinda is the Business Visionary , her vision must be well understood across all involved parties. Hira, as Project Manager, should act as a facilitator of alignment rather than just a controller of tasks. Workshops are one of the most effective ways to achieve this because they encourage discussion, clarification, consensus, and buy-in.

Therefore, from an AgilePM standpoint, B is the best choice because it most directly balances agile leadership with strong alignment to project objectives through shared vision, collaboration, and stakeholder involvement.

The correct answers are C and E .

This is a classic business availability and decision-latency risk in AgilePM. The problem is not just that Brinda is absent. The bigger issue is that the Business Visionary input is missing at a time when strategic adjustments are affecting delivery decisions . That creates a real risk of:

misalignment with the project vision,

unnecessary assumptions,

frustration in the Delivery Teams,

and costly rework.

AgilePM relies heavily on active business involvement . When a key business role becomes unavailable, the right response is to restore decision-making guidance quickly and protect the teams from working blindly on uncertain items .

Why C is correct

“Hira should engage other business stakeholders to assume Brinda Vyas ' responsibilities to ensure the Delivery Teams receives strategic guidance.”

This aligns strongly with AgilePM.

Hira, as Project Manager, should act to restore the missing business guidance by coordinating with suitable business stakeholders who can temporarily support or cover the gap. AgilePM does not encourage leaving teams without access to strategic direction. It also does not assume that work should continue normally when a key business authority is unavailable.

This response is good because it:

maintains business engagement,

reduces decision delays,

protects alignment with the vision,

and helps the Delivery Teams continue with informed guidance.

In AgilePM, if a critical role is unavailable, the project should adapt so the necessary business input remains accessible.

Why E is correct

“The Delivery Teams should focus on backlog items with clear business direction and pause tasks that require Brinda Vyas ' input until guidance is available.”

This is also very AgilePM-aligned.

It is a practical risk response that avoids reckless progress based on guesswork. Teams should keep moving where the direction is already clear, but they should avoid pushing ahead on items that depend on missing strategic clarification.

This balances:

maintaining momentum,

avoiding unnecessary delay across all work,

and reducing the risk of rework on unclear items.

That is exactly the kind of sensible, adaptive delivery behavior AgilePM supports.

Why the other options are incorrect

A. Continue increment work based on the backlog, assuming adjustments can be made when Brinda Vyas returns.

This is not a good AgilePM response because it normalizes working with outdated or incomplete strategic guidance. If recent strategic changes have not been communicated, continuing as normal increases the risk of building the wrong thing.

B. Mira Bachar and the Delivery Teams should document assumptions behind decisions and continue progress without validation.

Documenting assumptions is better than ignoring them, but continuing without validation is still too risky in this scenario. AgilePM values transparency, but it does not support knowingly progressing on uncertain strategic assumptions when better escalation and stakeholder engagement are possible.

D. Hira should escalate to Sarah Lark, the Business Sponsor, to replace Brinda Vyas with another qualified Business Visionary.

This may become necessary if the absence is prolonged or the project is materially threatened, but it is too strong as the best immediate response here. AgilePM would first look to restore business guidance through practical engagement and controlled work selection before moving to formal replacement.

AgilePM perspective

AgilePM expects:

active and timely business input,

collaborative response to risks,

continued delivery where direction is clear,

and escalation or substitution when critical decision-making is missing.

So the best way to handle this risk is to:

restore business guidance through other suitable stakeholders , and

limit work to items that have clear direction until ambiguity is resolved .

Therefore, the correct answers are:

C, E

B does not align with AgilePM’s MoSCoW prioritization.

In AgilePM, Must Have requirements are the ones that are absolutely essential. If a Must Have is missing, the solution is not viable because it may be unusable, unsafe, non-compliant, or fail to deliver its core purpose.

A Should Have requirement is important, but it is not mandatory for the increment to be considered successful . It adds significant value, and the team aims to deliver it if reasonably possible, but the solution can still be successful without every Should Have being included.

Why the other options align:

A is correct because it accurately describes a Must Have.

C is correct because Could Haves are desirable but only delivered if time and capacity permit.

D is correct because Won’t Have this time items are deliberately excluded from the current increment and may be revisited later.

AgilePM perspective:

MoSCoW is used to protect delivery confidence and business clarity. It helps teams and stakeholders distinguish between:

what is essential,

what is important,

what is desirable,

and what is deferred.

The error in B is that it treats Should Have as if it were equivalent to Must Have , which is not how AgilePM defines the category.

So the correct answer is B .

The correct answer is C .

AgilePM balances agility and compliance by embedding compliance into the way work is defined, built, and reviewed , rather than treating it as a large upfront phase or a late-stage check.

Why C is correct:

By including regulatory acceptance criteria in the Definition of Done , compliance becomes part of normal delivery quality.

This ensures the team does not separate “done” from “compliant.”

Reviewing compliance through Sprint Reviews supports incremental inspection and early detection of issues.

This is a strong AgilePM response because it:

keeps compliance visible,

integrates it into iterative delivery,

reduces the risk of late surprises,

and supports evidence-based control.

Why the other options are not the best:

A is too upfront and predictive. AgilePM does not require full design before development starts.

B may sound collaborative, but it is impractical, especially since Wanida has limited availability.

D is useful as a tactic in some contexts, but it is less robust than building compliance directly into the team’s definition of complete work.

So the best answer is C .

The correct answer is B .

This is an approach-based risk , not a VUCA-based one, because the issue comes from how the team interpreted and validated the vision during delivery, rather than from an external unpredictable force.

The problem described is that the team prioritized guest luxury over sustainability , which caused a misalignment with the project vision. In AgilePM, that kind of misalignment usually points to a failure in:

ongoing collaboration,

validation of assumptions,

frequent feedback loops,

and continuous alignment with the Business Visionary.

Why B is correct:

AgilePM does not treat vision alignment as a one-time event only handled in Foundations. Even if the vision is initially clear, the Delivery Team must continue to:

validate their understanding,

test assumptions,

gather feedback,

and confirm they are still delivering in line with business priorities.

Since Brinda only recognized the misalignment at the Sprint Review, it suggests that the team had been operating on assumptions that were not checked often enough. AgilePM strongly encourages regular inspection and collaboration precisely to prevent this kind of drift.

So this is approach-based because the issue arises from the way the team worked and communicated, not from the external environment.

Why the other options are incorrect:

A. Approach-based, because Brinda Vyas ' expectations should be clearly communicated, captured and clarified in the Foundations phase.

This is partly true, but it is not the best answer. Foundations is important, but AgilePM does not rely only on early clarification. The stronger AgilePM point is that alignment must be maintained continuously throughout delivery, not assumed after Foundations.

C. VUCA-based, because customer expectations change in dynamic and unpredictable environments.

This is incorrect because the scenario is not about changing customer expectations. It is about misalignment with Brinda’s existing project vision . The issue is internal interpretation and validation, not environmental uncertainty.

D. VUCA-based, because Agile embraces change, so deviations are normal.

This is incorrect. Agile accepting change does not mean any deviation from the project vision is simply normal or classified as VUCA. A deviation caused by weak alignment is still an approach issue.

AgilePM perspective:

AgilePM depends on:

clear business vision,

active business involvement,

iterative validation,

and continuous communication between business and delivery roles.

When delivery drifts away from the intended balance of value dimensions—here, luxury and sustainability —that usually indicates the team did not sufficiently validate its understanding as work progressed.

Therefore, the best answer is B .

B is correct.

In AgilePM, planning is most effective when it includes the people closest to delivery. Delivery Team Leaders bring practical insight into:

current progress,

risks and blockers,

dependencies between teams,

feasibility of commitments,

and likely delivery impacts.

That makes their attendance appropriate and useful in a Project Sprint Planning Event.

Why the others are not best:

A is too strong. AgilePM supports collaboration, but it does not “mandate” joint decision-making in that exact wording.

C is incorrect because planning is part of effective delivery, not separate from it.

D is incorrect because excluding Team Leaders would reduce transparency and planning quality.

AgilePM favors collaborative planning with the right delivery voices present, so B is the best answer.

The correct answers are B and E .

In AgilePM, risk management is both team-level and project-level . Risks should be handled at the lowest appropriate level first , with collaboration and visibility, and then aligned upward when they could affect wider priorities, architecture, business value, or delivery plans.

This scenario involves a technical integration risk between the Spa systems and the resort’s client management system. That kind of risk should not automatically be pushed upward for others to solve, nor should it be handled in isolation by one person. AgilePM favors a collaborative, transparent, and proportionate response .

Why B is correct

“The Delivery Team should address technical challenges collaboratively while keeping project-level roles informed.”

This is strongly aligned with AgilePM because:

the Delivery Team is closest to the work and best placed to explore the issue first,

technical risks should be surfaced early and addressed collaboratively,

and relevant project roles should stay informed in case the issue affects broader delivery, dependencies, architecture, or business priorities.

AgilePM does not encourage unnecessary escalation of every problem. Teams are empowered to work through delivery issues where possible. At the same time, transparency matters, so project-level roles such as Hira and Sukra should not be left unaware of a risk that could grow.

Why E is correct

“Hira should coordinate with Sukra Aroon and Brinda Vyas to align team risk management activities with overall project priorities.”

This also fits AgilePM very well. If an integration risk has the potential to affect:

solution integrity,

business outcomes,

scope decisions,

sequencing,

or delivery trade-offs,

then Hira, as Project Manager, should help ensure that team-level mitigation is aligned with the wider project context.

Why these specific roles matter:

Sukra Aroon brings architectural and technical oversight.

Brinda Vyas safeguards alignment with the project vision and business priorities.

Hira ensures coordination, visibility, and alignment across the project.

This reflects AgilePM’s principle that risk management is shared , not isolated.

Why the other options are incorrect

A. Escalate immediately to Hira who will devise and implement a mitigation plan.

This is too centralized. AgilePM does not say every identified risk should immediately be handed to the Project Manager to solve personally. The Delivery Team should first engage with the issue directly where appropriate.

C. Hira should instruct Sukra Aroon to resolve the issue independently to ensure there is no risk to the overall solution.

This is not AgilePM-aligned because it isolates the risk with one technical authority. Sukra’s input is important, but integration risks usually need collaboration with the team, not independent resolution in a silo.

D. The Delivery Team should escalate to project level roles and focus on other work until a resolution is found.

This is too passive and reduces team ownership. Unless the risk fully blocks progress, the team should actively collaborate on the issue and continue managing work intelligently rather than simply waiting.

AgilePM perspective

AgilePM encourages:

early identification of risk ,

team ownership where appropriate ,

cross-role collaboration ,

visibility to project leadership ,

and alignment of local actions with overall business and technical priorities .

So the best two answers are:

B, E

Here the task is to identify which AgilePM principle is most significantly compromised in each case, based on the behavior or concern described.

1. Lee Tan is skeptical about agile ways of working and dismisses Sprint Reviews as a waste of time, creating tension and hindering collective alignment.

Answer: G — Communicate continuously and clearly

Sprint Reviews are a core mechanism for transparency, feedback, shared understanding, and alignment. If Lee dismisses them and creates tension around them, the biggest principle being undermined is continuous and clear communication .

Why not just Collaborate ?

That is also affected, but the most direct issue here is rejection of a structured communication and feedback forum. Sprint Reviews exist to keep business and delivery aligned through ongoing communication.

So the most significantly compromised principle is:

1 → G

2. Priya insists that all aspects of the aromatherapy oil, including packaging and marketing, must be fully defined before development, causing concern among teammates.

Answer: F — Develop iteratively

This directly conflicts with AgilePM’s belief that not everything must be fully detailed upfront. AgilePM supports evolving detail over time through learning, feedback, and iteration.

Priya’s position reflects a predictive mindset: define everything first, then build. AgilePM instead encourages starting from sufficient understanding and refining as the team learns more.

So the most significantly compromised principle is:

2 → F

3. Lee Tan is reluctant to release operational staff to act as Business Advisors for the Spa’s booking system, prioritizing short term efficiencies. He assumes business requirements are obvious and Developers can proceed without direct business input.

Answer: A — Focus on the business need

This is a strong violation of the principle of focusing on the business need . AgilePM depends on active business involvement to ensure that what is delivered genuinely meets operational and strategic needs.

If operational staff are not made available as Business Advisors, the team risks building a solution based on assumptions rather than real business understanding. That undermines the ability to ensure the solution is fit for business purpose.

Why not Collaborate ?

That is involved too, but the core failure is the assumption that delivery can proceed without direct business input. That most fundamentally threatens alignment to the real business need.

So the most significantly compromised principle is:

3 → A

4. Many Delivery Team members in Spa operations, marketing, and IT are part-time and their daily responsibilities are taking priority over project roles. Their limited availability raises concerns about meeting Sprint commitments.

Answer: B — Deliver on time

This concern most clearly threatens the AgilePM principle of delivering on time . If part-time participation and competing priorities reduce team capacity, Sprint commitments become unreliable and timeboxes are put at risk.

AgilePM places strong emphasis on protecting time and using prioritization and commitment to ensure timely delivery. If people are not sufficiently available, timely delivery becomes difficult.

Why not Demonstrate control ?

That could also be affected, but the scenario explicitly points to concern about meeting Sprint commitments, which most directly maps to delivery timeliness.

So the most significantly compromised principle is:

4 → B

5. IT developers worry that testing critical booking system integrations can only happen at the end of the Project Increment, rather than being embedded within each iteration.

Answer: D — Never compromise quality

This most directly undermines never compromise quality . AgilePM expects quality to be built in throughout delivery, not deferred until the end. Leaving critical integration testing until the end increases the risk of defects, surprises, rework, and unstable delivery outcomes.

Testing should be integrated into the iterative process so that quality is assessed continuously and problems are found early.

Why not Develop iteratively ?

Iterative development is also relevant, but the main concern here is not iteration itself. It is that quality assurance, especially critical integration testing, is being postponed. That most clearly violates the principle of protecting quality.

So the most significantly compromised principle is:

5 → D

The correct answers are C and D .

AgilePM treats risk management as a continuous, embedded, and collaborative activity , not as a one-time exercise done only at the beginning of the project. Risks are identified, discussed, reviewed, and responded to throughout the lifecycle using iterative planning, stakeholder engagement, feedback loops, and frequent inspection points.

Why C is correct

“AgilePM embeds risk management in processes, proactively addressing risks at multiple levels.”

This is a core AgilePM concept. Risk is not handled separately from delivery. Instead, it is built into the way the project works through:

iterative planning,

prioritization,

collaboration between business and technical roles,

incremental delivery,

frequent reviews,

and ongoing reassessment of assumptions and dependencies.

AgilePM recognizes that risks may emerge from both:

the external environment such as regulation, price changes, or market shifts, and

the project approach such as weak communication, poor alignment, or misunderstood priorities.

Because of this, risk management must happen at multiple levels across the project, not only in formal risk logs.

Why D is correct

“AgilePM leverages Sprint Reviews and feedback loops to surface and mitigate risks.”

This also strongly aligns with AgilePM. Reviews, demonstrations, and feedback events are important mechanisms for exposing:

misalignment with business goals,

technical integration problems,

missing requirements,

stakeholder concerns,

and benefit realization issues.

AgilePM relies on iterative feedback because it helps the team identify risks early enough to respond before they become major failures. A Sprint Review, for example, may reveal that a feature is not fit for purpose, that dependencies were missed, or that stakeholder expectations were misunderstood. That is exactly how AgilePM uses feedback to reduce risk progressively.

Why the other options are not the best answers

A. AgilePM allows Mira Bachar to adjust Backlog priorities with advice from Sukra Aroon and Hira to address risks.

This is plausible in practice , because reprioritization can indeed be used to respond to risk. However, it is more of a specific situational example than a broad statement of AgilePM’s overall risk approach. Since the question asks for the two statements that describe the approach itself, C and D are stronger and more directly aligned.

B. AgilePM removes all risks before execution, prioritizing avoidance over mitigation.

This is incorrect. AgilePM does not assume all risks can be removed before work begins. In fact, AgilePM accepts uncertainty as normal and focuses on:

early visibility,

continuous adaptation,

mitigation,

and learning through iteration.

Trying to eliminate all risk upfront would be unrealistic and contrary to agile thinking.

E. AgilePM assigns risk management solely to the Project Manager, Hira.

This is incorrect. In AgilePM, risk management is a shared responsibility . The Project Manager plays an important coordinating role, but risks are also surfaced and addressed by:

business roles,

technical roles,

delivery teams,

and stakeholders.

For example:

Mira may reprioritize work to reduce value risk,

Sukra may identify architectural or feasibility risks,

Brinda may highlight business alignment risks,

Hira may coordinate mitigation and escalation.

AgilePM perspective

AgilePM manages risk by making the project:

visible,

collaborative,

iterative,

feedback-driven,

and adaptable.

Rather than depending only on formal reporting or one person’s control, AgilePM spreads risk awareness across the project and uses regular events and evolving plans to keep risk under active management.

Therefore, the best two answers are:

C, D

The correct answer is A .

In AgilePM, when there is a disagreement between business value and solution risk , the best response is not to immediately side with one party, nor to force a premature decision. Instead, the Project Manager should facilitate collaborative decision-making so that the relevant roles can assess value, feasibility, risks, and trade-offs together.

That is exactly what Option A does.

Brinda, as the Business Visionary , is focused on ensuring that the Eco-spa experience delivers the intended holistic wellness value. From her perspective, the meditation garden may be an important part of the guest experience and brand promise.

Sukra, as the Solution Architect , is responsible for ensuring the integrity, quality, and feasibility of the solution. His concern about cultivating and maintaining the required plants is legitimate because it relates to delivery feasibility, sustainability, operational burden, and long-term viability.

Hira, as the Project Manager , should not resolve this by taking sides too early. Her role is to create the conditions for an informed decision by bringing the right people together, clarifying the issue, and helping them assess both:

the business value of including the garden, and

the delivery and operational risks associated with it.

Why A is correct:

A facilitated workshop is the most AgilePM-aligned response because it:

encourages collaboration between business and technical roles ,

supports shared understanding of benefits, constraints, and risks ,

enables informed decision-making based on evidence and discussion,

allows stakeholders to explore alternatives or compromises,

and reflects agile leadership through facilitation rather than command-and-control.

In a workshop, the group could discuss questions such as:

Is the meditation garden truly essential for minimum usable business value?

Are there lower-risk alternatives that still achieve the same wellness outcome?

Can plant selection, design changes, or maintenance plans reduce the risk?

Does the value justify the cost and complexity?

Should it be deferred, simplified, or prototyped first?

This is exactly the sort of balanced evaluation AgilePM encourages.

Why the other options are incorrect:

B. Support Sukra ' s perspective to minimize any additional architectural and maintenance risks.

This is incorrect because it means Hira would be prematurely siding with the technical perspective without properly considering the business value. AgilePM requires balance between feasibility and business need. Risk matters, but so does value.

C. Prioritize the garden as a Must Have, allocating resources to manage the risks.

This is incorrect because it assumes the garden should automatically be treated as a Must Have. In AgilePM, prioritization should be based on agreed business value, urgency, and feasibility, not on one stakeholder’s preference alone. Also, making it a Must Have before evaluating the risks properly would be poor governance.

D. Remind Brinda and Sukra of their roles, Brinda defines needs, Sukra decides how to deliver them.

This option contains a partial truth about role boundaries, but it is not the best way to resolve the conflict. While Brinda does represent business needs and Sukra advises on solution design, this is too simplistic for a situation involving risk, value, and potential trade-offs. AgilePM encourages collaboration, not rigid role-based separation as the primary conflict resolution mechanism.

AgilePM perspective:

AgilePM places strong emphasis on:

active business involvement

collaborative decision-making

fitness for business purpose

iterative exploration of value and risk

facilitative leadership

When tension arises between a desired feature and implementation risk, the right response is to evaluate the issue collaboratively rather than allowing either business ambition or technical caution to dominate without discussion.

In this scenario, the meditation garden may indeed add significant value to the guest wellness experience, but it may also introduce environmental, operational, and sustainability concerns. The best AgilePM response is therefore to explore the trade-off through structured collaboration.

So, from an AgilePM standpoint, A is the best answer because Hira should facilitate a discussion that assesses both potential value and associated risks before deciding how to proceed.