AgilePM-Practitioner Questions and Answers

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

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

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

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

Comprehensive and Detailed Step-by-Step Explanation

Understanding Stakeholder Pain Points in the UniCo Scenario

A " pain point " refers to challenges, concerns, or additional efforts that stakeholders perceive during a change process. For the Sales team members, these challenges would most likely relate to adapting to new processes and requirements resulting from the rebranding and strategic shift.

Option Analysis

A. Rebranding gives the company a modern look that has been missing historically

This statement highlights a positive aspect of the change rather than a " pain point. " While rebranding may indirectly impact the Sales team, it is unlikely to be perceived as a primary concern or challenge.

Incorrect.

B. Comprehensive training is required to broaden skills, that are recognized as best practice

While training is an important component of change, the statement frames it positively (broadening skills recognized as best practices). Training may be challenging, but it is not likely the most significant pain point for Sales team members in this scenario.

Incorrect.

C. Increased effort will be needed initially to learn the new supporting business processes

The UniCo scenario indicates that Sales team members are already facing disruptions to their normal processes. Learning and adapting to new supporting business processes (e.g., systems and practices introduced to align with Selco’s expertise) requires significant effort and is a clear " pain point. " This aligns directly with the operational challenges described for the Sales staff.

Correct.

D. This gives an opportunity for all staff to be involved and engaged in shaping the change

Similar to A , this option reflects a positive engagement opportunity rather than a pain point. While involvement in shaping change is beneficial, it does not directly address the challenges faced by Sales team members.

Incorrect.

Why C is the Correct Answer (Scenario Alignment)

The Sales staff at UniCo are already facing disruptions and challenges due to the rebranding and integration of Selco. Adapting to new business processes, particularly those supporting mobile applications and innovation, represents a pain point as it demands additional effort and adjustment during the change process.

References (UniCo Scenario and AgilePM Alignment):

UniCo Scenario: " Sales staff have faced disruption due to changes in sales processes and must adapt to new supporting processes. "

AgilePM Handbook, Chapter 8: Addressing Stakeholder Needs and Managing Change Impacts.

Agile Business Consortium – Stakeholder Pain Points and Impact Assessment.

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

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

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

For the XAN Insurance Company Web Project, 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.

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

Selected Statements for the Business Case:

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

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

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

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

Why Other Statements Are Excluded:

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

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

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

To 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.

Comprehensive and Detailed Step-by-Step Explanation:

Context from the UniCo Scenario:

The new structure announcement has caused uncertainty and dissatisfaction among the Customer Services staff, particularly in the Help Desk team. The situation requires a proactive and engaging approach to involve employees early in the change process, focusing on positive participation and addressing resistance constructively.

Analysis of Each Option:

A. Target those staff in the Help Desk who are change-averse so that they are the first ones involved in the program.

Why Incorrect: While addressing change resistance is essential, targeting change-averse staff first could increase resistance and negativity if not managed carefully. AgilePM advocates engaging enthusiastic early adopters to build momentum before tackling resistance.

B. Delay communications a few weeks so that all staff have time to think for themselves about the benefits of the new structure.

Why Incorrect: Delaying communications creates further uncertainty and allows rumors to escalate, eroding trust. AgilePM emphasizes the importance of early, clear, and continuous communication to reduce resistance.

C. Identify those staff who would be willing to trial new Help Desk processes and work on pilots in the department.

Why Correct: This approach aligns with AgilePM’s principles of involving stakeholders in incremental delivery and piloting solutions to gain feedback and build trust. Engaging willing staff to trial new processes helps demonstrate the benefits of the change and encourages others to follow suit.

D. Encourage the Help Desk staff to begin setting goals for themselves under the new structure.

Why Incorrect: Encouraging goal-setting may be beneficial later in the change process but does not directly address the current dissatisfaction or involve staff in shaping the change. AgilePM stresses active engagement over passive goal-setting at this stage.

Why C Is Correct:

Engaging Willing Staff:

Identifying and involving willing staff in piloting processes allows them to become change champions , demonstrating the benefits to others.

Incremental Approach:

Pilots enable the department to refine processes based on feedback, which is a core AgilePM practice for managing change.

