AgilePM-Practitioner Agile Project Management (AgilePM) Practitioner Exam Question 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.

In the UniCo case, the organization is undergoing significant changes that involve integrating the Selco team, revising internal processes, and preparing staff for a shift to mobile applications. Sources of conflict during such organizational change include misunderstandings, role ambiguity, and resistance to changes in work styles or policies.

Revised Answers (aligned with the UniCo case):

1. Instructions are understood by different people in different ways, influenced by their unique personal background.

Answer: C. Perceptions

In the UniCo scenario, perceptions are a key source of conflict, especially between the long-standing UniCo staff and the Selco team. For example, different views on the importance of the rebranding efforts reflect how unique personal backgrounds influence perceptions.

2. The revision of internal processes or systems has caused a lack of clarity on the responsibilities for certain tasks, resulting in activities being overlooked or duplicated.

Answer: F. Roles

This aligns with the UniCo case where process revisions are required to integrate Selco staff and adjust to the new business focus. A lack of clarity in responsibilities—like how teams should collaborate on mobile applications—creates role-based conflict.

3. Instructions on the project are given by different people using different levels of planning, formality, and decision-making approaches.

Answer: B. Styles

In the UniCo scenario, the cultural differences between the dynamic, fast-paced Selco team and the more structured UniCo team highlight conflicting work styles, which may result in tension during decision-making and task execution.

4. The parties involved are continually making amendments and extensions to delivery deadlines to accommodate the changing environment.

Answer: H. Unpredictable policies

In UniCo, the organizational changes, such as the relocation of the Selco staff and the integration of operational processes, require frequent adjustments. This creates uncertainty and frustration, which are classic symptoms of conflict due to unpredictable policies.

This question examines the application of David Rock ' s SCARF framework , which identifies five social drivers influencing motivation: Status, Certainty, Autonomy, Relatedness, and Fairness. In this scenario, the focus is on status , which refers to the perception of one’s standing or importance relative to others in a group.

1. Understanding the Status Domain in SCARF

Status is one of the core social needs in the SCARF framework.

It is linked to how individuals perceive their importance or recognition within an organization.

Acknowledging contributions publicly enhances status by signaling respect and appreciation, which motivates individuals to engage and cooperate.

2. Why Option D is Correct

In this scenario, the Operations Director’s public praise of the Applications Manager acknowledges their cooperation in relocating to a shared workspace.

This public acknowledgment improves the Applications Manager’s informal status within the group by:

Showing that their efforts are valued.

Positioning them as a cooperative and contributing member of the leadership team.

Enhancing status in this way fosters motivation and strengthens engagement in the change process.

3. Analysis of Other Options

Option A: No, because ' status ' should be rewarded by ensuring open, two-way communication using rich channels.

While two-way communication is important for building relatedness or addressing concerns, it does not directly address the brain’s need for status , which is driven by recognition and acknowledgment.

Eliminate.

Option B: No, because the Application Manager ' s knowledge and skills are still relevant and there is no threat to ' status ' .

This misinterprets the concept of status. The relevance of skills is unrelated to the need for recognition. Status can still be boosted even when skills are intact, especially in a new environment where informal recognition is key.

Eliminate.

Option C: Yes, because highlighting cooperation provides an opportunity for the Applications Manager to learn and develop.

While cooperation can contribute to learning and development, the focus here is on public acknowledgment of contributions to improve status, not on skill-building or development.

Eliminate.

4. Practical Implications

The public acknowledgment at the Operations group meeting serves to:

Reinforce positive behavior (cooperation during relocation).

Increase the Applications Manager’s informal standing within the leadership team.

Such actions align with the SCARF framework by addressing social motivations and fostering collaboration.

5. Reference to SCARF Framework

Status : Enhancing motivation by recognizing contributions publicly, which boosts an individual’s perceived value.

Threats to status (e.g., moving to a shared workspace) can be mitigated by public praise, maintaining the individual ' s perception of importance.

Assertion 1:

In order to ‘create a sense of urgency around a single big opportunity’ with the rebranding work, the Marketing Manager should appoint the founder of Selco to lead the rebranding workstream.

