PMI DASM Exam Questions

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.

A well-written user story in agile practices, including Disciplined Agile, describes the customer's perspective. User stories are short, simple descriptions of a feature or requirement from the point of view of the end user or customer. They are intended to capture the 'who, what, and why' of a requirement, focusing on the value it delivers to the customer. This perspective ensures that the development team understands the real-world needs and motivations behind the features they are building, allowing them to create solutions that truly meet user needs.

PMI Disciplined Agile (DA) Toolkit, which outlines the structure and purpose of user stories, highlighting the importance of describing features from the customer's perspective.

PMI Agile Practice Guide, which discusses the use of user stories to capture customer requirements and deliver value.

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.

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.

A well-written user story in agile practices, including Disciplined Agile, describes the customer's perspective. User stories are short, simple descriptions of a feature or requirement from the point of view of the end user or customer. They are intended to capture the 'who, what, and why' of a requirement, focusing on the value it delivers to the customer. This perspective ensures that the development team understands the real-world needs and motivations behind the features they are building, allowing them to create solutions that truly meet user needs.

PMI Disciplined Agile (DA) Toolkit, which outlines the structure and purpose of user stories, highlighting the importance of describing features from the customer's perspective.

PMI Agile Practice Guide, which discusses the use of user stories to capture customer requirements and deliver value.