PMI DASM Exam
Disciplined Agile Scrum Master (Page 2 )

Updated On: 1-Feb-2026

Which of the following roles would fall under that of a "specialist" on a Disciplined Agile Delivery Team?

  1. Business Analyst
  2. Product Owner
  3. Project Manager
  4. Stakeholder

Answer(s): A

Explanation:

In the context of the Disciplined Agile (DA) framework, a "specialist" on a Disciplined Agile Delivery Team is someone with a specific, specialized skill set or domain expertise that contributes to the overall development and delivery process.
While the DA framework promotes cross-functional team members, it acknowledges that certain roles require specialized knowledge. A Business Analyst (BA) is considered a specialist role because they bring specific expertise in requirements gathering, process analysis, stakeholder communication, and translating business needs into actionable tasks for the development team. According to PMI's Disciplined Agile guidelines, BAs provide value by ensuring that the requirements are well-understood and clearly defined, which is crucial in aligning the team's efforts with stakeholder needs. On the other hand, the roles of Product Owner (B) and Project Manager (C) are more related to leadership, decision-making, and coordination, rather than specialized technical or analytical expertise. Stakeholders (D) are external to the delivery team and are not considered specialists within the team itself.



Which rote on the delivery team builds the product right?

  1. Architecture Owner
  2. Team Lead
  3. Team Member
  4. Product Owner

Answer(s): C

Explanation:

In Disciplined Agile (DA), the Team Member role is primarily responsible for building the product correctly. Team Members are the individuals who directly create the product by writing code, testing, designing, and performing other tasks necessary to deliver a working solution. The Architecture Owner may guide architectural decisions, and the Team Lead may facilitate processes, but it is the Team Members who actively build the product and ensure it meets the required standards and specifications.


Reference:

PMI Disciplined Agile (DA) Toolkit, which clarifies the responsibilities of the various roles, specifying that Team Members are the ones actively involved in building the product. PMI, "Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)," which details the responsibilities of Team Members in delivering the product.



What goal diagrams should a team select first?

  1. The goals in which the team has the least experience
  2. The goals that ate most relevant to the team's context and lite cycle.
  3. The goals that are the easiest to complete.
  4. The goals that are selected by the customer and stakeholders.

Answer(s): B

Explanation:

In Disciplined Agile, teams are encouraged to select goals that are most relevant to their context and life cycle. This approach ensures that the team focuses on achieving outcomes that align with their specific needs, challenges, and project phase. Goal diagrams in DA help teams visualize and prioritize their objectives, and by choosing goals most pertinent to their current context, teams can address the most critical aspects first and adjust their practices effectively.


Reference:

PMI Disciplined Agile (DA) Toolkit, which discusses the use of goal diagrams and emphasizes the importance of selecting goals based on the team's context and project life cycle. PMI, "Choose Your WoW! A Disciplined Agile Delivery Handbook for Optimizing Your Way of Working (WoW)," which provides guidance on goal-setting and prioritization in Disciplined Agile.



What docs a well-written user story describe?

  1. The expectations of the product owner.
  2. The needs of all users.
  3. The customers' perspective.
  4. A fixed outcome.

Answer(s): C

Explanation:

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.


Reference:

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.



Select two tactical scaling factors that must be considered when analyzing the team's context.
(Choose two)

  1. Demographics
  2. Best Practices
  3. Domain Complexity
  4. Team Size
  5. Budget
  6. Dynamics

Answer(s): C,D

Explanation:

When analyzing a team's context for tactical scaling in Disciplined Agile, two key factors that must be considered are Domain Complexity and Team Size:
C . Domain Complexity: Refers to the complexity of the problem domain the team is working within. More complex domains require different approaches and potentially more sophisticated techniques to manage uncertainty, dependencies, and risks.
D . Team Size: The size of the team affects how the team communicates, collaborates, and organizes itself. Larger teams may require additional coordination, communication practices, and role definitions to be effective.
The other options are less relevant for tactical scaling:
A . Demographics, B. Best Practices, E. Budget, and F. Dynamics are not directly identified as key tactical scaling factors in the Disciplined Agile context.



Viewing page 2 of 11
Viewing questions 6 - 10 out of 50 questions



Post your Comments and Discuss PMI DASM exam prep with other Community members:

Join the DASM Discussion