Building Trust:

By involving staff in shaping the change, the organization fosters trust and mitigates resistance.

References to AgilePM Framework:

Stakeholder Engagement:

AgilePM encourages engaging key stakeholders early and leveraging early adopters to build momentum. (AgilePM Practitioner Guide, Chapter 8: Stakeholder Engagement)

Incremental Delivery:

AgilePM promotes piloting processes and iteratively refining solutions to ensure successful adoption. (AgilePM Practitioner Guide, Chapter 5: Incremental Development)

Managing Resistance:

Actively involving staff in pilots addresses resistance by showing the benefits of the change firsthand. (AgilePM Practitioner Guide, Chapter 10: Preparing for Change)

Comprehensive and Detailed Step-by-Step Explanation:

Context from the UniCo Scenario:

The Human Resources and Facilities Manager is responsible for tracking data related to the upskilling of staff in mobile applications, as well as analyzing training progress across departments. For effective change analytics, timely and accurate data is critical to enable actionable insights. Delays in reporting and inaccuracies can hinder real-time adjustments to training programs and resource allocation.

Analysis of the Answer Options:

A. No, because reporting on staff data should only be carried out by Human Resources.

Why Incorrect: This statement is irrelevant to the limitations of data analytics. While HR typically oversees reporting on staff data, the issue lies in the ability to provide real-time, accurate data for decision-making, not which department oversees the process.

B. No, because internal processes are likely to ensure a good data quality.

Why Incorrect: While internal processes might improve data quality, they do not guarantee timely or real-time accuracy. The issue highlighted in this scenario is the lag in data reporting, which limits its usefulness in dynamic change management.

C. Yes, because the volume of the source data is likely to be unmanageable.

Why Incorrect: There is no evidence in the scenario suggesting that the volume of data being collected for staff training is unmanageable. The challenge described pertains to the timeliness and accuracy of the data, not its scale.

D. Yes, because the source data is unlikely to provide ‘real-time’ accuracy.

Why Correct: Effective change analytics requires real-time data to monitor progress and make adjustments dynamically. In this case, the HR and Facilities Manager’s reliance on data that is not timely or accurate limits the ability to intervene effectively during training or skill development.

Why D Is the Best Answer:

Real-Time Data Is Crucial for Change Analytics:

AgilePM emphasizes the need for actionable insights derived from up-to-date information. Data that is delayed or inaccurate prevents quick responses to emerging issues.

Alignment with Agile Principles:

In change programs, especially those involving skill development, real-time feedback is critical for iterative improvements. Lagging or retrospective data fails to align with this principle.

Practical Challenges:

The scenario implies limitations in data collection or reporting processes, which prevent real-time monitoring. This hinders the Human Resources and Facilities Manager from accurately tracking progress and making timely interventions.

References to AgilePM Framework:

Iterative Monitoring and Feedback:

AgilePM advocates for frequent and timely feedback to ensure continuous alignment with project goals. (AgilePM Practitioner Guide, Chapter 8: Quality Management)

Importance of Data-Driven Decision-Making:

Data must enable proactive, real-time adjustments to processes. Delayed or inaccurate data undermines this approach. (AgilePM Practitioner Guide, Chapter 11: Measuring Success)

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 Explanation:

Practical skill acquisition focuses on hands-on practice to ensure learners achieve mastery and consistency. This is central to Gagné ' s Nine Events of Instruction , which emphasize active learning strategies.

1. Relevance of Practice in Gagné’s Model:

Gagné ' s Event 6: Elicit Performance (Practice) highlights that learners must perform the skills themselves to solidify learning.

Practical application is critical to achieving competence, especially for motor or procedural skills. It allows learners to identify gaps and refine their performance through repetition.

2. Why Option A is Correct:

Practicing skills ensures that learners can consistently perform the task correctly. Repeated application:

Reinforces memory.

Builds muscle memory for physical tasks.

Promotes confidence and accuracy.

Consistency is the key indicator of mastery for practical skills.

3. Analysis of Other Options:

Option B: Observing repeated demonstrations of the skill by the instructor.

Observing demonstrations is useful for understanding, but it does not substitute for hands-on practice. Learners must engage actively to develop the skills themselves.