Reason:

Kotter defines ‘creating a sense of urgency around a single big opportunity’ as identifying innovators who will create momentum by pioneering the change.

Answer: A

Explanation: Both the assertion and reason are true, and the reason clearly explains why the founder of Selco is suited to lead the rebranding workstream. Kotter’s model emphasizes identifying champions for change who can create urgency and inspire action.

Assertion 2:

All managers across UniCo need to be committed to the rebranding before the change process can begin to ‘formulate a strategic vision’.

Reason:

The ‘strategic vision’ is only viable when the majority of managers believe that change is absolutely essential.

Answer: A

Explanation: Both the assertion and reason are true, and the reason provides the rationale for the assertion. A strategic vision gains traction only when key leaders and managers recognize the importance of change, aligning with Kotter’s second step of securing buy-in.

Assertion 3:

The positive staff reaction to the recent press article will contribute to the momentum of the change programme by ‘celebrating visible, significant short-term wins’.

Reason:

‘Celebrating visible, significant short-term wins’ will help to reduce negativity.

Answer: A

Explanation: Both the assertion and reason are true, and the reason explains the assertion. Kotter’s model identifies celebrating early wins as a critical step to sustain momentum and mitigate resistance.

Assertion 4:

The CEO’s openness will help to make the vision more ‘sellable’ to the ‘volunteer army’ when ‘communicating the vision and the strategy’.

Reason:

It is important to institutionalize the strategic changes into the culture so that implementation of the vision becomes second nature to staff.

Answer: B

Explanation: Both the assertion and reason are true, but the reason does not directly explain the assertion. The CEO’s openness is more about inspiring and aligning the volunteer army, while institutionalizing change into culture is a separate step in Kotter’s model.

Final Answer Table

Assertion Line

Answer

1

A

2

A

3

A

4

B

Comprehensive and Detailed Explanation:

Providing learning feedback in cognitive learning focuses on offering timely, actionable information that helps learners assess their understanding and adjust their approach during or immediately after the learning process.

1. Feedback in Gagné’s Nine Events of Instruction:

Gagné ' s Fifth Event emphasizes the importance of providing feedback during learning activities to reinforce correct understanding and correct misconceptions.

Effective feedback is specific, immediate, and relevant to the learning task. It allows learners to reflect on their performance and apply improvements in real time.

2. Why Option C is Correct:

Reviewing learners ' ideas in a group discussion provides an interactive opportunity for real-time feedback. It allows learners to:

Share their understanding.

Receive constructive input from peers and facilitators.

Make immediate adjustments to their thinking.

Group discussions align with cognitive learning principles by promoting active engagement, critical thinking, and collaborative feedback.

3. Analysis of Other Options:

Option A: Giving supervisor feedback on return to work.

Supervisor feedback is important but typically occurs after the learning activity. It is more suited for workplace performance improvement rather than immediate learning feedback.

Option B: Testing before and after learning.

Testing evaluates knowledge acquisition but does not provide real-time feedback during the learning process, which is crucial for cognitive learning.

Option D: Discussion at the learners’ next annual performance reviews.

Annual reviews occur too late to be effective for learning feedback. Feedback needs to be immediate and closely tied to the learning activity for maximum impact.

4. Practical Example:

During a training session on problem-solving, participants share their approaches in a group discussion. The trainer provides constructive feedback, highlighting strengths and offering corrections, enabling learners to refine their skills on the spot.

5. Reference to Gagné’s Model:

Event 5: Provide Learner Feedback

Gagné emphasizes that feedback reinforces learning, ensures understanding, and guides learners toward desired outcomes.

Comprehensive and Detailed Step-by-Step Explanation:

Context from the UniCo Scenario:

The sales team is struggling with the transition to mobile products and new supporting systems, resulting in missed sales targets and unsustainable work practices. This resistance stems from change fatigue , lack of skills , and a perceived lack of support during the transition period . The Sales Director must address this resistance by providing motivation, clear guidance, and practical solutions .

Analysis of Each Option:

A. Visibly celebrate examples of the Sales staff using the new skills and systems.

