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

Phased Approach: Rolling out change one department at a time reflects a phased delivery strategy, which allows for controlled implementation and adjustment before wider deployment.

Other Options:

A: Big Bang involves simultaneous rollout across the organization.

C: Voluntary Adoption allows individuals to opt in.

D: Incremental/Iterative applies to feature or solution delivery rather than departmental rollout.

Key AgilePM Concepts Referenced:

Delivery Strategies: AgilePM Handbook, Chapter 3, Section 3.7.

The purpose of the Foundations Summary in AgilePM is to provide enough information to decide whether the project is likely to deliver a return on investment. This document serves as a comprehensive overview of the project's viability, including a high-level understanding of the business case, objectives, scope, and risks. It ensures that all stakeholders have a clear understanding of the project's potential value and feasibility before significant resources are committed.

References:

AgilePM Foundation Handbook

"Agile Project Management: Creating Innovative Products" by Jim Highsmith

 The Delivery Plan defined by DSDM has a planning horizon that includes the end of the project7. This plan looks towards the future, often months or years ahead, to guide the incremental delivery of the project’s outcomes.

Small Incremental/Iterative Releases: Delivering change in smaller increments allows for immediate feedback and adaptation, embodying the concept of 'Minimum Viable Change Practice.'

Other Options:

A: Big Bang involves a single, large-scale rollout, unsuitable for iterative practices.

B: Phased rollouts involve sequential implementation but may not emphasize iteration.

C: Voluntary Adoption doesn’t inherently align with iterative releases.

Key AgilePM Concepts Referenced:

Iterative Delivery Strategies: AgilePM Handbook, Chapter 3, Section 3.7.

Simple: The Cynefin framework classifies situations where cause and effect are obvious as "simple," requiring straightforward solutions based on best practices.

Other Options:

Multifaceted: Not a recognized category in Cynefin.

Complex: Refers to situations where cause and effect are not immediately apparent.

Chaotic: Refers to situations with no apparent relationship between cause and effect.

Key AgilePM Concepts Referenced:

Cynefin Framework for Complexity: AgilePM Handbook, Chapter 3, Section 3.3.

The stated benefits of using DSDM include the business being better able to direct development, the reduced risk of building the wrong solution, and a smoother deployment process2. These benefits stem from DSDM’s iterative approach and close collaboration with stakeholders2.

Cognitive Rigidity: This represents a fixed mindset, where individuals resist new ways of thinking or acting. Neuroscience highlights that flexibility is key to adapting to change.

Other Options:

A: Routine seeking reflects comfort in familiarity but isn’t a fixed mindset.

B: Emotional reactions are part of normal responses to change.

D: Short-term focus relates to decision-making, not fixed thinking.

Key AgilePM Concepts Referenced:

Managing Resistance Through Neuroscience: AgilePM Handbook, Chapter 6, Section 6.7.

Statement 1: Incorrect. Non-verbal communication refers to gestures, facial expressions, and body language, which cannot be captured in written form.

Statement 2: Correct. Actions, such as behavior during change or leading by example, can convey powerful messages without verbal communication.

Key AgilePM Concepts Referenced:

Non-Verbal Communication in Engagement: AgilePM Handbook, Chapter 4, Section 4.4.

The Solution Architecture Definition is an evolutionary product that provides a high-level design framework for the solution2. It is intended to cover both business and technical aspects of the solution to a level of detail that makes the scope of the solution clear but does not constrain evolutionary development2. This ensures that the solution architecture supports the business direction and the solution under development will be fit for its intended purpose3

Statement 1: Incorrect. Diverse teams tend to take longer to make decisions due to differing perspectives and approaches. However, this trade-off leads to more thorough and creative decision-making, which is a recognized strength of diverse teams.

Statement 2: Incorrect. Members of diverse teams often require time to align on communication styles, goals, and processes. Effective collaboration in diverse teams is developed through trust-building and active engagement, as outlined in Agile team practices.