Option C: Group discussion of how to learn the new skills.

Discussion may help learners understand the steps or importance of the skill but does not directly contribute to skill mastery.

Option D: Presentation of how the new skills relate to the organizational change.

While this provides context, it does not help learners physically or cognitively practice the skill.

4. Practical Example:

In a training session for operating new machinery, learners achieve the best outcomes by practicing with the equipment until they can operate it confidently and consistently.

5. Reference to Gagné’s Model:

Event 6: Elicit Performance (Practice) emphasizes the importance of active learner participation to reinforce learning and ensure skill mastery.

Column 1 & Matches from Column 2

A new company logo, which maintains features of the existing UniCo logo, but also represents expertise in innovative solutions and mobile applications, is needed as a high priority for the rebranding of UniCo. Answer: C (Change Backlog) Explanation:

This represents a prioritized task to meet a strategic goal (rebranding). Such items are typically tracked and managed in a Change Backlog in Agile practices, enabling the team to prioritize and focus on delivering value.

Next time we work with the Sales Team, we will need to schedule the fast-track training of the Sales staff more carefully, as taking a member of staff away from the sales work caused operational issues. Answer: B (Retrospectives) Explanation:

The statement reflects a learning from past actions to improve future efforts, which is the essence of a Retrospective in Agile. Retrospectives are designed to reflect on what went well, what didn’t, and what can be improved.

Gaining access rights to make amendments to UniCo ' s new finance system is currently causing issues and holding up the updates to enable the system to work with the new processes. Answer: A (Stand-Ups) Explanation:

This statement describes a blocker or impediment being identified. Stand-Ups are daily meetings where team members discuss progress, share updates, and raise blockers for resolution.

The company procedures for delivering large-scale computer systems will need to be revised to reflect the new processes for mobile applications, taking an estimated 60 days of effort. Answer: C (Change Backlog) Explanation:

Revising procedures is a substantial task that needs to be prioritized and tracked. This is managed through the Change Backlog, where such larger initiatives are broken into smaller deliverables and scheduled appropriately.

Final Answer Table

Column 1 (Statement)

Column 2 (Answer)

1.

C (Change Backlog)

2.

B (Retrospectives)

3.

A (Stand-Ups)

4.

C (Change Backlog)

Explanation Based on Agile Practices

Change Backlog: Used to manage prioritized tasks and ensure alignment with business goals.

Retrospectives: Provide a mechanism for teams to reflect on their work and identify improvements.

Stand-Ups: Help highlight blockers and ensure continuous progress in iterative cycles.

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.

Comprehensive and Detailed Step by Step Explanation:

1. Assertion: The Change Manager should aim to engage and move the Customer Services Director to the Active Players quadrant.

Reason: Acknowledging a stakeholder’s influence is an important step in developing greater understanding of how to manage them.

Analysis: The Customer Services Director currently holds significant influence but is not fully engaged with the change. Moving them to the " Active Players " quadrant aligns with stakeholder management principles because Active Players have both high influence and high interest. The reason provided supports this by emphasizing understanding and managing stakeholders ' influence.

Conclusion: Both the assertion and reason are correct, but the reason does not directly explain why moving the stakeholder to " Active Players " is the action. Answer: B (True, True BUT the reason does not explain the assertion).

2. Assertion: The Change Manager should plan to increase the Operations Director’s level of interest in the change.

Reason: Influential Observers need to become Key Players if they need to be engaged actively in the change.

Analysis: The Operations Director is an influential observer with high influence but low interest. Increasing their interest ensures their alignment with the program goals, making them Key Players. The reason provided directly explains why this move is necessary.

Conclusion: Both the assertion and reason are correct, and the reason directly explains the assertion. Answer: A (True, True AND the reason explains the assertion).

3. Assertion: It is appropriate to manage the involvement of Selco staff by regularly sending them progress updates.

Reason: Spectators only require regular information updates to maintain their interest in the change.

Analysis: Selco staff are categorized as " Spectators, " indicating they have low influence and interest. Regular updates are sufficient to keep them informed without unnecessary engagement. The reason aligns with stakeholder management strategies for Spectators.