Celebrating successes motivates the sales staff and creates positive reinforcement, boosting morale during challenging transitions. This approach aligns with AgilePM’s emphasis on recognizing progress to encourage a sense of achievement and reduce resistance .

Correct.

B. Allow those Sales staff with opposing attitudes to use the old systems in parallel.

Using the old systems in parallel creates inconsistency, confusion, and prevents full adoption of the new approach. It may reinforce resistance rather than addressing it. AgilePM principles advocate for consistent implementation of changes to ensure alignment and long-term success.

Incorrect.

C. Identify the options available for moving people out of the Sales area to other jobs.

This action does not address the core issue of resistance and the challenges in adapting to the new systems. It may also demoralize staff and increase turnover, contrary to the AgilePM principle of building team engagement and capability.

Incorrect.

D. Assign some of the sales team to work exclusively on developing the necessary skills.

Providing focused time for skill development allows staff to adapt without the pressure of simultaneously meeting sales targets. This aligns with AgilePM’s emphasis on supporting capability development and creating a sustainable pace of work during transitions.

Correct.

E. Provide a clear timetable of change to those Sales staff preparing for future operations.

While planning is essential, a timetable alone does not directly address the immediate challenges faced by the sales team. The focus here should be on reducing current pressure and supporting skill development.

Incorrect.

Why A and D Are Correct:

Celebrating Success (A):

Boosts morale and encourages adoption of new systems through visible recognition of progress.

Reinforces a positive culture of adaptability, which is crucial in AgilePM for overcoming resistance.

Focused Skill Development (D):

Eases the transition by giving staff the necessary time to master new skills without being overwhelmed.

Aligns with AgilePM’s focus on supporting team development to ensure successful change adoption.

References to AgilePM Framework:

Team Morale and Engagement:

Recognizing team achievements fosters collaboration and reduces resistance. (AgilePM Practitioner Guide, Chapter 12: Managing People)

Supporting Capability Development:

Ensuring teams have time and resources to upskill is a key factor in managing transitions. (AgilePM Practitioner Guide, Chapter 10: Preparing for Change)

Sustainable Pace of Work:

AgilePM emphasizes balancing work demands to prevent burnout and maintain productivity during change initiatives. (AgilePM Practitioner Guide, Chapter 9: Leadership and Engagement)

Comprehensive and Detailed Step-by-Step Explanation:

When identifying a statement that fits under the Change Management Team and Relationships heading, it is crucial to focus on relationships, interactions, and dynamics within the team and between stakeholders.

1. Key Elements of the " Change Management Team and Relationships " Heading:

This heading relates to how the change management team interacts, communicates, and builds relationships with other stakeholders to address concerns or resistance.

It emphasizes understanding team dynamics, addressing concerns, and fostering collaboration.

2. Option Analysis:

Option A: The training available to UniCo staff needs to be realigned to include mobile application technology, so that the necessary skills are developed to support customers.

This is related to capability building rather than relationships or team dynamics. It focuses on skills alignment, which falls under training and development, not the Change Management Team and Relationships heading.

Eliminate.

Option B: The CEO seems to be a little concerned about taking the company in a different direction and his reservations need to be addressed.

This directly relates to the dynamics between the change management team and a key stakeholder (the CEO). Addressing the CEO’s concerns is essential for fostering trust and alignment, which is a core aspect of managing relationships within a change initiative.

Correct Answer.

Option C: The Project Management Office has offered to provide support in planning, scheduling, monitoring, and control.

While this statement highlights an offer of assistance, it pertains to project governance and support functions rather than team dynamics or relationship management. It does not directly address relationships or concerns.

Eliminate.

Option D: The Sales staff need to understand how the changes will lead to greater opportunities for increased commissions before they are likely to participate.

This is related to motivating the sales staff and aligning them with the change initiative but does not address team dynamics or relationships within the change management team itself.

Eliminate.

3. Relevance in UniCo’s Scenario:

The CEO’s concern about the strategic direction of the company is a potential risk to the success of the change initiative. Addressing his reservations is crucial for securing executive sponsorship, which is a key factor in successful change management.

