Most Recent PMI DASM Exam Questions & Answers

The three phases of Disciplined Agile Delivery (DAD)'s delivery life cycle are:

Inception: This phase focuses on getting the project off the ground. It includes identifying stakeholders, understanding the vision, defining the initial scope, and planning for the necessary resources and timeline.

Construction: This phase involves building the solution incrementally and iteratively, with continuous delivery of working software and regular stakeholder feedback.

Transition: This phase prepares the solution for release into production or the marketplace. It includes final validation, user training, deployment planning, and release management.

Other options are incorrect:

A . Commencement, Creation, Evolution are not standard DAD phases.

B . Initiation, Foundation, Conversion do not match DAD terminology.

C . Introduction, Substance, Alteration are not relevant to DAD.

Therefore, the correct answer is D. Inception, Construction, Transitions.

In the context of the Disciplined Agile framework, when a team is dealing with rapidly changing requirements but is resistant to frequent releases and does not have an Agile mindset, the Traditional lifecycle is appropriate. This lifecycle aligns with teams that prefer a more plan-driven, less iterative approach, which typically includes longer release cycles and detailed upfront planning. The Traditional lifecycle in Disciplined Agile follows a waterfall-like approach, which is suitable when the team is not yet prepared to adopt Agile principles such as frequent delivery and adaptive planning.

The other options do not match this scenario:

A . Program lifecycle is used for coordinating multiple teams on larger programs, which is not relevant to a single team with the specified conditions.

B . Lean focuses on optimizing flow and delivering value quickly, which contrasts with the team's preference for infrequent releases.

D . Agile lifecycle involves iterative development and frequent releases, which the team is resistant to.

Therefore, C. Traditional is the correct answer as it fits the team's preference for less frequent releases and their lack of an Agile mindset.

The coordination meeting (often referred to as the daily stand-up or daily coordination meeting in Agile practices) is crucial for a project team because it provides an opportunity for the team to help itself stay in sync. This meeting is typically held daily and allows team members to communicate their progress, discuss any challenges or impediments, and align their activities with the project's goals.

In Disciplined Agile, such meetings are vital for fostering collaboration and ensuring that everyone on the team is aware of what others are doing, which helps avoid misunderstandings, duplicate work, and potential blockers. The purpose is not to report to a manager but for the team to coordinate, plan, and adjust their work dynamically to ensure continuous alignment and effective progress towards the team's objectives.

PMI Disciplined Agile Toolkit, which emphasizes the importance of coordination meetings (or daily stand-ups) in maintaining team alignment and promoting self-organization.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which describes the value of regular team coordination to ensure synchronicity and continuous alignment within agile teams.

Disciplined Agile (DA) provides a solid foundation for business agility through multiple mechanisms, including:

B . Defining a framework for agility at scale: DA offers a comprehensive toolkit that supports scaling agile practices across an organization, integrating principles from various agile methodologies to ensure coherence and alignment.

D . Providing guidance to streamline processes in a context-sensitive manner: DA emphasizes tailoring processes to the specific context of the organization, project, or team, rather than applying a one-size-fits-all approach. This flexibility allows organizations to adapt more effectively to change and improve their agility.

A . Enforcing adherence to organizational standards contradicts the DA principle of pragmatism and flexibility.

C . Creating awesome teams that foster joy is beneficial but is not specifically cited as foundational for business agility.

E . Describing trade-offs is part of DA's decision-making framework but not directly a way of providing a foundation for business agility.

Thus, the correct answers are B. Defines a framework for agility at scale and D. Provides guidance to streamline processes in a context-sensitive manner.

In Disciplined Agile (DA), the three common phases across project life cycles are Inception, Construction, and Transition. These phases reflect the iterative and incremental approach of agile methodologies tailored to suit varying contexts.

Inception: This phase is about getting things started properly. It includes initial planning activities such as defining the vision, developing a preliminary project plan, identifying stakeholders, securing funding, and setting up the initial environment.

Construction: This phase focuses on developing a consumable solution in a series of iterations. The team builds, enhances, and evolves the solution to ensure that it meets stakeholders' needs while remaining aligned with the overarching vision and goals.

Transition: The transition phase ensures that the solution is ready for delivery to the end-users or stakeholders. This includes final validation and verification activities, user training, deployment, and addressing any remaining issues.

These phases are common in the DA life cycles, reflecting the disciplined approach to managing complexity in various types of projects, from straightforward to highly complex, while supporting adaptability and continuous improvement.

PMI, 'Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW),' which outlines the DA life cycles, including Inception, Construction, and Transition phases.

PMI's Disciplined Agile Toolkit, which describes these phases in detail and their relevance across different types of project life cycles.