Conclusion: Both the assertion and reason are correct, and the reason directly supports the assertion. Answer: A (True, True AND the reason explains the assertion).

4. Assertion: The Human Resources Manager needs to be managed and moved to the Key Players quadrant.

Reason: People with specialist skillsets should be categorized with a high level of influence and power in any change.

Analysis: The Human Resources Manager currently resides in the " Active Players " quadrant. While they contribute specialist skills, this does not necessarily justify elevating them to " Key Players, " who must also possess significant influence. The reason, while true, does not align with the change scenario.

Conclusion: The assertion is false, but the reason is true. Answer: D (False, True).

Comprehensive and Detailed Step-by-Step Explanation:

The SCARF framework identifies five key domains of social experience that influence motivation: Status, Certainty, Autonomy, Relatedness, and Fairness. This question asks if the action taken by the Change Manager appropriately addresses the autonomy domain.

1. Why Autonomy is Not Addressed

Autonomy refers to an individual’s sense of control over their choices and environment.

In this scenario, UniCo employees feel powerless due to the loss of leisure space without consultation . Autonomy could have been addressed by giving staff more control or input during the decision-making process, such as asking for their preferences or involving them in discussions about how the space could be used.

Arranging a social lunch does not restore autonomy, as it does not give employees more control or decision-making power.

2. Why Relatedness is Addressed

Relatedness refers to the sense of connection and belonging among individuals in a group.

By organizing a social lunch for UniCo employees and Selco staff, the Change Manager is fostering social interaction and relationship-building , which addresses the need for relatedness rather than autonomy.

This helps improve relationships between the two groups but does not resolve concerns related to autonomy.

3. Analysis of Each Option

Option A: No, because ' autonomy ' is best rewarded by establishing clear change expectations.

While setting clear expectations can help alleviate uncertainty, it does not directly address autonomy. Restoring autonomy requires giving employees more input or control.

Eliminate.

Option B: No, because encouraging social interactions rewards the brain’s need for ' relatedness. '

Correct. The lunch encourages connection and collaboration, which aligns with the relatedness domain, not autonomy.

Correct Answer.

Option C: Yes, because ' autonomy ' is best rewarded by listening and supporting affected staff.

While listening to concerns is important, this action does not directly give staff more autonomy. Instead, it addresses relatedness by fostering relationships through social interactions.

Eliminate.

Option D: Yes, because inviting colleagues to interact will make staff feel less powerless.

Interactions may improve social cohesion, but they do not resolve the sense of powerlessness tied to autonomy. Autonomy requires giving individuals more choice or control.

Eliminate.

4. Practical Implications

To better address autonomy , the Change Manager could have involved UniCo employees in discussions about how to accommodate Selco staff or given them options for how leisure space could be managed collaboratively.

Social lunches, while helpful, are better suited for addressing relatedness by creating bonds and reducing friction between teams.

5. Reference to SCARF Framework

Relatedness: Actions that promote connection and collaboration among team members.

Autonomy: Actions that empower individuals with choices and control over their environment or decisions.

Comprehensive and Detailed Step-by-Step Explanation

A Sponsor is a critical role in any change program, tasked with providing high-level support, ensuring resources are allocated, and maintaining alignment between the change initiative and the organization ' s strategic priorities. The CEO is best suited for this role because they have the authority, vision, and ability to secure the necessary resources for the program.

1. Why D (Budget Allocation) is Correct

A sponsor’s primary responsibility is ensuring that the change initiative has adequate resources, including financial support.

The CEO’s ability to assign budgets promptly ensures that the program can progress without delays caused by a lack of funding.

This aligns with the sponsor ' s role of prioritizing resources to avoid disruptions to the change process.

2. Why E (Commitment and Authority) is Correct

A key attribute of a successful sponsor is their commitment to the change initiative and their authority to prioritize it across the organization.

The CEO’s position as the ultimate decision-maker and their endorsement of the change program as UniCo’s future direction reinforces the legitimacy and importance of the initiative.

By promoting the change and making it a strategic priority, the CEO ensures alignment at all levels of the organization.

3. Analysis of Incorrect Options

Option A:

While a thoughtful leadership style can be valuable, this alone does not align with the core responsibilities of a sponsor. The sponsor must be proactive in decision-making, resource allocation, and strategic oversight rather than focusing on creating an environment for behavior changes.

Eliminate.

Option B:

While acknowledging unease about the new direction might indicate self-awareness, it does not demonstrate why the CEO is the best fit for the sponsor role. Sponsors are expected to lead with confidence and conviction, even in unfamiliar situations.

Eliminate.

Option C:

Being heavily involved in operational details is not the role of a sponsor. Instead, the sponsor should focus on strategic oversight and delegating operational responsibilities to program managers or change leaders.

Eliminate.

4. Practical Implications

A sponsor like the CEO ensures alignment between the change initiative and organizational goals.

Their ability to secure resources and champion the program ensures its visibility and priority within the organization, fostering commitment at all levels.

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.

The correct answer is A .

AgilePM values estimation, but it also values proportionality . Estimating should help planning and decision-making, not become a heavy exercise that delays progress and creates unnecessary documentation.

Why A is correct:

Estimates should be accurate enough for the planning purpose at hand.

Teams should avoid excessive refinement when the extra effort gives little added value.

AgilePM encourages “just enough” detail, not exhaustive analysis.

This question highlights a common anti-pattern:

too much time spent estimating,

too much documentation,

and too little focus on actual delivery.

Why the other options are incorrect:

B is incorrect because trying to eliminate all uncertainty is unrealistic and contrary to AgilePM thinking.

C is incorrect because although early estimates may be broad, refinement is still useful later when more information becomes available.

D is incorrect because documenting every assumption in detail is excessive and not agile.

So the best answer is A .

Comprehensive and Detailed Step-by-Step Explanation

Understanding Transparency in Change Management

Transparency refers to open communication, ensuring that stakeholders are well-informed and have access to relevant information. It promotes trust and reduces resistance to change by making the process visible and understandable.

Option Analysis

A. Ensure everyone is treated fairly by providing the same information, in the same format, to everyone impacted by this change

Providing consistent information ensures that all stakeholders receive the same details and feel equally valued, reinforcing transparency in communication.

Correct.

B. Send daily emails to everyone to remind them how important this change is and why they should support it

While frequent communication is helpful, daily emails emphasizing importance can feel repetitive or coercive, which does not align with the principle of transparency.

Incorrect.

C. Distribute the key milestones and target dates for including Selco’s mobile technology and approaches into the UniCo operations

Sharing milestones and timelines increases clarity and accountability, providing stakeholders with a clear understanding of progress and expectations.

Correct.

D. Ask Corporate Services to provide guidelines to ensure all written communications are easy to read and navigate

Although clarity in communication is valuable, creating guidelines focuses on internal documentation rather than openly sharing information with stakeholders.

Incorrect.

E. Publish how staff members can raise complaints and suggestions, formally and anonymously if needed

While this supports inclusion and feedback, it does not inherently align with transparency as it focuses more on creating a feedback mechanism than on open sharing of information.

Incorrect.

Why A and C are the Correct Answers (Scenario Alignment)

A: Ensures equality in information dissemination, helping all stakeholders feel informed and included.

C: Offers visibility into the change process, timelines, and progress, building trust through clear and open communication.

References (AgilePM and Scenario Alignment):

AgilePM Handbook, Chapter 7: Transparent Communication Strategies in Change Management.

UniCo Scenario: " UniCo staff must be kept informed of the integration process and timelines to align their efforts with the organization ' s goals. "

Agile Business Consortium – Importance of Milestones and Open Communication in Stakeholder Engagement.

D is correct.

In AgilePM, thinking about how benefits will be realized should not be postponed until the final Sprint. Realization planning should be considered early, as part of the project’s business justification and ongoing business thinking, so the solution is built with adoption and benefit delivery in mind from the start.

Why D is correct:

benefit realization should be planned early,

post-launch alignment with guest demand is part of achieving business value,

and waiting until the final Sprint is too late and increases risk.

Why the others are not best:

A is incorrect because Delivery Teams should not ignore realization considerations until the end.

B is incorrect because final-Sprint-only realization planning is too late for AgilePM.

C is partly tempting, but too absolute. Business roles are central to realization, yet delivery teams also contribute. The main issue is timing, not only ownership.