Building trust and fostering alignment with the CEO ensures that the change management team has the support and resources needed to execute the change effectively.

4. Agile Practitioner Documentation References:

Stakeholder Management in Agile: Managing relationships with key stakeholders, including executives, is critical for ensuring alignment and addressing concerns.

Change Management Best Practices: Emphasizes addressing resistance and building strong relationships with all stakeholders involved in the change.

Using Schein ' s Concept of Survival and Learning Anxieties

Instructions:

Column 1 contains messages about the change communicated to the sales staff. For each message, select the appropriate element from Column 2.

Detailed Explanation

Schein ' s concept of survival and learning anxieties provides a framework for understanding how organizations can manage the discomfort (anxiety) associated with change while fostering readiness to adopt new behaviors.

1. " It may take longer than expected to learn... further training courses and support will be available. "

Answer: C. Creation of psychological safety

Psychological safety is established when individuals feel supported and reassured, reducing fear of failure or being overwhelmed. Offering additional training and support creates a safe environment for learning new processes.

2. " The new roles are quite different... staff lose their place if unable to adjust. "

Answer: B. Creation of guilt or anxiety

This message induces learning anxiety , as it implies a fear of losing one ' s role unless adjustments are made. Schein identifies this as a driver of motivation to change but cautions that it must be balanced with psychological safety to avoid resistance.

3. " Sales related to large-scale computer systems are declining... selling solutions within the mobile application environment. "

Answer: A. Disconfirmation

Disconfirmation occurs when individuals realize that their current behaviors, practices, or assumptions are no longer effective. Highlighting declining sales forces staff to question existing approaches and prepares them for change.

4. " Each member of staff will be measured... linked to individuals. "

Answer: B. Creation of guilt or anxiety

By associating performance metrics with individual accountability, this message creates survival anxiety or guilt, pushing staff to align with organizational expectations to avoid negative outcomes.

Summary of Schein’s Concepts:

Disconfirmation : Challenges existing assumptions and highlights the need for change.

Creation of Guilt or Anxiety : Introduces discomfort that motivates individuals to act.

Creation of Psychological Safety : Provides support and reassurance, ensuring individuals feel secure enough to embrace change.

Comprehensive and Detailed Step-by-Step Explanation:

Facilitating a workshop to design a process in a scenario like UniCo’s, where organizational change and integration are critical, requires participants with specific traits that align with Agile Project Management (AgilePM) principles. Here ' s why D is the best choice:

1. Alignment with Agile Values:

AgilePM emphasizes engagement, collaboration, and enthusiasm among participants. These attributes are critical for fostering a constructive environment where innovative and practical solutions can emerge.

Participants who are willing to be involved and enthusiastic bring energy to discussions and are more likely to engage fully in brainstorming and problem-solving, which is essential in designing effective processes.

2. Analysis of the Options:

Option A: Understanding the culture of the organization

While this is important for creating relevant and realistic solutions, it is not the most critical trait. Participants who lack enthusiasm or willingness to engage may not contribute effectively even if they understand the culture.

Option B: A good history of change implementation

Having a history of successful change implementation is a valuable trait, but it is less critical in the context of process design. This characteristic focuses on past actions rather than current engagement and collaboration.

Option C: Confidence in discussing ideas with others

Confidence is helpful, but enthusiasm and willingness to participate are foundational traits that often foster confidence during the workshop.

Option D: Willingness to be involved and enthusiastic

This characteristic ensures that participants are actively engaged and contribute constructively, which is vital for the success of any workshop. Enthusiasm also promotes collaboration and positivity, aligning with Agile principles.

3. Importance in UniCo’s Scenario:

UniCo’s challenges, such as resistance to change and the integration of Selco staff, require participants who are ready to engage with new ideas and adapt to new approaches. Enthusiasm and willingness help overcome resistance and drive collaborative efforts.

For UniCo to realign its business processes effectively, participants must actively contribute to discussions and be open to learning from their new Selco colleagues.

4. Agile Practitioner Documentation References:

Collaboration Over Hierarchy: AgilePM emphasizes fostering collaboration among team members with diverse skill sets and attitudes.