Why Diverse Teams Matter in Agile:Agile emphasizes collaboration and innovation, which are enhanced by diverse teams. However, the process of building trust and understanding takes time. AgilePM recommends fostering inclusivity and addressing conflicts constructively to harness the strengths of diverse teams.

Key AgilePM Concepts Referenced:

Building Effective Teams: AgilePM Handbook, Chapter 5, Section 5.3.

Trust and Transparency in Teams: Chapter 4, Section 4.6.

Solution increments are created during the Evolutionary Development phase. This phase is where the solution is developed iteratively, building on the firm foundations laid out in the previous phases1. It involves creating increments of the product through time-boxed iterations, ensuring that the solution evolves in line with the project’s objectives and business needs.

Feedback and Coaching: Sponsors play a critical role in change, and change managers support them by providing feedback and coaching to help them lead effectively. This builds their confidence and ensures alignment with the change vision.

Other Options:

A: Sponsors should prepare the vision themselves.

B: Sponsors themselves lead commitment-building efforts.

D: Protecting sponsors isn’t an effective strategy; engaging them is key.

Key AgilePM Concepts Referenced:

Sponsor Engagement: AgilePM Handbook, Chapter 6, Section 6.2.

The application of Principle 8, Demonstrate Control, is collectively applied by the whole team4. This principle ensures that there are proper levels of planning, progress measurement, and reporting in place.

DSDM acknowledges that change is inevitable and that projects operate within a changing world5. The methodology is designed to embrace change and harness its benefits, rather than resist it.

Statement 1: Correct. Actively responding to contributions fosters a sense of inclusion and appreciation, which is crucial for engagement and trust during change.

Statement 2: Incorrect. Decisions during change often involve emotional as well as rational considerations, as people’s behaviors and attitudes are not purely logical.

Key AgilePM Concepts Referenced:

Engaging Stakeholders Emotionally: AgilePM Handbook, Chapter 4, Section 4.3.

The DSMD (Dynamic Systems Development Method) principle of “Build incrementally from firm foundations” emphasizes the importance of having a solid understanding of the project’s foundation before proceeding with incremental development. This principle ensures that each increment is built upon a stable base, which supports the overall project integrity and success.

Transparency: Sharing the rationale and timeline for change ensures openness and builds trust among stakeholders. Transparency is fundamental to managing expectations and mitigating resistance.

Other Options:

Inclusivity: Focuses on ensuring all voices are heard.

Connectivity: Refers to fostering relationships.

Empathy: Relates to understanding others’ feelings, not information sharing.

Key AgilePM Concepts Referenced:

Transparent Communication: AgilePM Handbook, Chapter 4, Section 4.2.

Storming Stage: During this stage, team members test and challenge assumptions, roles, and processes. This is essential for resolving conflicts and building stronger foundations for collaboration.

Other Stages:

Forming: Initial stage with minimal conflict.

Performing: High-functioning stage with clear roles.

Adjourning: Focuses on reflection and closure.

Key AgilePM Concepts Referenced:

Team Development Models: AgilePM Handbook, Chapter 5, Section 5.4.

Autonomy, Mastery, and Purpose: As outlined by Daniel Pink, these three factors drive motivation in knowledge work, which relies on creativity and engagement. Agile practices support autonomy through self-organizing teams, mastery through continuous learning, and purpose through shared goals.

Other Options: These reflect traditional or outdated models of motivation and do not align with Pink’s framework.

Key AgilePM Concepts Referenced:

Motivating Teams: AgilePM Handbook, Chapter 5, Section 5.7.

Statement 1: Correct. Rich communication channels, such as face-to-face conversations or video calls, are necessary for active engagement as they allow for two-way interaction and emotional connection.

Statement 2: Correct. Leaner channels, like emails or memos, are appropriate when the message is straightforward and unlikely to be misinterpreted.

Key AgilePM Concepts Referenced:

Effective Communication Channels: AgilePM Handbook, Chapter 4, Section 4.3.