So the best AgilePM answer is D .

==========================

Comprehensive and Detailed Step-by-Step Explanation:

Context from the UniCo Scenario:

The CEO is tasked with overseeing the change analytics strategy to assess the effectiveness of the transformation program at UniCo. The focus on market share, customer awareness, and sales performance represents metrics primarily indicative of past outcomes rather than predictive trends. These are " lagging indicators " because they measure results that have already occurred rather than helping to predict future performance.

Analysis of the Answer Options:

A. No, because ‘leading’ metrics must be based on quantitative data.

Why Incorrect: While leading indicators are often quantitative, this is not a definitive requirement. Leading indicators can include qualitative metrics, such as customer sentiment or readiness for change, which forecast future outcomes.

B. No, because these metrics are lagging, output-focused indicators.

Why Correct: The CEO ' s metrics—market share, customer awareness, and sales of mobile applications—are retrospective and assess the outcomes of past strategies rather than providing actionable insights for proactive decision-making. This makes them lagging indicators that are unsuitable as " leading, result-oriented measures. " Leading indicators would include forward-looking metrics, such as staff readiness, customer pre-orders, or app engagement metrics.

C. Yes, because these indicators will identify if UniCo sales continue to decline.

Why Incorrect: While these metrics may identify declining sales, they are not suitable for preempting or preventing such issues. They lack predictive value and fail to inform actions needed to drive improvements proactively.

D. Yes, because these metrics monitor benefits realization at senior management level.

Why Incorrect: Although these metrics are useful for benefits realization, they are not sufficient as " leading " indicators. They reflect past performance rather than informing management on whether the change program is on track to achieve its intended future benefits.

Why B Is the Best Answer:

Distinction Between Leading and Lagging Indicators:

Leading indicators provide predictive insights to guide decision-making and corrective actions, while lagging indicators assess outcomes already achieved. The CEO ' s metrics fall into the latter category, as they focus on market share and customer awareness, which reflect results of past efforts.

Relevance to Change Analytics Strategy:

A robust change analytics strategy must include metrics that enable proactive adjustments. For example, measuring customer engagement during app trials or employee training completion rates would offer actionable insights into the program ' s progress.

Alignment with AgilePM and Change Management Practices:

AgilePM emphasizes continuous monitoring and adaptation using predictive metrics to guide successful delivery. The CEO ' s reliance on lagging indicators does not align with this proactive approach.

References to AgilePM Framework:

Metrics in Change Programs:

The AgilePM framework recommends using KPIs that drive decisions, emphasizing early indicators of potential issues. This ensures that leadership can take corrective actions during the program rather than after its completion. (AgilePM Practitioner Guide, Chapter 7: Governance and Control)

Benefits Realization and Leading Indicators:

Leading indicators are essential for tracking progress toward benefits realization. Focusing on lagging metrics risks missing early warning signs of misalignment. (AgilePM Practitioner Guide, Chapter 11: Measuring Success)

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.

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 two statements that explain why the Architecture Angels’ Marketing Director would be an appropriate Business Visionary are:

• B. Is fully committed to changing the company’s strategic direction to include hotel renovation. This shows that the Marketing Director is aligned with the project’s goals and is invested in its success.

• E. Has a passion for old buildings and can see the potential for business opportunity. This passion and vision are key characteristics of a Business Visionary, who is responsible for guiding the project towards delivering value for the business.

The two items that the Workshop Facilitator should be provided with when preparing for the workshop are:

• B. An understanding of the decision-making process. This will help the facilitator guide the discussion and help the group reach a consensus.

• C. Background to the disagreement and the reasons for this. This will help the facilitator understand the context of the disagreement and facilitate a more effective discussion.

Please note that while hints and tips on how to influence and persuade others (option A), empowerment to discuss any wider project issues that may arise during the workshop (option D), and a step-by-step guide to running an effective workshop (option E) could be helpful, they are not as crucial as understanding the decision-making process and the background to the disagreement for this specific workshop.

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

A. Team Leader E. Project Manager

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

The 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.

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.

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.