People Over Processes: The Agile Manifesto highlights the importance of individuals and interactions, focusing on their willingness to engage over their technical or organizational knowledge.

Facilitating Workshops in AgilePM: The handbook stresses the role of positive energy and active participation in workshops as drivers of innovation and process design success.

Comprehensive and Detailed Step-by-Step Explanation

The size and scope of a change agent network must be tailored to the needs of the specific workstream it is supporting. In the case of the Operational delivery processes workstream , the focus is on integrating systems and processes across both the UniCo and Selco locations.

1. Why C (Agents Covering Both Applications and IT Support) is Correct

Broad Coverage: Selecting change agents from both the Applications and IT Support areas ensures that the network addresses the full range of changes required, including technical systems, applications, and IT processes.

Dual Location Focus: The operational delivery workstream spans both the UniCo and Selco locations. Having representation from both locations ensures that changes are implemented effectively and address the unique challenges of each site.

Balance of Expertise: IT Support staff are critical for process-related changes, while Applications staff bring expertise in mobile application development, which aligns with UniCo’s strategic goals.

2. Analysis of Incorrect Options

Option A (Assign Two Agents):

Assigning only two change agents is overly restrictive and would not provide sufficient coverage for a large-scale integration of operational processes across multiple departments and locations.

Eliminate.

Option B (Recruit Mainly IT Support Staff):

While IT Support staff are experiencing significant changes, focusing solely on this group excludes other important areas, such as Applications, which are critical to UniCo’s strategy of integrating mobile applications.

Eliminate.

Option D (Involve Only Selco Staff):

Although Selco staff bring valuable expertise in mobile applications, relying exclusively on them could alienate UniCo staff and hinder buy-in for the change. A balanced network incorporating both UniCo and Selco staff is more effective.

Eliminate.

3. Practical Implications

Selecting change agents from both Applications and IT Support ensures that the network is comprehensive and aligned with the goals of the operational delivery processes workstream.

This approach also promotes collaboration between UniCo and Selco staff, which is essential for successful integration and cultural alignment.

The correct answer is C .

In AgilePM, information radiators such as dashboards are very useful, but they are not sufficient on their own for senior governance and strategic decision-making , especially for a role like the Business Sponsor .

Sarah, as the Business Sponsor , is accountable for ensuring that the project remains viable, aligned with business objectives, and worthy of continued investment. That means she needs more than raw or near-real-time status information. She also needs:

interpretation of what the information means,

context behind risks and issues,

insight into business impact,

understanding of trade-offs,

and confidence that the project is still aligned to strategic goals.

A dashboard can show progress, risks, and actions, but it usually does not fully provide the narrative, business context, rationale, escalations, and decision support that an executive stakeholder needs. AgilePM values transparency, but transparency is not the same as complete understanding.

Why C is correct:

A real-time dashboard is helpful as a supporting mechanism, but it does not fully meet Sarah’s needs because:

strategic stakeholders need context , not just data,

they often need explanation of why something matters ,

they need help understanding whether intervention is required,

and they require communication tailored to business decisions, not just operational tracking.

So the dashboard is useful, but not enough by itself .

Why the other options are incorrect:

A. Yes, because she will have access to progress updates, removing all meeting dependency.

This is incorrect because AgilePM does not suggest that dashboards replace all direct engagement. Communication with senior stakeholders still matters. Meetings, conversations, reviews, and decision forums remain important for clarifying implications and making timely decisions.

B. Yes, because she can rely solely on the dashboard for all her updates.

This is also incorrect. “Solely” is the problem. In AgilePM, relying on only one communication channel is risky, particularly for a sponsor role. Sponsors need summaries, discussions, escalations, and interpretation in addition to visible status information.

D. No, because she will need Hira to compile and present the data in a physical report for sharing.

This is incorrect because AgilePM does not require formal physical reporting as the preferred solution. AgilePM favors timely, transparent, and fit-for-purpose communication , not unnecessary documentation. The problem is not the absence of a physical report; the problem is the need for decision-making context.

From an AgilePM perspective:

AgilePM encourages rich communication , stakeholder engagement, and visible progress tracking. Dashboards are excellent for transparency and ongoing awareness, but executive roles such as the Business Sponsor need communication that supports governance and strategic control. That often includes:

regular reviews,

exception-based escalation,

discussions on risk exposure,

alignment to business case and priorities,

and recommendations from the Project Manager and key business roles.

In this scenario, Hira has done something valuable by introducing a real-time dashboard. However, to truly meet Sarah’s needs, Hira should combine the dashboard with targeted sponsor communication , highlighting key decisions, risks, dependencies, and whether the increment remains aligned to business objectives.

Therefore, from an AgilePM viewpoint, C is the best answer because dashboards support transparency, but they do not on their own provide the full context and insight required for strategic decision-making.

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.

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.

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.

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 lead the Solution Development Team effectively during the first Structured Timebox, the Project Manager should:

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

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

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

Selected Statements for the Development Approach Definition:

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

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

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

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

Why Other Statements Are Excluded:

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

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

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

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.

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.

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.

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

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

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

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

In Agile Project Management, it ' s important to involve key stakeholders and to ensure that there ' s a collaborative approach to project decisions. Considering the Agile principles and the given scenario, the appropriate application of Agile to the Feasibility Assessment would likely involve the following statements:

B. The Architecture Angels ' Finance Director should approve the final Business Case as part of the Feasibility Assessment. In Agile, it ' s crucial to ensure that the business aspect of any project aligns with the financial feasibility. The Finance Director ' s approval would be significant in validating the economic viability of the project.

D. The different options should be presented to the ' Hoy for Hoy Hall ' Action Group for their feedback before the chosen outline solution is finalised. Agile encourages stakeholder engagement and iterative feedback. Presenting options to the action group aligns with the Agile value of customer collaboration over contract negotiation, allowing for community input that could be vital due to the building ' s heritage status and the community ' s interest.

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.

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.

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.

A is correct.

In AgilePM, MoSCoW prioritization is used to protect the timebox and preserve delivery of the most important outcomes. A Should Have is important, but it is not essential in the same way as a Must Have . If delivery risk increases, it is valid to reclassify or defer a Should Have, especially where a workable alternative still supports the business outcome.

Why A is best:

it reduces delivery risk,

protects the timebox,

and still preserves some outdoor guest experience through the River Pool Patio workaround.

Why the others are weaker:

B is too broad. Dependencies alone do not automatically justify removal.

C is too restrictive. A Should Have may be deferred when needed to protect time and viability, not only when a Must Have is directly threatened.

D is incorrect because workarounds are not automatically poor practice; they can be sensible agile trade-offs.

So the most AgilePM-aligned answer is A .

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

In AgilePM, a Delivery Team structure should support effective collaboration, clear focus, frequent delivery, and alignment to business needs . Hira’s proposal to split the Developers into two Delivery Teams can be justified when that structure improves communication, coordination, and commitment around a coherent area of work.

Option D is correct because it best reflects a practical AgilePM reason for organizing teams in this way. If one team concentrates on Spa Infrastructure and the other on Guest Experience / Spa Operations , each team can build stronger collaboration around a shared purpose. Team members working toward closely related outcomes often communicate more effectively, develop stronger ownership, and stay better aligned to their immediate goals. In AgilePM, this supports the principle of creating empowered teams that can focus on delivering business value.

Why the other options are incorrect from an AgilePM perspective:

A is incorrect because one Delivery Team should not dictate another team’s priorities. In AgilePM, priorities are driven by the business need and managed through appropriate roles such as the Business Visionary and especially the Product Owner / Business Ambassador-style representation of business needs , not by one team controlling another. Teams collaborate; they do not command each other.

B is incorrect because separate Delivery Teams do not eliminate the need for coordination. In this scenario, the spa infrastructure and guest experience elements are clearly connected. For example, treatment rooms, utilities, hydrotherapy capability, reservations support, and guest experience design are likely to have dependencies. AgilePM supports iterative delivery, but it also recognizes the importance of active coordination where workstreams are interdependent.

