AgilePM-Foundation Agile Project Management (AgilePM) Foundation Exam Question and Answers

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.

Statement 1: Correct. Offering supportive feedback after moments of insight reinforces learning and helps individuals process change more effectively.

Statement 2: Incorrect. While talks from experts may inform, they are less impactful than engaging individuals directly.

Key AgilePM Concepts Referenced:

Neuroscience in Change Management: AgilePM Handbook, Chapter 6, Section 6.2.

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.

Qualitative Measures: These provide insight into the underlying reasons, motivations, and emotions behind behaviors. Examples include interviews, open-ended surveys, and focus groups.

Other Options:

B: Quantitative measures focus on numerical data but lack context.

C: Leading indicators predict future performance but don’t explain behavior.

D: Lagging indicators reflect past performance, not the reasons behind it.

Key AgilePM Concepts Referenced:

Measurement and Analysis: AgilePM Handbook, Chapter 7, Section 7.5.

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.

Within the Solution Development team, it is not required for all members to be multi-skilled experts1. While a diverse set of skills is beneficial, DSDM emphasizes collaboration and the effective use of individual strengths rather than expecting every team member to be an expert in all areas1.

Statement 1: Correct. Leading by example is crucial for inspiring trust and alignment with the change vision. Symbolic actions by leaders play a significant role in fostering engagement.

Statement 2: Incorrect. Change influence is not limited to leaders; team members and change agents can also drive and inspire change.

Key AgilePM Concepts Referenced:

Role of Leadership in Change: AgilePM Handbook, Chapter 6, Section 6.2.

In a DSDM project, contingency is typically managed by varying the features to be delivered6. This approach aligns with the DSDM principle of delivering the most critical work first and using the MoSCoW prioritization to adjust the scope of delivery as needed.

When initially creating MoSCoW priorities in AgilePM, the primary focus is on Timebox priorities. This approach ensures that each Timebox (a fixed period during which specific tasks must be completed) has clear and prioritized objectives. The MoSCoW method (Must have, Should have, Could have, Won't have this time) helps the team to deliver the most critical features within the given timeframe, thereby optimizing the value delivered in each iteration. This prioritization ensures that essential functionalities are completed first, making the project adaptable and resilient to changes.

References:

AgilePM Foundation Handbook

"Agile Project Management with Scrum" by Ken Schwaber

Statement 1: Correct. The change curve describes typical emotional responses to change, including denial, resistance, exploration, and commitment.

Statement 2: Incorrect. The change curve applies to both positive and negative changes, as it reflects the adjustment process regardless of the perceived nature of the change.

Key AgilePM Concepts Referenced:

Emotional Responses to Change: AgilePM Handbook, Chapter 6, Section 6.3.

Performing Stage: In this stage, team members work cohesively towards achieving results. Roles and processes are clear, and collaboration is at its peak.

Other Stages:

Forming: Initial setup with limited collaboration.

Storming: Characterized by conflict and role clarification.

Adjourning: Focused on disbanding after tasks are completed.

Key AgilePM Concepts Referenced:

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

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.

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.

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

Timeboxing: Fixed time periods, such as sprints, are used to focus efforts and deliver outcomes within a predefined timeframe. This helps teams remain disciplined and maintain momentum while working iteratively.

Other Options:

A: Minimum viable product relates to the initial version of a product with essential features.

C: Full transparency refers to visibility into the process.

D: Frequent delivery is broader and does not imply fixed time periods.

Key AgilePM Concepts Referenced:

Timeboxing: AgilePM Handbook, Chapter 3, Section 3.4.

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.

In DSDM, it is true that one DSDM role does not necessarily mean one person. This allows for flexibility in assigning roles based on the project’s needs and the individuals’ skills and capacities. It is possible for one person to hold multiple roles or for a role to be shared among several people, depending on what is most effective for the project.

The Post-Project phase in AgilePM is crucial for evaluating the project’s success in terms of the business benefits realized3. It is conducted after the project is completed and focuses on assessing whether the expected benefits outlined at the start of the project have been achieved

Supporting and Influencing Local Staff: Line leaders play a vital role in translating the change vision into action at the team level. They understand the specific needs and concerns of their teams and can act as a bridge between staff and senior management.

Other Options:

A: Local decision-making authority is beneficial but not their primary role.

B: Leaders are often deeply impacted by change.

D: Line leaders often juggle multiple responsibilities.

Key AgilePM Concepts Referenced:

Role of Line Leaders: AgilePM Handbook, Chapter 5, Section 5.6.

Maintenance is not one of the interest groups into which each DSDM role is grouped1. The recognized interest groups are Business, Solution/Technical, and Management1. These groups represent the different areas of focus within a DSDM project.

In DSDM, each role is grouped into interests such as Business, Solution/Technical, and Management. Maintenance is not one of the interests into which DSDM roles are grouped. The primary focus of DSDM roles is to ensure that the project is delivered successfully by balancing business needs, technical feasibility, and effective management practices.

References:

DSDM Agile Project Framework Handbook

"Agile Project Management: Best Practices and Methodologies" by Eric Brechner

Communicating the Danger of Inaction: Highlighting risks of not changing amplifies dissatisfaction with the status quo, creating urgency and driving motivation for change.

Other Options:

A: Performance targets align with accountability, not dissatisfaction.

C: Clarifying steps supports action but doesn’t address dissatisfaction.

D: Benefits focus on the positive outcome, not dissatisfaction.

Key AgilePM Concepts Referenced:

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

Statement 1: Correct. Diverse teams leverage different perspectives, leading to higher creativity and innovation, as Agile encourages collaborative solutions.

Statement 2: Incorrect. Diverse teams typically take longer to reach consensus due to varying viewpoints and styles of communication, though the decisions they make are often more robust.

Key AgilePM Concepts Referenced:

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

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.

Adjourning: This stage occurs when a team disbands after achieving its objectives. Members reflect on their accomplishments and prepare to move on, often with a sense of closure and satisfaction.

Other Stages:

Forming: Initial stage where the team is being established.

Storming: Involves conflict as roles and expectations are clarified.

Performing: High-functioning stage focused on productivity.

Key AgilePM Concepts Referenced:

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

The Foundations phase is when it is established how quality will be assured4. This phase builds upon the preliminary investigation from the Feasibility phase to establish a fundamental understanding of the business rationale for the project and how the development and delivery of the solution will be managed, including quality assurance measures4.

The DSDM process can indeed be configured and calibrated to cater for a range of projects, from those requiring light governance to those needing stronger governance1. This flexibility allows the DSDM process to be tailored to the specific needs of the project, ensuring that the right balance between control and agility is achieved1.