A. Yes, because this will allow the Solution Development Team to focus on the quality of the Solution Development Timebox ' s deliverable as a whole, in order to keep focus on the business need.

Rationale:

Setting acceptance criteria for the overall deliverables of a timebox is a key practice in Agile to ensure that the work meets the business objectives and quality expectations. It helps the Solution Development Team to understand what is required for the deliverables to be considered complete and acceptable. This aligns with the Agile principle of delivering quality and maintaining a constant pace of development. It also ensures that all team members are aligned on the goals and can focus on delivering value in line with business needs.

The Facilitator should invite the following two individuals to participate in the Workshop:

D. IT Operations Manager (Solution Development Team) E. Marketing Director (Business Visionary)

The rationale for this selection is that the disagreement is between the Marketing Director, who wants the reservation system to have professional photos and video tours (which impacts how the system will be used by potential customers and affects marketing strategy), and the IT Operations Manager, who is concerned with the system ' s technical limitations and maintenance. Both of these individuals are key to resolving the issue at hand, as they represent the conflicting requirements that need to be reconciled for the project to move forward.

Here are the DSDM Principles that would most help to reduce or mitigate the listed risks:

The ‘Hoy for Hoy Hall’ Action Group may cause delay to the project if they are not kept updated on how the finished rooms are going to look.

G. Communicate continuously and clearly

Timber Tigers will ensure that the front rooms are finished and approved by the end of Timebox A.

E. Build incrementally from firm foundations

The Architecture Angels IT support team may require more detail up front in order to approve the initial design for the new online reservation system.

A. Focus on the business need

The morale of the Solution Development Team may be adversely affected if the external web design specialist is not a team player.

C. Collaborate

Empowering the Solution Development Team to manage themselves on a day-to-day basis may result in the Project Manager losing sight of what activities are being carried out, by whom and when.

H. Demonstrate control

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

This scenario is about a specialist availability risk . Wanida has important compliance expertise, but her limited availability creates a risk that the Southeast Asia Delivery Teams may not get timely answers on compliance-sensitive work.

In AgilePM, the best response is usually to:

adapt communication and collaboration mechanisms ,

plan access to scarce expertise carefully ,

and help the team work efficiently without creating avoidable waiting time or risky assumptions .

That is exactly what A and D describe.

Why A is correct

“Hira should coordinate a communication plan to ensure the Delivery Team has timely access to Wanida ' s expertise based on her availability.”

This aligns very well with AgilePM and with Hira’s role as Project Manager. Hira is responsible for enabling coordination, reducing blockers, and helping the right people collaborate effectively. When a key expert has limited availability, a communication plan is a practical and agile response.

This could include:

agreed contact windows,

prioritization of urgent questions,

scheduled compliance touchpoints,

response expectations,

and visibility of when Wanida is available.

This is exactly the kind of facilitative coordination AgilePM expects.

Why D is correct

“The Delivery Team should compile key compliance questions in advance and send in batches to Wanida Anong to minimize real-time communication needs.”

This is also strongly aligned with AgilePM because it is:

practical,

collaborative,

proactive,

and efficient.

Rather than interrupting Wanida repeatedly or waiting until blockers pile up, the team should organize its questions thoughtfully and make the best use of her limited time. That reduces communication overhead and improves the quality of the interaction.

It also reflects mature agile behavior:

identify what information is truly needed,

consolidate it,

ask early,

and reduce dependency friction.

Why the other options are incorrect

B. Hira should escalate to Sarah Lark, the Business Sponsor, to allocate more compliance resources and protect the projects integrity.

This may become necessary if the risk becomes serious enough , but it is not the best immediate AgilePM response based on the scenario as stated. AgilePM prefers managing the issue at the lowest appropriate level first through coordination and practical adaptation before escalating for additional sponsorship intervention.

C. Hira should use the Risk Log to record risks and delay compliance-sensitive features until Wanida Anong is available.

Recording the risk may be sensible, but automatically delaying compliance-sensitive features is too rigid and not the best AgilePM answer. AgilePM favors finding adaptive ways to keep work moving safely rather than defaulting to delay when better communication planning may solve the problem.

E. The Delivery Team should proceed with assumptions and review with Wanida Anong at the end of the increment to minimize delays.