C is incorrect because although team focus is valuable, the wording suggests separation from “other skill sets” in a way that promotes silos. AgilePM favors collaborative, multi-skilled teams , not isolated specialist groups that avoid interaction. A team may have a specialization in outcome or domain, but Agile ways of working still depend on cross-functional cooperation and shared understanding.

From the case context, Hira is managing a significant initiative that combines:

construction and sustainable infrastructure,

wellness services,

guest operations,

local traditions,

compliance,

and business value delivery.

Because the work spans distinct but related domains, having two specialized Delivery Teams can make sense only if it improves communication and commitment within each area while still preserving overall coordination under shared product direction. That is exactly what Option D captures.

So, from an AgilePM viewpoint, D is the strongest supporting statement because it aligns with the idea that an effective team structure should enhance collaboration, ownership, and focus while contributing to successful incremental delivery.

The correct answers are A and E .

In AgilePM, effective risk management depends on shared responsibility, continuous awareness, and proactive behaviour across the whole team. Risk is not something handled only by one role, one document, or one event. It is woven into the way the team works every day.

Why A is correct

“Team members should adopt a collaborative mindset, sharing responsibility for identifying and mitigating risks.”

This aligns strongly with AgilePM. Risks emerge from many areas:

business priorities,

technical feasibility,

compliance,

dependencies,

stakeholder engagement,

and delivery constraints.

Because of that, the best way to manage risk is for the team to work collaboratively and raise concerns early. Different people see different risks:

Mira may see value or prioritization risk,

Sukra may see architecture or integration risk,

Hira may see coordination or dependency risk,

Wanida may see compliance risk,

Developers may see delivery feasibility risks.

AgilePM encourages a culture where risks are surfaced openly and addressed together rather than left to a single person.

Why E is correct

“Risk management should be proactive and part of daily activities, not a separate process.”

This is also a core AgilePM principle. Risk management is most effective when it is:

continuous,

visible,

built into team discussions,

and handled as part of normal delivery activity.

That means risks should be considered during:

planning,

backlog discussions,

reviews,

daily collaboration,

dependency conversations,

and stakeholder feedback.

AgilePM does not treat risk as something only reviewed in occasional formal meetings. The team should be alert to emerging issues and respond before they become major problems.

Why the other options are incorrect

B. Hira should have sole responsibility for managing all risks with clear accountability.

This is incorrect. Hira, as Project Manager, has an important role in coordinating risk management, but AgilePM does not place all risk responsibility on one person. Risk management is shared across business, technical, and delivery roles.

C. Developers should resolve all risks collaboratively and promptly without escalation.

This is incorrect because some risks should be escalated. AgilePM encourages teams to resolve issues at the right level, but not to avoid escalation when broader decisions, sponsorship, governance, or cross-team intervention are needed.

D. Sukra Aroon should handle all technical risks independently to ensure the solution is fit for purpose.

This is incorrect because even technical risks often require collaboration. Sukra contributes architectural leadership, but technical risks may affect priorities, cost, compliance, usability, and business outcomes, so they should not be handled in isolation.

AgilePM perspective

AgilePM supports team behaviour where:

everyone is alert to risk,

risks are discussed early,

people collaborate across roles,

escalation happens when needed,

and risk thinking is part of everyday delivery.

So the two statements that best describe appropriate team behaviour for effective risk management are:

A, E

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 answers are A and C .

AgilePM does not ignore uncertainty. It manages it openly and practically.

Why A is correct

“Use broad estimation ranges for high-uncertainty work and refine estimates as more information becomes available.”

This fits AgilePM very well because it acknowledges reality: some work is more uncertain than other work. Broad early estimates are often more honest and useful than false precision.

Why C is correct

“Identify key assumptions behind estimates and revisit them regularly as the project evolves.”

This is also strongly aligned. Estimates are shaped by assumptions, and AgilePM expects those assumptions to be made visible and rechecked as learning increases.

Why the other options are incorrect

B is too absolute. AgilePM still expects useful estimation even when uncertainty exists.

D is contrary to agile thinking because fixed early estimates create false certainty.

E is not appropriate because uncertain work should still be considered in planning, even if estimated at a higher level.