Statement 1: Correct. Diverse teams bring varied perspectives, which enhances creativity and innovation. AgilePM highlights the importance of leveraging diversity for better outcomes.

Statement 2: Correct. Diverse teams approach problems from multiple angles, resulting in more thorough decision-making. However, this often requires additional time to align perspectives.

Key AgilePM Concepts Referenced:

Team Collaboration: AgilePM Handbook, Chapter 5, Section 5.3.

A Timebox Plan is updated at the Daily Start-ups. These daily meetings allow the team to review progress, discuss any issues, and make necessary adjustments to the plan. Regular updates ensure that the project stays on track and that any deviations are addressed promptly, facilitating smooth and efficient progress towards the Timebox objectives.

References:

AgilePM Foundation Handbook

"Scrum: The Art of Doing Twice the Work in Half the Time" by Jeff Sutherland

Principle 1 – Focus on the Business Need suggests that every decision taken during a project should be viewed in light of the overriding project goal. This principle ensures that all decisions align with the main objective of delivering what the business needs, thus maintaining a clear focus on achieving the project’s goals.

In DSDM, the Minimum Usable Subset refers to the “Must Have” requirements as defined by the MoSCoW prioritization1. This subset ensures that the project delivers the core functionalities that are critical for the system to be considered useful and viable2.

Active Listening: The change curve requires empathetic and effective communication to understand concerns, address resistance, and guide individuals through emotional responses to change. Active listening is a vital skill in this process.

Other Options:

Time management: Important but not specific to the emotional aspects of change.

Negotiation: Relevant for resolving conflicts but secondary to listening during change.

Decision-making: Necessary for leadership but not for guiding individuals emotionally.

Key AgilePM Concepts Referenced:

Engagement and Support: AgilePM Handbook, Chapter 6, Section 6.4.

Dialogue: The ability to talk about anything while maintaining relationships and achieving a good outcome is a clear demonstration of effective dialogue. Dialogue is essential for fostering mutual understanding and collaboration, especially during change. AgilePM emphasizes open communication and rich interaction to address concerns and align stakeholders.

Other Options:

Inclusivity: Focuses on ensuring diverse perspectives are included but doesn’t inherently emphasize open conversations.

Connectivity: Refers to fostering connections among team members and stakeholders, which is a broader concept.

Transparency: While important, it primarily relates to openly sharing information rather than fostering dialogue.

Key AgilePM Concepts Referenced:

Engagement and Communication Principles: AgilePM Handbook, Chapter 4, Section 4.2.

Minimum Viable Product (MVP): An MVP allows early customers to use a product and provide valuable feedback, which is then incorporated into subsequent iterations. This is central to Agile practices, emphasizing incremental delivery and responsiveness to user needs.

Other Options:

B: Full transparency relates to visibility into processes and progress, not product development.

C and D: These refer to team dynamics, not product delivery.

Key AgilePM Concepts Referenced:

Incremental Delivery: AgilePM Handbook, Chapter 3, Section 3.7.

The missing word in the sentence is “Champion”. The Business Sponsor is known as the project Champion because they are committed to the solution and the delivery approach34. This role is crucial as it provides the strategic direction and controls the funding/budget for the project1.

Dissatisfaction with the Status Quo: The change formula includes dissatisfaction as a key driver for change. Without sufficient dissatisfaction, the motivation to change is diminished.

Other Options:

B, C, and D: These factors, while important, are not explicitly part of the Beckhard and Harris change formula.

Key AgilePM Concepts Referenced:

Change Formula Framework: AgilePM Handbook, Chapter 6, Section 6.5.

Action Phase: Breaking change actions into smaller, manageable tasks happens during the Action step, where detailed plans are implemented. This ensures smoother execution and tracking of progress.

Other Options:

Discovery: Focuses on understanding the current situation.

Ideas: Involves generating potential solutions.

Prioritization: Helps decide which tasks or changes to focus on.

Key AgilePM Concepts Referenced:

Continuous Change Management Cycle: AgilePM Handbook, Chapter 6, Section 6.6.