This is not AgilePM-aligned because it creates unnecessary compliance risk. Proceeding on unvalidated assumptions in a compliance-sensitive area can lead to rework, governance problems, or regulatory failure. AgilePM supports iterative learning, but not careless deferral of essential expert input.

AgilePM perspective

AgilePM encourages:

proactive risk handling,

strong communication,

collaboration across roles,

efficient use of specialist availability,

and escalation only when needed.

When a key expert is only partly available, the first response should be to structure access intelligently and help the team interact with that expert in the most effective way.

Therefore, the best two answers are:

A, 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 .

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 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 statement that does NOT comply with AgilePM is H .

In AgilePM, the Project Manager does play an important coordination and leadership role, but reviewing Sprint Backlogs each Sprint to check and focus priorities is not the right expression of that responsibility. Prioritization is primarily driven by the business roles , and the detailed Sprint-level backlog is typically managed much closer to the Delivery Team level.

Why H is incorrect:

Priorities are not owned by the Project Manager alone. They are shaped by business need and value, usually through the relevant business ownership roles.

The Sprint Backlog is a detailed delivery artifact used by the team to organize and execute work during the Sprint.

Hira can support coordination, visibility, dependency management, and escalation, but she should not be positioned as the person who reviews Sprint Backlogs in order to “focus priorities” each Sprint as though that were her core responsibility.

That wording shifts too much control toward the Project Manager and away from the empowered team and business-led prioritization model that AgilePM supports.

Why the other options are compliant:

A. Brinda Vyas owns and communicates the project vision, ensuring everyone understands how they contribute to the business goals.

This aligns well with the Business Visionary role. AgilePM expects the vision to be clearly owned and communicated.

B. Brinda Vyas resolves business-related conflicts and needs to be sufficiently available so Delivery Teams can move forward without delay.

This is also aligned. Business leadership must be engaged and available enough to avoid delays in clarification and decision-making.

C. Developers collaborate with each other and Sukra Aroon who ensures technical integrity of the solution, that it meets agreed priorities.

This is broadly aligned. Developers collaborate on delivery, and the Solution Architect safeguards technical coherence and integrity. The “agreed priorities” part is driven by the wider project context, but the statement is still generally consistent with AgilePM collaboration.

D. Developers provide consensus-based estimates to support effective planning and prioritization.

This fits AgilePM well. Delivery teams are closely involved in estimating because they are best placed to judge effort and feasibility.

E. Mira Bachar ensures business needs are clear and prioritized so the Delivery Teams can deliver maximum value.

This is consistent with the Product Owner-style responsibility of clarifying and prioritizing business needs.

F. Mira Bachar collaborates with Brinda Vyas, Sukra Aroon, and Hira to balance business priorities, technical feasibility and delivery constraints.

This strongly aligns with AgilePM’s collaborative approach across business, technical, and management roles.

G. Hira ensures effective collaboration between everyone and removes blockers.

This is a good AgilePM description of the Project Manager’s facilitative role.

AgilePM perspective:

AgilePM promotes:

business-led prioritization

empowered delivery teams

facilitative project management

collaborative dependency handling

clear role boundaries

A Project Manager should support transparency and coordination, but not take over detailed Sprint backlog control in a way that weakens team empowerment or business ownership of priorities.

Therefore, the statement that does not comply with AgilePM is H .

The two actions that the Workshop Facilitator should take if the team cannot agree on the system content are:

C. Facilitate the creation of a list of actions to be carried out after the workshop, to resolve the issue. This will ensure that the disagreement does not stall the project and that there is a clear plan for how to move forward.

E. Prepare a report describing the outcome of the workshop. This will provide a record of the discussion and any decisions made, which can be useful for future reference and for keeping stakeholders informed.

Please note that while presenting their own interpretation of what the system should include (option A) or presenting the group with a predefined specification of what should be included (option B) might seem like potential solutions, these actions could bias the discussion and may not lead to a solution that meets all stakeholders’ needs. Agreeing to disagree and closing the workshop (option D) could leave the issue unresolved, which could cause problems later in the project. The facilitator’s role is to guide the discussion and help the team reach a consensus, not to impose their own views or prematurely end the discussion.