So the best answers are A, C .

D is correct.

In AgilePM, adapting the Delivery Plan can be entirely appropriate, especially to support early testing and reduce risk. The issue in this question is the wording that Hira decides this alone. Sequencing and delivery trade-offs should be made collaboratively with the relevant business and technical roles, not unilaterally by the Project Manager.

Why D is best:

Delivery planning should reflect input from Delivery Teams, Product Owner, and Solution Architect.

Hydrotherapy sequencing affects dependencies, feasibility, and business priorities.

AgilePM supports collaborative control, not one-person plan ownership.

Why the others are weaker:

A is partly true in principle, but it ignores the collaboration issue.

B is also partly true, but documentation is not the core question.

C is incorrect because the Delivery Plan is not rigidly fixed after Foundations.

So the most accurate AgilePM answer is D .

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 .

This question is about keeping infrastructure work aligned with the planned treatment experience throughout development. The strongest way to do that is through ongoing review and refinement with the Product Owner , here Mira Bachar.

Why A is correct:

Mira represents the guest and business perspective.

Regular review ensures infrastructure items still support the intended hydrotherapy experience.

Refinement allows the backlog to evolve as understanding improves.

This is consistent with AgilePM’s emphasis on collaboration, feedback, and continuous alignment.

Why the other options are incorrect:

B is not agile. Locking backlog items too early prevents adaptation and increases the risk of delivering something misaligned.

C is useful, but it focuses more on priority than on direct alignment with the intended experience. High priority alone does not guarantee the right treatment outcome.

D is incorrect because prioritization should not sit solely with the Infrastructure Team. Delivery Teams contribute feasibility insight, but business/value prioritization belongs with the Product Owner and wider business roles.

AgilePM perspective:

AgilePM encourages:

frequent review,

collaborative refinement,

active business involvement,

and evolving backlog detail.

Therefore, the best answer is A .

The best answers are C and D .

C is correct because AgilePM promotes building quality and risk control into the work itself. Adding integration testing to acceptance criteria ensures that relevant items are not considered complete unless the integration risk has been addressed.

D is also correct because including explicit integration test scenarios in the Sprint Backlog makes the risk visible, actionable, and part of planned delivery rather than something left vague or deferred.

Why the others are weaker:

A is not AgilePM-aligned because timeboxes should not be casually extended.

B is too centralized; Sukra’s input matters, but risk handling should be collaborative and embedded in delivery.

E is too late and reactive; integration concerns should be addressed continuously, not saved for the end.

So the correct answers are C, D .

The correct answers are B and D .

An initial Product Backlog in AgilePM should be:

value-oriented,

manageable,

visible,

and adaptable.

Why B is correct

“Capture dependencies between Product Backlog items to proactively prevent blockers in development.”

This is useful and practical. Dependencies matter because they can affect sequencing, feasibility, and delivery flow. Identifying them early helps reduce surprises.

Why D is correct

“Allow Product Backlog flexibility so it evolves based on feedback and business needs.”

This is a core AgilePM concept. The backlog is not static. It should evolve as:

business needs become clearer,

feedback is received,

priorities shift,

and learning emerges through delivery.

Why the other options are incorrect

A is too rigid and over-specified.

C is wrong because prioritization should be based on business value and need, not merely speed of completion.

E is unhelpful because separating business and technical backlog items too rigidly can damage alignment and visibility.

So the best answers are B, D .

The best answers are B and E .

B is correct because AgilePM’s strongest reassurance comes from visible, embedded quality control . Making quality criteria explicit and ensuring teams confirm compliance before calling work “Done” shows that quality is being managed proactively, not assumed.

E is also correct because stakeholders are specifically worried due to problems in the India project. Reviewing those past issues and showing how Project Increment 4 is handling them differently directly addresses their concern with evidence and learning.

Why the others are weaker:

A is helpful, but it is more about visibility than about the strongest quality assurance mechanism.

C is too absolute; AgilePM helps manage quality, but it does not guarantee quality issues can never happen.

D introduces a heavier control layer that is not the primary AgilePM approach.

So the correct answers are B, E .

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.

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.

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.

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.